MA

Mantisbt MCP

Work with MantisBT issues from Claude and other MCP clients: read, create, update. Offline semantic search, compact summaries, toolsets.

Grade A Local · stdio API key 44 tools v1.18.4 · 13 Nov 2026 MIT
No reviews yet by @dpeschnpm 12,612 Runs on your machine, nothing hosted
96/100
trust score
164
downloads a day
local
runs on your machine
4k
downloads in 30d

What it does

Connects Claude Code, Claude Desktop and other MCP clients to the MantisBT REST API. Read, create and update issues, notes, attachments, relationships, tags and versions without leaving the editor.

What it covers

  • Issues: fetch one or up to 50 at once, filter lists, create, update, delete
  • Notes, attachments, relationships, tags and monitors — including editing existing notes and adding watchers in the same call as an update
  • Projects and versions: categories, members and versions in one call; create, rename, release and obsolete versions
  • Metadata: enum values, available fields and your own profile, cached locally

Offline semantic search

search_issues finds issues by meaning, not just by wording: "duplicate entries in the invoice list" also finds reports that say "shown twice" or "double records". The embedding model runs locally — no OpenAI key, no external API. Ranking combines semantic similarity with keyword matching (BM25), so identifiers, error codes and version numbers are found exactly. The index updates incrementally on start. Enable with MANTIS_SEARCH_ENABLED=true.

Fewer tokens

The server counts and projects fields itself, so the model gets a compact answer instead of raw issue lists:

  • list_issues with group_by: "status" — a status overview of 604 issues in 165 tokens instead of about 1.27 million
  • get_issue with select — five issues with only the fields you need, 96 % smaller
  • response: "short" on create_issue and update_issue returns only the core and the changed fields

Control over what the model can do

  • MANTIS_TOOLSETS offers only the tool groups you list, e.g. issues,notes,meta
  • MANTIS_DISABLE_DESTRUCTIVE=true hides every delete and remove tool
  • HTTP mode binds to 127.0.0.1 by default and refuses to start without a bearer token (MCP_HTTP_TOKEN)

Works with localized installations

Status, priority, severity and the other enum fields accept canonical English names, localized names or numeric IDs. A German or French MantisBT works the same way as an English one, and status filters match by ID rather than by label.

Resources and prompts

  • Resources such as mantis://projects/{id} (project with users, versions and categories) and mantis://enums for clients that read MCP resources
  • Prompt templates for a structured bug report, a feature request, an issue summary and a project status report

Requirements

  • Node.js 22 or newer
  • MantisBT 2.23+ with the REST API enabled
  • A MantisBT API token (My Account → API Tokens)

Install via npx -y @dpesch/mantisbt-mcp-server and set MANTIS_BASE_URL and MANTIS_API_KEY. Stdio is the default transport; Streamable HTTP is available with TRANSPORT=http. Open source under the MIT license.

Quickstart

# 1 — add it to Claude Code claude mcp add --scope user --env 'MANTIS_BASE_URL=${MANTIS_BASE_URL}' --env 'MANTIS_API_KEY=${MANTIS_API_KEY}' --transport stdio mantisbt-mcp '--' npx -y @dpesch/mantisbt-mcp-server # 2 — ask your agent for something these tools do # search_issues, get_search_index_status, rebuild_search_index and 41 more

It needs MANTIS_BASE_URL, MANTIS_API_KEY: this reads them from your environment, so export them first.

Mantisbt costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher
DP
@dpesch1 server
1 category
All 1 server
More in this category

See also

See all