KIM MCP Broker | Kynection

Connect Once

1. Open setup

Use your own KIM login to create a private MCP token.

2. Add the MCP URL

Point your LLM platform at https://mcp.kynection.kim/mcp.

3. Start with knowledge

Ask for schema, app, and relationship context before reading live records.

Install Guides

Use these sections for Claude, Cursor, Gemini CLI, Codex, and other MCP clients.

Claude / Claude Desktop

Custom remote MCP connector with OAuth or bearer auth.

Cursor

Streamable HTTP in Cursor MCP settings or mcp.json.

Gemini CLI

gemini mcp add --transport http.

Setup Instructions

Go to https://mcp.kynection.kim/setup.
Enter your KIM email and password.
Keep the server URL as kynection.upvise.com unless Kynection gives you another server.
Copy the generated token beginning with kim_.
Configure your MCP client with the URL and authorization header below.

MCP URL:
https://mcp.kynection.kim/mcp

Authorization header:
Authorization: Bearer <your kim_ token>

Install In AI Platforms

Claude / Claude Desktop

Open Claude settings, then go to Connectors or Customize > Connectors.
Add a custom connector / custom remote MCP server.
Use https://mcp.kynection.kim/mcp as the remote MCP URL.
When Claude opens the authorization flow, sign in with your KIM credentials.
Enable the connector in the conversation tools menu.

Team and Enterprise workspaces may require an Owner to add the custom connector first.

Cursor

Open Cursor Settings, then go to MCP.
Add a new remote MCP server.
Choose Streamable HTTP when available.
Use https://mcp.kynection.kim/mcp as the URL.
Authenticate with OAuth, or add the Authorization header if Cursor asks for manual headers.

{
  "mcpServers": {
    "kim-gateway": {
      "type": "http",
      "url": "https://mcp.kynection.kim/mcp",
      "headers": {
        "Authorization": "Bearer <your kim_ token>"
      }
    }
  }
}

Gemini CLI

Gemini web may not expose custom MCP setup in every workspace. Use Gemini CLI where MCP server configuration is available.

gemini mcp add --transport http kim-gateway https://mcp.kynection.kim/mcp --header "Authorization: Bearer <your kim_ token>"

gemini
/mcp

Codex

export KIM_MCP_TOKEN='<your kim_ token>'
codex mcp add kim-gateway --url https://mcp.kynection.kim/mcp --bearer-token-env-var KIM_MCP_TOKEN

Other MCP Clients

Use Streamable HTTP first. If the client only supports SSE, use the SSE URL.

Streamable HTTP:
https://mcp.kynection.kim/mcp

Header:
Authorization: Bearer <your kim_ token>

SSE fallback:
https://mcp.kynection.kim/sse?token=<your kim_ token>

Platform Notes

If a client asks for a bearer token field, paste only the value beginning with kim_.
If a client asks for a full authorization header, paste Authorization: Bearer <your kim_ token>.
If OAuth is supported, the client may open Kynection authorization automatically and ask for your KIM login.
Only connect platforms and workspaces you trust, because MCP tools can read and act through your KIM account permissions.

Useful First Prompts

Check connection

Use connection_status and knowledge_list.

Plan a query

Use knowledge_table for projects.projects, then tell me the safest way to query active projects.

Understand an app

Use knowledge_app for KimProjects and summarize the key tables.

Find joins

Use knowledge_relationships for sales.quotes and projects.projects before reading records.

Available Knowledge Tools

These tools help the model choose the right KIM tables, relationships, and app context.

knowledge_list
knowledge_search
knowledge_table
knowledge_relationships
knowledge_app

Notes For Teams

Each user creates their own token with their own KIM credentials.
Tokens are private and should not be shared.
The broker stores credentials encrypted and uses a cached Upvise token first.
If the Upvise token expires or fails, the broker re-logins automatically with the saved KIM credentials.