> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gleap.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP servers

> Give Kai Code tools beyond the repository — your issue tracker, docs, databases and internal APIs.

[MCP](https://modelcontextprotocol.io) servers give Kai Code tools that go beyond reading and writing code: querying your database, searching your docs, creating an issue in your tracker, or calling an internal API. They are configured per project under **Kai Code → Settings → MCP** and are available in every coding session of that project.

MCP servers are optional. Kai Code works without any.

## Add a server

Choose **Add MCP server**. The chooser offers three kinds of servers:

<CardGroup cols={3}>
  <Card title="Popular integrations" icon="puzzle-piece">
    One-click presets such as **Gleap**, plus 1000+ apps through Composio. Search the list by name.
  </Card>

  <Card title="Custom HTTP / SSE server" icon="server">
    A remote MCP server you reach by URL. Optional custom headers for authentication.
  </Card>

  <Card title="Local stdio process" icon="terminal">
    A command Kai runs itself — `npx`, a binary — with arguments and environment variables.
  </Card>
</CardGroup>

### Popular integrations

* **Gleap** adds Gleap's own tools: reading and managing tickets and feedback, the knowledge base and customers. It connects with one click and needs no OAuth.
* **Composio integrations** (Linear, Notion, Jira, Slack, GitHub and many more) open the app's own sign-in when you add them. The row shows **Pending** until the sign-in completes; use **Reconnect** if the connection expires later.

<Warning>
  Tools can read everything the connected account can read, and Kai may include what a tool returns in its work. Review the tool list after connecting, switch off tools the agent does not need, and mention any limits in the project's custom instructions.
</Warning>

### Custom servers

For an HTTP server enter its URL and any headers it needs. For a stdio server enter the command, its arguments and environment variables such as API keys.

## Manage servers

The **Connected tools** list shows every server with its status from the most recent coding session that used it: **Connected · N tools**, **Error** with the message when Kai could not reach it, **Pending** for a Composio sign-in that is not complete, **Disabled**, or **Not yet used**. From a row you can:

* switch the server **on or off** without removing its configuration,
* **Edit** its connection — for HTTP servers the editor lists the **Available tools** so you can switch off any tool you don't want Kai to use,
* **Reconnect** a Composio integration whose sign-in expired,
* **Remove** it. You can re-add it later from the server browser.

## Where the tools run

For cloud sessions Kai connects to HTTP servers and starts stdio processes in the Gleap cloud. For sessions on a [Kai Code Bridge](/documentation/guides/kai-code-bridge) machine, stdio servers run on that machine, so they can reach tools and databases on your local network.