Redmine MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Redmine MCP Server?

Redmine MCP Server is a plugin that provides a Model Context Protocol server using Server Side Event for Redmine, allowing for real-time updates and interactions.

how to use Redmine MCP Server?

To use the Redmine MCP Server, download the plugin into the Redmine plugin directory and start Redmine. You can then access various tools to manage issues and wiki pages.

key features of Redmine MCP Server?

  • Tool list_issues: Lists all issues per project.
  • Tool list_wiki_pages: Lists all wiki pages per project.
  • Tool read_issue: Reads a specific issue.
  • Tool read_wiki_page: Reads a specific wiki page.

use cases of Redmine MCP Server?

  1. Managing project issues in real-time.
  2. Accessing and editing wiki pages dynamically.
  3. Integrating with other tools that utilize the Model Context Protocol.

FAQ from Redmine MCP Server?

  • Is the Redmine MCP Server secure?

The HTTP endpoint does not have authentication, so it is recommended to use it in a secure environment.

  • What databases are supported?

The plugin has been tested with SQLite, MySQL 8.0, and PostgreSQL 12.

  • Is this plugin stable?

The plugin is currently experimental and may have issues depending on the version of dependencies.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago