Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MANTIS_BASE_URLYesThe MantisBT site URL, for example https://mantis.example.com. Required.
MANTIS_API_TOKENYesA MantisBT API token for an account with the permissions needed. Required.
MANTIS_READ_ONLYNoOptional flag to block all write calls (POST, PATCH, PUT, DELETE). Default: false.false
MANTIS_ALLOW_HTTPNoOptional flag allowing non-https URLs, except localhost. Default: false.false
MANTIS_ALLOW_DELETENoOptional flag allowing DELETE calls. Default: false (all DELETE calls blocked).false
MANTIS_VECTOR_DB_PATHNoOptional path to the local vector store JSON file. Default: .mantis-vector-store.json..mantis-vector-store.json
MANTIS_EMBEDDING_MODELNoOptional embedding model name. Default: text-embedding-3-small.text-embedding-3-small
MANTIS_EMBEDDING_API_KEYNoOptional API key for the embedding endpoint. Default: none.
MANTIS_EMBEDDING_API_URLNoOptional OpenAI-compatible embedding endpoint URL. Default: local embedder.
MANTIS_RESOLVED_THRESHOLDNoOptional resolved threshold configuration. Default: 80.80
MANTIS_ALLOW_EXTERNAL_EMBEDDINGSNoOptional opt-in for external embeddings. Default: false.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_my_unresolved_assigned_contextB

MAIN FUNCTION: Collects everything about all issues assigned to the user (or to a specific user) that are not yet resolved/closed. Returns the full description, steps to reproduce, additional information, complete notes/comments, custom fields, relationships, tags, attachment metadata, change history, and an executive summary grouped by project/priority/status to give the LLM full context.

get_issue_full_contextB

Gets all details of a specific issue by ID (description, notes, history, attachments, custom fields and relationships).

list_issuesC

Lists and filters MantisBT issues by project, saved filter, assignee (handler), reporter, status or text search.

create_issueC

Creates a new issue in MantisBT.

update_issueB

Updates any field of an existing MantisBT issue (status, assignee/handler, priority, severity, resolution, texts, versions, tags or custom fields).

delete_issueC

Deletes a MantisBT issue by ID.

add_issue_noteC

Adds a note/comment to an issue in MantisBT, with visibility support (public/private) and time tracking.

delete_issue_noteC

Removes a specific note/comment from an issue.

add_issue_relationshipC

Creates a relationship between two issues (e.g. related-to, duplicate-of, parent-of, child-of, has-duplicate).

delete_issue_relationshipC

Removes a relationship between issues.

get_issue_attachmentB

Downloads the content (text or Base64) of a specific issue attachment for inspection by the LLM.

add_issue_attachmentC

Adds an attachment file (Base64) to an existing issue.

attach_issue_tagsC

Attaches one or more tags to an issue.

detach_issue_tagC

Removes a tag from an issue by tag ID.

monitor_issueA

Adds a user (or the authenticated user if omitted) as a monitor/observer of an issue.

list_projectsA

Lists all accessible MantisBT projects, including categories, versions and custom fields.

get_projectB

Gets full details of a specific project by ID.

create_project_versionC

Creates a new version within a MantisBT project.

list_filtersA

Lists all saved filters available to the user in MantisBT.

get_current_userB

Returns the full profile of the authenticated user (/users/me) in MantisBT.

check_mantis_connectionA

Validates connectivity and authentication with the MantisBT REST API (including automatic detection of /api/rest/index.php when mod_rewrite is disabled).

get_mantis_configC

Gets configuration options from the MantisBT server (e.g. status_enum_string, priority_enum_string, workflows).

sync_issues_to_vector_storeA

Collects MantisBT issues, computes vector embeddings (local 256d or external API) and lifecycle metrics (lead time, reopens, assignment ping-pong, stagnation), and persists everything to the local mini vector store for semantic search and efficiency analysis.

search_vector_issuesB

Runs a semantic search by cosine similarity over the MantisBT issue mini vector store, combining embeddings and metadata filters to find recurring bugs, similar root causes or technical history.

analyze_project_efficiencyA

Analyzes project engineering efficiency via the MantisBT issue vector store: computes resolution rate, mean/P50/P90 lead time, rework rate (reopens), assignee ping-pong, stagnant/overdue issues, efficiency per developer, semantic clusters of recurring bottlenecks, and an Efficiency Score (0-100) with actionable diagnostics.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target a clearly distinct resource+action (tags, notes, relationships, attachments, vector search, analytics). The main overlaps are update_issue (which claims it can also change tags/custom fields) versus attach_issue_tags, and get_issue_full_context versus the aggregate get_my_unresolved_assigned_context, though descriptions do clarify the latter. An agent can pick correctly in nearly all cases.

Naming Consistency4/5

Almost everything follows a consistent verb_noun snake_case pattern (list_projects, create_issue, delete_issue_note, add_issue_relationship). Minor deviations exist: attach_issue_tags vs detach_issue_tag (singular/plural mismatch) and the sentence-style get_my_unresolved_assigned_context. Still highly predictable overall.

Tool Count4/5

25 tools is at the upper edge, but the domain legitimately spans issues, projects, versions, tags, notes, relationships, attachments, config, and vector/analytics features, so each tool roughly earns its place. Slightly heavy and could be consolidated (e.g. attach/detach tag pairs), but not bloated for the stated purpose.

Completeness3/5

Issue lifecycle and notes/relationships are well covered, but there are notable gaps: no delete_issue_attachment, no create/update/delete project, no list/create tags, and versions only support create. These holes will force agents into dead ends on common maintenance tasks, even if core bug-tracking workflows work.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues