MCP Integration

Getting started

1. Create a personal access token

   Go to Settings → Integrations, switch to Account integrations, and create a token in the MCP section. It is shown once. You can keep up to 10 active tokens.

2. Point the client at the www host

   Paste the snippet for your client below. Replace YOUR_TOKEN_HERE. Public analysis tools also work with no token.

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project. Cursor reads url plus headers for a remote HTTP server.

{
  "mcpServers": {
    "gehirn": {
      "url": "https://www.gehirn.md/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Claude Code

Register the server from the shell. --header sends the bearer token. Check it with claude mcp list.

claude mcp add --transport http gehirn https://www.gehirn.md/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN_HERE"

VS Code

VS Code uses a top-level servers object, not mcpServers. Put this in .vscode/mcp.json or in your user mcp.json.

{
  "servers": {
    "gehirn": {
      "type": "http",
      "url": "https://www.gehirn.md/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Claude Desktop

claude_desktop_config.json launches local commands. It does not take a remote url field. This config runs mcp-remote and puts the bearer token in env, because a space inside args is mangled on some desktops.

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "gehirn": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.gehirn.md/api/mcp",
        "--header",
        "Authorization:${GEHIRN_TOKEN}"
      ],
      "env": {
        "GEHIRN_TOKEN": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Restart Claude Desktop after saving. Settings → Connectors → Add custom connector can point at the same URL, but that screen does not take a bearer token, so account tools stay unavailable there.

Tools

Twenty-two tools. Account tools need a trialing or active plan. Article credits and the other quotas of that plan still apply. There is no separate planning tool: content plans come out of start_write.

Questions and draft review

1. start_research or start_write returns a job. If it is still running, poll get_job.
2. When the job needs input, get_job includes the questions. Show them to the person, then send the answers with answer_job.
3. When a draft is included, show that full draft before asking for approval. Approving or requesting one revision does not spend another article credit.

Security

• A token can use every account tool on that account. It cannot read another account.
• Do not commit tokens or paste them in public channels.
• Revoke a token from Settings → Integrations. The limit is 10 active tokens.
• generate_company_md, get_cached_company_md, analyze_tone_of_voice, and analyze_design_system work without a token and are rate-limited by IP.

Credits

start_research, start_write, and rewrite_article each use one article credit. start_research also runs at most once per project per day. Reading projects, the Tresor, or job status does not use a credit. Without a trialing or active plan, account tools return “Start a plan.”

Troubleshooting

• 401. The bearer token is missing, revoked, or not a gehirn.md token. Create a new one and put it in the Authorization header as Bearer followed by a space.
• Authorization disappears. The client called https://gehirn.md and followed a redirect. Use https://www.gehirn.md/api/mcp. Redirects drop the Authorization header.
• Start a plan. The account has a token, but the subscription is not trialing or active.