Model Context Protocol

Deliver Selected Board Context

Connect an MCP-compatible client to read cards, create tasks, add comments, and track progress within its approved board scopes. You select the context that applies to the task.

Get Started

Server Configuration

MCP Server

Server URL

https://app.kardbrd.com/mcp/

Transport

HTTP (JSON-RPC)

OAuth 2.0 Authentication (with PKCE)

Authorization Server

https://app.kardbrd.com/oauth

Available Scopes

board:read : Read access to boards, cards, lists, and comments

board:write : Create, update, and delete boards, cards, lists, and comments

Setup Guides

Choose a client, add the server configuration, and complete OAuth authorization.

Claude Code Recommended

Add this server to your settings. The first connection starts the OAuth authorization flow.

Add to your MCP settings:

{
  "mcpServers": {
    "kardbrd": {
      "type": "http",
      "url": "https://app.kardbrd.com/mcp/"
    }
  }
}

Run claude mcp add or edit ~/.claude/settings.json.

Cursor

Add this server entry to your MCP configuration and authorize the first connection.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "kardbrd": {
      "url": "https://app.kardbrd.com/mcp/",
      "transport": "http"
    }
  }
}

Windsurf

Add this server entry to your Windsurf configuration. The OAuth prompt appears on the first connection.

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "kardbrd": {
      "serverUrl": "https://app.kardbrd.com/mcp/"
    }
  }
}

ChatGPT

Connect from ChatGPT settings without a config file.

Open ChatGPT Settings, then Connections
Click "Add MCP Server"
Enter server URL: https://app.kardbrd.com/mcp/
Complete the OAuth authorization flow

Other MCP Clients

Use these settings for another MCP-compatible client:

Server URL: https://app.kardbrd.com/mcp/

Transport: HTTP (JSON-RPC)

Auth: OAuth 2.0 + PKCE (https://app.kardbrd.com/oauth)

The server supports dynamic client registration and does not require pre-registration.

Available Tools

The server provides board operations within approved OAuth scopes. Your team chooses the relevant cards and keeps their context correct and current.

Boards

List authorized boards, get board details, and view available activity.

Cards

Create, read, update, move, and archive cards when the approved scope permits each action.

Checklists

Add checklists to cards, create todo items, mark them complete. Progress stays on the card.

Comments

Add comments, read available discussions, and react with emoji on cards in scope.

Attachments

Attach files and markdown documents to cards. Keep relevant research, plans, and supporting material with the task.

Links

Connect cards to pull requests, documents, external resources, and related cards.

Protocol Features

Dynamic Client Registration

MCP clients can register during the authorization flow.

OAuth 2.0 with PKCE

OAuth 2.0 follows OAuth 2.1 security requirements, enforces PKCE, and issues tokens for approved scopes.

Granular Permissions

Choose board:read or board:write access and revoke authorization from your account settings.

Simple HTTP Transport

The server uses JSON-RPC over HTTP, which keeps the transport configuration direct and inspectable.

Deliver Context Through MCP

Connect a compatible client, select the relevant board material, and keep it current as the project changes.

Get Started

Questions? [email protected]