MantisBT MCP Server
Let your coding agent create, search, and update MantisBT issues, notes, attachments, and links from the editor instead of context-switching to the web UI.
Overview
MantisBT MCP Server is an MCP server for the Build phase that connects agents to MantisBT for issue, note, file, tag, and relationship management with semantic search.
What is this MCP server?
- stdio MCP server (v1.9.1) via npx @dpesch/mantisbt-mcp-server
- Manage issues, notes, file attachments, tags, and issue relationships through MantisBT REST API
- Semantic search across issue metadata to find related bugs and tasks in natural language
- Configurable metadata cache (MANTIS_CACHE_DIR, default TTL 3600 seconds)
- Requires MANTIS_BASE_URL and MANTIS_API_KEY from MantisBT Profile → API Tokens
- Server version 1.9.1
- Default metadata cache TTL 3600 seconds (1 hour)
- Transport: stdio via npm package @dpesch/mantisbt-mcp-server
What problem does it solve?
Switching between your editor and MantisBT breaks flow when agents cannot read, search, or update the same issues you use for shipping.
Who is it for?
Solo builders or small teams on MantisBT who want agent-driven triage, updates, and backlog search during build and ship.
Skip if: Teams on Jira, Linear, or GitHub Issues only, or hosts without MantisBT REST API and API tokens enabled.
What do I get? / Deliverables
After registration, your agent can query and mutate MantisBT issues—including semantic search—using your REST base URL and API token.
- Agent-callable MantisBT issue, note, file, tag, and relationship operations
- Semantic search results over cached issue metadata
- stdio MCP transport registered in your agent config
Recommended MCP Servers
Journey fit
Issue and backlog management is where solo builders first wire external trackers into agent workflows during active product work. The pm subphase is the canonical shelf for backlog, triage, and release-adjacent issue tooling.
How it compares
MantisBT REST integration via MCP, not a standalone issue-tracking skill or hosted SaaS tracker.
Common Questions / FAQ
Who is MantisBT MCP Server for?
Indie developers and small teams who run MantisBT and want Claude Code or Cursor to manage issues and search the backlog without opening the browser.
When should I use MantisBT MCP Server?
Use it when you are actively building or shipping and need the agent to file bugs, add notes, attach files, or semantically search existing issues.
How do I add MantisBT MCP Server to my agent?
Add the stdio MCP entry with npx @dpesch/mantisbt-mcp-server and set MANTIS_BASE_URL and MANTIS_API_KEY in your agent MCP config.