Connect Claude to your board: Bundlle's MCP server
Every workspace now ships its own MCP server, so Claude Code, Cursor and claude.ai can read the board and move the work.
Bundlle has always read your GitHub activity and moved tasks on its own. But more and more of the work itself now happens inside AI tools like Claude Code and Cursor, and those tools could not see the board at all.
Now they can. Every Bundlle workspace ships with its own MCP server: one URL you add to your AI tool of choice, and the board becomes something your agent can read and act on.
What MCP is, in one paragraph
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to outside tools and data. An app exposes an MCP server; assistants like Claude Code, Cursor and claude.ai connect to it and gain a set of typed tools they can call during a conversation. Bundlle exposes one such server per workspace.
What your agent can do
Reading: list projects and tasks, pull a task's full detail with comments and blockers, search across the workspace, see what is assigned to you, and read the AI activity feed to learn why a card moved.
Writing: create tasks with assignees, priority and deadline, move tasks across the board, change assignees, leave comments that @mention teammates, and chain blocked-by dependencies. Every write shows up on the live board instantly, exactly like an edit made in the app.
Set up in about a minute
Copy your workspace's MCP URL from Settings, then Integrations, then MCP server. In Claude Code, run the one-line add command shown on that page and sign in when the browser opens. In Cursor, paste the ready-made snippet into mcp.json. On claude.ai, add the URL as a custom connector under Settings and Connectors.
There are no API keys. The first connection opens a normal browser sign-in with your Bundlle account, and the settings page shows a green tick once your client is talking to the workspace.
Your role is the permission model
The connection acts as you, never as a super-user. Owners and admins see the whole workspace, members see the projects they belong to, and viewers connect read-only. Each URL is scoped to exactly one workspace, so an agent connected to one client's board can never touch another's.
The loop this closes
Ask your agent what you are assigned, pick a task, and ship the fix. The push lands in GitHub, Bundlle's commit matching recognises the work, and the card moves on its own, with a confidence score and a reason in the activity feed.
The board stays honest no matter who, or what, is doing the work. That was always the point.
Let your board keep up with you.
Connect a GitHub repo and watch the board start keeping itself current. Free to start, no card required.