# Connect other MCP clients to iKanban

Any agent or tool that can call a remote [Model Context Protocol](https://modelcontextprotocol.io) server can work with your iKanban board — Gemini CLI, Codex, your own scripts built on an MCP SDK, or an internal agent. This page lists what such a client needs. For step-by-step setup in the two most common clients, see [Connect Claude Code](/docs/mcp/claude-code) and [Connect Cursor](/docs/mcp/cursor).

The MCP server is included in every paid plan, from Starter up, with no daily call limit (fair use). See [Pricing](/pricing) for the plans.

## The connection details

| Setting | Value |
| --- | --- |
| Server URL | `https://mcp.i-kanban.com/sse` |
| Transport | MCP Streamable HTTP over HTTPS (not the older SSE transport, despite the `/sse` path) |
| Authentication | Header `Authorization: Bearer vk_…` with a personal API key |
| Server name | Any; the examples in these docs use `ikanban-remote` |

Create the key in **Settings → API Keys**. Keys start with `vk_`, are shown once, and act as you: the client sees what you can see and nothing more. Delete the key in the same place to revoke it. The same page has an MCP access switch and an allowed-client list; if a valid key is refused, check those first (changes can take up to five minutes). A key can also be made read-only, which lets a client read but not create or update.

In your client's documentation, look for "add a remote MCP server" or "HTTP MCP server". Most clients take the URL and a set of request headers. If a client offers a choice of transport, pick **HTTP** or **Streamable HTTP**; a client set to SSE fails to connect.

## Check it works

Without a key the server answers `401 Unauthorized`, which tells you the address is right and only the key is missing:

```bash
curl -s -o /dev/null -w "%{http_code}\n" -X POST https://mcp.i-kanban.com/sse
```

Once your client is connected, ask it something that needs the board, using your own team's identifier:

```text
List the open tasks in the ENG team.
```

It should call `list_issues` and reply with the tasks.

## What the server offers

- **Read, create and update** across teams, issues, projects, sprints, releases, documents, folders, comments and tags. The full, current tool list is in the app under **Settings → MCP Servers**.
- **No delete.** Nothing can be deleted over MCP, by design.
- **Human identifiers.** Teams by key (`ENG`), issues by key (`ENG-42`); projects, sprints and documents by the ids the matching `list_*` tool returns.

The [MCP field guide](/docs/mcp/mcp-usage-from-field) covers each tool group and the parameters that trip people up.

Building on the iKanban API from code rather than an agent? The MCP server is the supported external interface; see [Setup and Access](/docs/getting-started/setup) for how keys and access work.