Skip to content

Developers

MCP server

Connect Claude Code, Claude Desktop, Cursor and other AI assistants to Deckbell to find, create and update issues, comment and post in channels.

Deckbell runs an MCP (Model Context Protocol) server, so AI assistants such as Claude and Cursor can work with your Deckbell workspace: find the issues assigned to you, create and update issues, comment, and post in channels.

  • Server URL: https://api.deckbell.com/mcp (Streamable HTTP)
  • Sign-in: an API token, sent as a Bearer token

The quickest way to set it up is Integrations → MCP server in the app: it makes a token for your assistant and fills it into ready-to-paste setup for each client.

Create a token for your assistant

In Integrations → MCP server choose Create a token for MCP, or make one in Settings → API tokens. The assistant acts as you, so it can only do what the token's scopes and your role allow; tick only Read scopes if you just want it to look things up. Give it its own token so you can revoke it separately.

Claude Code

Run this in a terminal, with your token:

claude mcp add --transport http deckbell https://api.deckbell.com/mcp \
  --header "Authorization: Bearer dkb_your_token"

Claude Desktop

Open Settings → Developer → Edit config, add Deckbell to claude_desktop_config.json, and restart Claude. This uses mcp-remote, so it needs Node.js installed:

{
  "mcpServers": {
    "deckbell": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.deckbell.com/mcp", "--header", "Authorization:${DECKBELL_AUTH}"],
      "env": { "DECKBELL_AUTH": "Bearer dkb_your_token" }
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "deckbell": {
      "url": "https://api.deckbell.com/mcp",
      "headers": { "Authorization": "Bearer dkb_your_token" }
    }
  }
}

Other MCP clients that support remote (Streamable HTTP) servers with custom headers work the same way: the URL above and an Authorization: Bearer header.

Tools

ToolWhat it doesNeeds scope
whoamiWhich person, workspace and scopes the connection usesany
list_projectsThe workspace's projects and their keysprojects:read
list_statuses_and_labelsA project's statuses and labelsprojects:read or issues:read
search_issuesSearch and filter issuesissues:read
list_my_issuesYour open issues (or all, with done ones)issues:read
get_issueAn issue's details and commentsissues:read
create_issueCreate an issueissues:write
update_issueChange status, priority, assignee, labels, title, description, estimate; archiveissues:write
add_commentComment on an issue, as youcomments:write
list_channels, read_channelChannels you're in and their recent messageschat:read
post_messagePost in a channel, as youchat:write
list_membersPeople in the workspacemembers:read

The assistant only sees the tools its token can use.

Things to ask

  • "What's assigned to me in Deckbell?"
  • "Create a bug in WEB: the checkout button does nothing on Safari. High priority."
  • "Move WEB-42 to In Progress and add a comment that I'm on it."
  • "Summarize what was said in #general today."

Comments and messages the assistant writes appear under your name, and mentioning an AI agent ("@Coder take this") in a comment starts it, as in the app. Calls count towards the token's rate limit. Revoke the token in Settings → API tokens to disconnect the assistant.

Still stuck? Email us and we’ll help.