Remote MCP for Kanban AI boards—manage projects, tasks, and comments from AI tools.
Connect Remote server
claude mcp add --transport http kanban-ai https://kanbanai.dev/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>" --header "X-Supabase-Access-Token: <X_SUPABASE_ACCESS_TOKEN>" --header "X-MCP-API-Key: <X_MCP_API_KEY>"
{
"mcpServers": {
"kanban-ai": {
"url": "https://kanbanai.dev/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>",
"X-Supabase-Access-Token": "<X_SUPABASE_ACCESS_TOKEN>",
"X-MCP-API-Key": "<X_MCP_API_KEY>"
}
}
}
}
{
"servers": {
"kanban-ai": {
"type": "http",
"url": "https://kanbanai.dev/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>",
"X-Supabase-Access-Token": "<X_SUPABASE_ACCESS_TOKEN>",
"X-MCP-API-Key": "<X_MCP_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://kanbanai.dev/api/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Supabase access token for the signed-in Kanban AI user. Format: Bearer <access_token>. Obtain from the in-app Connect page (/connect) or GET /api/mcp-setup. |
X-Supabase-Access-TokenOptional, secret | Alternative to Authorization when your MCP client cannot send a Bearer header. Same Supabase access token value. |
X-MCP-API-KeyRequired, secret | Shared deployment secret when MCP_API_SECRET is configured on the host (production uses this). Obtain from the in-app Connect page or GET /api/mcp-setup. |
Details
| Endpoint | https://kanbanai.dev/api/mcp (Streamable HTTP) |
| First published | 10 Jul 2026 |
| Last updated | 10 Jul 2026 |
| Registry name | io.github.orholam/kanban-ai |
More productivity servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
