Kite MCP Server

Integrate existing AI applications with Kite using the Model Context Protocol (MCP).,

Model Context Protocol (or MCP) helps LLMs interface with external systems.

The Kite MCP server allows a large and growing number of web and desktop applications supporting MCP to utilize your Kite Passport, and is easy to setup by copying and pasting a URL. These applications, such as Claude and ChatGPT, may use more approachable language such as "connectors" or "integrations" when referring to setting up connections to MCP servers.

Accessing Your Kite MCP Server URL

Every KitePass has a unique MCP server URL. This URL contains your API key and should be treated as a secret credential that is only provided to trusted MCP clients.

Your MCP server URL can be found on your Kite Passport page, with an icon to copy the URL to your clipboard in one click.

The MCP server URL utilizes the following format:

https://mcp.prod.gokite.ai/api_key_{api_key_value}/mcp

In the staging environment, the URL is hosted at mcp.staging.gokite.ai instead of mcp.prod.gokite.ai and the MCP server uses the staging API.

Adding Your Kite MCP Server to a Client

Many clients allow MCP servers to be connected simply by providing a URL through a user interface.

Here is a screenshot of the interface Claude, a desktop client, uses for connecting to remote MCP servers:

Here is a similar screenshot of the interface Lutra, a web-based client, uses for connecting to remote MCP servers:

If you are asked to specify a transport type as part of the setup, choose Streamable HTTP.

Manual JSON Configuration

Some clients may require a more manual type of configuration via a file in a format such as JSON. Here is an example of how you can connect to your MCP server to Claude using the claude_desktop_config.json file:

{
  "mcpServers": {
    "kite-passport-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.prod.gokite.ai/api_key_{api_key_value}/mcp"]
    }
}

The exact format used by different applications may vary, but the syntax shown above works with most clients requiring this type of manual configuration.