MCP servers

The server is at https://<workspace>.kaiku.tech/mcp (streamable HTTP) and signs in with a token in the Authorization: Bearer header. It is built in: nothing to install.

The Connect over MCP tab in Settings shows your exact address, makes the token (see Connecting a tool) and gives the lines to paste, with the token already in them. For Claude Code:

claude mcp add --transport http kaiku https://<workspace>.kaiku.tech/mcp \
  --header "Authorization: Bearer <token>"

For a client configured by a file — Claude Desktop, Cursor and others:

{
  "mcpServers": {
    "kaiku": {
      "type": "http",
      "url": "https://<workspace>.kaiku.tech/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

The full list, with each tool marked as reading or writing, is under Available tools on the same tab. In short:

• Issues: search, read, create, edit, move to another project, set a project’s own columns; comments; links between issues.
• Questions: ask a person a question with answer options, and read the answer.
• The wiki: search, read, create, edit and delete pages; comments; tie a page to an issue.
• Files: attach to an issue or a page (up to 20 MB through MCP), read back, delete.
• Projects: list, and — for a project lead or an administrator — its own columns and automatic rules.
• Agent runs: record what an agent spent on an issue — tokens by kind and machine time — and read it back.
• Credentials attached to an issue or a page: list them, and reveal one.

• The server acts with your permissions, and a token limited to one project limits every tool to it.
• A read-only token may call only the reading tools. Revealing a credential is not one of them.
• Its search refuses a query it cannot fully read, instead of widening it — see Search (JQL).
• Its answers and refusals are in English, whatever language the workspace speaks.

The widely used open-source MCP server for the incumbent tracker and wiki works against Kaiku unchanged, both halves with one token. The names below are that project’s own and are given only because they have to be typed as they are; Kaiku is not affiliated with that vendor or that project.

Both addresses are your bare workspace address. The server then uses the self-hosted edition’s way of signing in, with the token as a personal access token:

{
  "mcpServers": {
    "tracker": {
      "command": "docker",
      "args": ["run", "--rm", "-i",
        "-e", "JIRA_URL", "-e", "JIRA_PERSONAL_TOKEN",
        "-e", "CONFLUENCE_URL", "-e", "CONFLUENCE_PERSONAL_TOKEN",
        "ghcr.io/sooperset/mcp-atlassian:latest"],
      "env": {
        "JIRA_URL": "https://<workspace>.kaiku.tech",
        "JIRA_PERSONAL_TOKEN": "<token>",
        "CONFLUENCE_URL": "https://<workspace>.kaiku.tech",
        "CONFLUENCE_PERSONAL_TOKEN": "<token>"
      }
    }
  }
}

• Without Docker: uvx mcp-atlassian, with the same four settings in its environment.
• For the wiki alone, leave out the two JIRA_ settings.
• If a client insists on the cloud layout of the wiki, give it …kaiku.tech/wiki as the wiki address.
• That server has no tool for creating a project; Kaiku’s own server does, for administrators.
• What it can and cannot do through Kaiku follows from Tracker API and Wiki API.