Mantis MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Mantis MCP Server?

Mantis MCP Server is a service based on the Model Context Protocol (MCP) designed for integration with the Mantis Bug Tracker system. It provides a set of tools that allow users to query and analyze data within the Mantis system through the MCP protocol.

how to use Mantis MCP Server?

To use Mantis MCP Server, install it via npm and configure the necessary environment variables in a .env file. You can then run the server and interact with it through the MCP protocol.

key features of Mantis MCP Server?

  • Issue management with filtering options
  • User management capabilities
  • Project management tools
  • Statistical analysis of issues
  • Performance optimizations including field selection and pagination
  • Comprehensive error handling and logging

use cases of Mantis MCP Server?

  1. Managing and tracking bugs in software development projects.
  2. Analyzing issue statistics for project management.
  3. Integrating with other tools that utilize the MCP protocol for enhanced functionality.

FAQ from Mantis MCP Server?

  • How do I install Mantis MCP Server?

You can install it using npm with the command npm install mantis-mcp-server.

  • What configurations are needed?

You need to set up a .env file with your Mantis API URL and API key among other settings.

  • Can I use Mantis MCP Server on Windows?

Yes! There are specific instructions for configuring it on Windows as well as macOS/Linux.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago