MCP servers

No account yet? You do not need one to connect. Give your agent the front door, with no token:

claude mcp add --transport http kaiku https://app.kaiku.tech/mcp

{
  "mcpServers": {
    "kaiku": { "type": "http", "url": "https://app.kaiku.tech/mcp" }
  }
}

Then ask it to sign you up. Connected like this it has four tools and nothing else, and it takes you through the steps:

1. It tells you what Kaiku is and what it costs, and shows you the terms of service and the privacy policy. It asks whether you agree — only your yes lets it go on.
2. It asks for your email address, your name and a name for your company, and finds a free address for it, such as acme.kaiku.tech.
3. We email you a 6-digit code. Read it to the agent. It lives 15 minutes and allows 5 attempts.
4. The agent gets your account, your company on the free trial with a first project, and an MCP token for it — shown once.
5. It writes the token into its MCP configuration and reconnects. The new connection is you, in your company, with every tool below.

The reconnect is needed because the first connection has nobody behind it and cannot become you. Your account has no password: on the web, sign in with Google or Apple at the same address, or set a password with Forgot password. If you did not sign up through an agent and got our welcome letter, revoke the token in Settings → Connect over MCP.

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>" }
    }
  }
}

Grok connects to Kaiku as a custom connector. Nothing to install and no token to copy: you sign in to Kaiku once, in the window Grok opens.

1. Open grok.com/connectors and press New Connector, then Custom.
2. Give it a name — Kaiku — and the address https://app.kaiku.tech/mcp.
3. Grok opens Kaiku’s sign-in. Sign in, choose your company if you have more than one, and allow the connection.
4. In a chat, turn the Kaiku connector on and ask, for example, «What is waiting on me in Kaiku?» or «Create an issue in project ABC: check the September invoices».

On Grok Business and Enterprise a team admin adds the connector first, in the xAI console; after that each member signs in to Kaiku as themselves. Grok works with your rights in Kaiku — what you may read and change, and nothing else. To cut it off, remove the connector in Grok.

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. From your own disk, by path: pm-files.
• 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 server above runs in Kaiku, so it cannot read a file on your disk: an assistant can only type the file out into the conversation, which is slow for a screenshot and refused past 512 KB when reading one back. pm-files is a small companion server that runs on your computer. It attaches files to issues and wiki pages by their path and saves attachments into a folder, and the file never passes through the conversation.

• attach_to_issue, attach_to_wiki_page — attach files by path, up to 100 MB each. For a page, the answer gives the line that shows the file in the page’s text.
• save_issue_attachment, save_wiki_attachment — save an attachment into a folder, so a page can be copied with its pictures.
• readable_roots — which folders it may use, and which workspace it talks to.

Connecting it

1. Install Node.js 18 or newer, if you do not have it.
2. In Settings → Connect over MCP, press Generate token, then Copy. Do not paste it anywhere.
3. Open a terminal in your project’s folder and run the line for your client. The same tab, under Files from this computer, shows these lines with your address already in them.
4. Restart the client, and ask the assistant to call readable_roots.

# Claude Code
curl -fsSL https://<workspace>.kaiku.tech/api/mcp/local-files/install.sh | bash

# Claude Desktop
curl -fsSL https://<workspace>.kaiku.tech/api/mcp/local-files/install.sh | bash -s -- --client claude-desktop

# Cursor
curl -fsSL https://<workspace>.kaiku.tech/api/mcp/local-files/install.sh | bash -s -- --client cursor

The script takes the token from the clipboard, checks it against your workspace and only then writes it into the client’s own config; if the check fails, nothing is written. It never prints the token. An assistant never needs it either: if one asks for your token to set this up, do not give it.

Kaiku’s own MCP server knows about pm-files. Ask your assistant to attach a file from your computer: if pm-files is not connected, it will show you the command for your workspace (the local_files_setup tool).

Which folders it may use

pm-files reads files only from its roots and saves only into them. That limit is what keeps it from being a way to send any file on the machine, so the defaults are narrow: the folder you ran the command in, the system temporary folder (where browsers and screenshot tools put files) and, for Claude Code, its own working folder. Your home folder is never a root by default — run the command from a project folder, not from ~.

To choose the folders yourself, name them before bash, separated by colons. Running the command again replaces the previous setup:

curl -fsSL https://<workspace>.kaiku.tech/api/mcp/local-files/install.sh | PM_FILES_ROOTS="$HOME/screenshots:$HOME/work" bash

By hand, and on Windows

The script is for macOS and Linux. Elsewhere, download the server from your workspace — https://<workspace>.kaiku.tech/api/mcp/local-files/server.mjs — and add it to your client’s MCP config. There the token is typed into the config file itself, which stays on your computer:

{
  "mcpServers": {
    "pm-files": {
      "command": "node",
      "args": ["C:\\Users\\you\\pm-files\\server.mjs"],
      "env": {
        "PM_API_URL": "https://<workspace>.kaiku.tech",
        "PM_TOKEN": "<token>",
        "PM_FILES_ROOTS": "C:\\Users\\you\\work"
      }
    }
  }
}

On Windows, separate several roots with ; rather than :.

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.