MCP Integration
Overview
The Model Context Protocol (MCP) integration allows you to connect your MindBacklog workspace directly to AI assistants like Claude Desktop, Claude Code, Cursor, and other MCP-compatible IDEs. This lets your AI assistant read your PRDs, user stories, customer signals, and feature context natively without you having to manually copy and paste.
Use Cases
By connecting MindBacklog to your AI tools, you unlock powerful agentic workflows:
- VibeCoding: Ask Claude Desktop to "Implement the UI components for the 'Dark Mode' feature in MindBacklog." The AI will automatically query the PRD and user stories from MindBacklog to understand the requirements and begin writing code.
- Context Retrieval: Quickly ask your IDE "What are the latest customer signals regarding our billing page?" Your AI will fetch real-time signals from MindBacklog's Intelligence Hub.
- Architecture Planning: Ask your agent to review your codebase and check if it meets the acceptance criteria defined in a specific MindBacklog story.
Setting up Claude Desktop
Claude Desktop currently requires a local bridge to connect to remote HTTP servers. We provide the official @mindbacklog/mcp package to make this seamless.
Generate an MCP Token
In MindBacklog, navigate to your Developer Settings and generate a new MCP Token. Copy this token (it starts with mb_).
Update Claude Desktop Config
Open Claude Desktop, go to Settings > Developer > Edit Config. This will open your claude_desktop_config.json file.
Add the following configuration, replacing YOUR_TOKEN_HERE with your actual token:
{
"mcpServers": {
"mindbacklog": {
"command": "npx",
"args": ["-y", "@mindbacklog/mcp"],
"env": {
"MINDBACKLOG_TOKEN": "YOUR_TOKEN_HERE"
}
}
}
}
Restart Claude Desktop
Fully quit the Claude Desktop app (Command+Q on Mac) and reopen it. You should see the hammer (🔨) icon in your chat input, indicating the MindBacklog tools are connected!
Setting up Claude Code or Cursor
Tools that natively support remote HTTP MCP servers (like Claude Code or custom agents) don't need the local NPM bridge. You can connect them directly using the Streamable HTTP transport.
Configure your client to point to https://app.mindbacklog.com/mcp using the http or streamable-http type, passing your token in the Authorization: Bearer header. Check your specific client's documentation for the exact syntax.
Security & Tokens
Your MCP tokens have access to your organization's data. Treat them like passwords. If a token is compromised, you can revoke it immediately from your Developer Settings in MindBacklog. Revoked tokens instantly lose all access.