Connect claude.ai to Agenticboard

On claude.ai, Agenticboard is a custom connector: you add it once, sign in, and approve what Claude may reach. There is no token to copy and nothing to keep on disk, because the connection authenticates over OAuth 2.1 and Claude receives a scoped token behind the scenes. From then on Claude reads and drives the same board, tickets and docs your team uses.

Connector URL

https://agenticboard.app/api/mcp/

Auth

OAuth 2.1, no token to paste

Client ID / Secret

Left blank — registered automatically

Set it up

1. 1

   Add the custom connector

   In claude.ai, open Settings → Connectors → Add custom connector. Name it — Agenticboard does nicely — and set the URL to https://agenticboard.app/api/mcp/. Leave the OAuth Client ID and Secret blank; the server registers the client for you.

2. 2

   Approve what Claude may reach

   Click Add, then Connect. You are sent to Agenticboard to sign in and approve the connection. On the consent screen you pick the same three things a token would carry: the access level, which projects Claude may reach, and the documentation scope. Then choose Authorize.

3. 3

   Check that it answers

   Ask Claude to list your projects. You should see the tools the connection is allowed to use: the write tools appear only when you granted read and edit, and the doc tools only when documentation access is on.

Removing the connector revokes the access again, and so does revoking it from Agenticboard. If you would rather use a Personal Access Token, any header-capable client takes one — Claude Code, Cursor and Claude Desktop are set up that way. Both paths hit the same MCP server.

What Claude can do

What you approved decides the shape of the toolset. These are the tools the MCP server exposes.

• Read the board.list_projects, get_board, get_task and list_members give it columns, cards, labels, comments, attachments and testing feedback.
• Move the work along.create_task and update_task open a card or change its title, description, status, priority, type, assignee, deadline, PR URL, version or cycle.
• Follow your process.get_workflow returns the project's ordered steps, and the write tools return the next step to take, so the work happens in the order you set rather than the order it occurs to anyone.
• Check what is already solved.find_resolved searches done tasks and returns how each was fixed, and get_task_history gives one ticket's full trail.
• Read and keep the docs.list_docs, get_doc, create_doc and update_doc work the same pages your team reads. Edits carry a reason into the doc's version history.
• Leave the evidence behind.comment_task, add_test_report and attach_file put the test result and the screenshot on the card, where a reviewer will look for them.
• Find anything.search covers projects, tasks and docs, and get_history with search_history reach the knowledge behind them: doc changes, resolved tickets and captured errors.

The connection acts as you, narrowed by what you approved, and every call it makes is logged under the token's Activity in Agenticboard.

Other guides: Claude Code · Cursor · Claude Desktop · Sentry