Kanban AI

io.github.orholamPublished by GitHub account orholamv1.0.0Updated Oct 24, 2026

Remote MCP for Kanban AI boards—manage projects, tasks, and comments from AI tools.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for Kanban AI boards, letting an assistant manage projects, tasks and comments from AI tools.

What you can do
Manage Kanban AI projects, tasks and comments through the remote MCP endpoint, so an assistant can work with board content directly from AI tools. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Use it when you already work in Kanban AI and want an AI assistant to read or update your boards, projects, tasks and comments without switching apps.
Requirements
A remote endpoint at kanbanai.dev over streamable HTTP, with OAuth required. A Supabase access token is sent in the Authorization header as a Bearer token, or in X-Supabase-Access-Token if the client cannot send Bearer headers. When the host configures MCP_API_SECRET, a shared X-MCP-API-Key is also required. Credentials come from the in-app Connect page or the setup API endpoint.
Before you install
All three headers are secrets tied to your signed-in Kanban AI account; treat them like passwords and do not share them. The server can change board data such as projects, tasks and comments, so review assistant actions before relying on them. Board content is sent to the remote kanbanai.dev service.

Installation

In SourceWeft

  1. Open Kanban AI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.orholam%2Fkanban-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "kanban-ai": {
      "type": "http",
      "url": "https://kanbanai.dev/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.