MCP Integration

New to MCP? Follow these steps in order. The whole setup usually takes about five minutes.

DevvyBoard exposes a Model Context Protocol (MCP) server that AI assistants can call as tools. Once configured, your AI assistant can:

• List all projects your API key is authorised for
• Read the full Kanban board — columns and cards — for any project
• Fetch individual card details including description, priority, and deadline
• Create cards in any column (write scope required)
• Update card title, description, priority, or deadline (write scope required)
• Move a card to another column (write scope required)
• Delete a card (write scope required)

API keys are scoped to specific projects and carry either read or read-and-write permissions. You can create and revoke keys at any time.

Add the DevvyBoard MCP server to your Cursor configuration. Cursor reads MCP servers from ~/.cursor/mcp.json (global) or a .cursor/mcp.json file at the root of any project (project-scoped).

{
  "mcpServers": {
    "devvyboard": {
      "command": "npx",
      "args": ["-y", "devvyboard-mcp"],
      "env": {
        "DEVVYBOARD_API_KEY": "dbk_live_YOUR_KEY_HERE"
      }
    }
  }
}

Claude Code uses a claude_desktop_config.json file for MCP configuration. Add the DevvyBoard server under the mcpServers key.

Config file location by platform:

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

{
  "mcpServers": {
    "devvyboard": {
      "command": "npx",
      "args": ["-y", "devvyboard-mcp"],
      "env": {
        "DEVVYBOARD_API_KEY": "dbk_live_YOUR_KEY_HERE"
      }
    }
  }
}

Codex CLI supports MCP servers via a codex.json configuration file in your project root or home directory.

{
  "mcpServers": {
    "devvyboard": {
      "command": "npx",
      "args": ["-y", "devvyboard-mcp"],
      "env": {
        "DEVVYBOARD_API_KEY": "dbk_live_YOUR_KEY_HERE"
      }
    }
  }
}

Alternatively, export the key as an environment variable before running Codex:

export DEVVYBOARD_API_KEY=dbk_live_YOUR_KEY_HERE
codex

The MCP server exposes the following tools. Each tool call targets the DevvyBoard REST API on your behalf using the API key supplied in your configuration.

Every API key carries one of two scope levels. You choose the scope when creating the key from Connectivity.

Each HTTP call under /api/integrations/v1/* counts toward your quota (MCP tools map one-to-one). Exceeding a limit returns HTTP 429 with rate-limit headers — not a silent throttle.