Your AI assistant,
powered by your data.

Set up in minutes

Point your AI assistant at the Manager Toolkit MCP server and you're ready to go. No complex configuration, just add the server URL, authorise your account, and start asking questions in plain English.

• Works with Claude Desktop, Claude.ai, Cursor, and any MCP-compatible client
• One server URL to remember: https://mcp.manager-toolkit.com/mcp
• Uses Streamable HTTP transport, the modern standard for remote MCP servers
• No new accounts or API credentials to manage for most clients, just your existing Manager Toolkit login

{
  "mcpServers": {
    "managers-toolkit": {
      "url": "https://mcp.manager-toolkit.com/mcp"
    }
  }
}

Natural language access to your data

Once connected, your AI assistant can read and write your Manager Toolkit data on demand. Ask about overdue actions, get a summary of a team member's catchups, or create a follow-up. The AI handles the tool calls automatically.

• Read actions, catchups, targets, teams, surveys, retrospectives, and more
• Create actions, log meeting notes, and update records without switching apps
• Each tool call is transparent so you can see exactly what data was fetched or created
• Combine MCP with AI's reasoning: “Summarise last month's catchups with Alex and suggest follow-ups”

Secure OAuth authentication

Manager Toolkit MCP uses standard OAuth 2.0 with PKCE, the same secure flow used by major platforms. Your AI assistant will prompt you to authorise the first time it needs access. No passwords are ever shared.

• OAuth 2.0 with PKCE: no client secrets stored in your AI assistant config
• Sign in with your existing Manager Toolkit account, no separate credentials needed
• Issued tokens appear in your Profile settings so you always know what has access
• Revoke any token instantly and the connection is cut immediately

API key authentication for automations

Building a custom integration or a fully automated workflow? Use an API key instead of OAuth for machine-to-machine access. Generate keys from your Profile settings and pass them in the request headers. No browser flow needed.

• Create named API keys from your Profile settings page
• Pass the key as an Authorization: Bearer header in your MCP client config
• Ideal for scheduled automations, CI/CD pipelines, or server-side integrations
• Each key is scoped to your account, so you can revoke individual keys without affecting other integrations

{
  "mcpServers": {
    "managers-toolkit": {
      "url": "https://mcp.manager-toolkit.com/mcp",
      "headers": {
        "Authorization": "Bearer mt_live_xxxxxxxxxxxx"
      }
    }
  }
}

Everything you need to connect

MCP brings your management data to wherever you already work, with no context-switching, no copy-pasting, and no extra apps.