Connect your AI assistant

MCP server · https://api.getdevboard.app/mcp

devBoard speaks MCP, the protocol coding assistants use to reach other tools. Once it is connected, your assistant can read the item it is working on, open new ones, comment, move cards and log time. It works as you, inside one workspace, and can do exactly what your role allows.

1. Create a token

Open devBoard and go to Settings → Developer.
Tap New token and name it after the tool, like "Claude Code".
Copy it. It is shown once; after that you only see its first few characters.

Each token belongs to the workspace you had open when you made it. Guests can read a workspace but cannot create tokens.

2. Add devBoard to your assistant

Swap <your-token> for the token you copied.

Claude Code

claude mcp add --transport http --scope user devboard https://api.getdevboard.app/mcp \
  --header "Authorization: Bearer <your-token>"

--scope user makes it available in every project. Leave it out to add it to the current project only. Check it with /mcp inside Claude Code.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "devboard": {
      "url": "https://api.getdevboard.app/mcp",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

VS Code

Add this to .vscode/mcp.json. VS Code asks for the token the first time and keeps it out of the file, so the file is safe to commit:

{
  "inputs": [
    { "type": "promptString", "id": "devboard-token", "description": "devBoard token", "password": true }
  ],
  "servers": {
    "devboard": {
      "type": "http",
      "url": "https://api.getdevboard.app/mcp",
      "headers": { "Authorization": "Bearer ${input:devboard-token}" }
    }
  }
}

Claude Desktop

Claude Desktop only starts local commands from its config, so it reaches devBoard through mcp-remote (Node.js required). Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "devboard": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.getdevboard.app/mcp",
        "--header", "Authorization:${DEVBOARD_AUTH}"],
      "env": { "DEVBOARD_AUTH": "Bearer <your-token>" }
    }
  }
}

Restart Claude Desktop afterwards.

Anything else

Any client that supports remote MCP over Streamable HTTP works. The address is https://api.getdevboard.app/mcp, and the token goes in an Authorization: Bearer header.

3. Try it

"What's on my plate today?"
"Start APP-42." It assigns you, moves the card to in progress, starts your timer and gives you the branch name.
"Break the onboarding epic into tasks and give each one a due date next week."
"File a bug: the login button does nothing on iPad. Urgent, assign it to me."
"Comment on APP-42 that the fix is in review and mention @[Ana]."
"How much time did I log this week, per ticket?"
"Done with APP-42, move it to Code review."

Open a pull request from the branch it gave you and the PR links itself to the item. Setting that up is covered below.

What your assistant can do

Find and read	Look up the workspace (projects, columns, labels, releases, people), search items by column, assignee, label, type, priority, release or due date, read an item in full with its comments and pull requests, see My Work, and run saved views.
Tickets	Create epics, tasks and subtasks, edit any field, reassign, relabel, move between columns, archive and restore.
Comments	Add, edit and delete your own comments. `@[Name]` notifies a teammate.
Your day	Start and finish work in one step, run your timer, log time after the fact, read your timesheet, check your inbox and manage your personal to-dos.
Releases	Plan and ship releases and add labels, if you are an admin.

It cannot delete items, change workspace settings, or manage members and invites. Those stay in the app.

Keeping it safe

A token works as you, with your role. If you are a member, the assistant can do what a member can and nothing more.
It sees one workspace, the one it was made in. Your personal to-do list is yours across workspaces, so the assistant can reach that too.
Revoke a token in Settings → Developer and it stops working at once. Revoke it the moment it ends up somewhere it shouldn't.
devBoard only keeps a hash of the token. If you lose it, make a new one.

Link pull requests from GitHub

A pull request that mentions an item key (APP-123) in its title or branch shows up on that item, and it can move the card when it opens, merges or closes. A workspace admin sets this up once per repository:

In devBoard, open Settings → Developer, copy the webhook URL and save a webhook secret.
In GitHub, open the repository's Settings → Webhooks → Add webhook.
Paste the URL as the Payload URL and set Content type to application/json. GitHub defaults to form-encoded, which devBoard rejects.
Enter the same secret.
Choose Let me select individual events, tick Pull requests only, and save.

Back in devBoard, choose which column a card moves to when a pull request opens, merges, or closes without merging.

Without MCP

The same token works on a small REST API at https://api.getdevboard.app/dev/v1, for scripts and CI:

curl -H "Authorization: Bearer <your-token>" https://api.getdevboard.app/dev/v1/items/APP-42

curl -X POST -H "Authorization: Bearer <your-token>" -H "Content-Type: application/json" \
  -d '{"category":"done"}' https://api.getdevboard.app/dev/v1/items/APP-42/status

Routes: GET me, GET projects, GET items?project=&q=, GET items/{KEY}, GET items/{KEY}/pulls and POST items/{KEY}/status.

Questions or something missing? hello@getdevboard.app