Connect a client

Setting up an agent takes three steps in Taskgert, then one in your MCP client.

1. Create a bot

Open Bots in the sidebar (you need a workspace) and create a bot. Give it a name people will recognise in the activity, such as "Claude".

2. Add the bot to a project

Open the project, go to Members, and add the bot with the role it needs — usually EDITOR. The bot only ever sees the projects it was added to.

3. Create a token

On the bot's page, create a token and choose its scopes (see Concepts). Copy the token: it is shown only once.

4. Configure your client

The server speaks Streamable HTTP at https://mcp.taskgert.com/mcp (for a self-hosted Taskgert, use your own MCP address), with the token as a bearer header.

Claude Code

claude mcp add --transport http taskgert https://mcp.taskgert.com/mcp \
  --header "Authorization: Bearer tgt_live_…"

Add --scope project to share the server (not the token) with your repository, or --scope local to keep it to yourself. Check it with claude mcp get taskgert.

Cursor

In ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "taskgert": {
      "url": "https://mcp.taskgert.com/mcp",
      "headers": { "Authorization": "Bearer tgt_live_…" }
    }
  }
}

Claude Desktop

Claude Desktop runs local servers from claude_desktop_config.json; bridge to Taskgert with mcp-remote:

{
  "mcpServers": {
    "taskgert": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.taskgert.com/mcp",
        "--header",
        "Authorization: Bearer tgt_live_…"
      ]
    }
  }
}

Restart Claude Desktop after editing the file.

Any other MCP client

Point it at the URL above with the header Authorization: Bearer <token>. The server is stateless: no session to open or close, every request stands alone.

5. Try it

Ask your agent:

Call whoami, then list my projects and show me the board of the first one.

whoami tells the agent which bot it is and what its token allows — the quickest way to check the setup.