Redmine Fastmcp Server With Oauth

What is Redmine Fastmcp Server With Oauth?

Redmine Fastmcp Server With Oauth is a centrally-deployed MCP (Model Context Protocol) server for Redmine that uses OAuth 2.0 authentication. An administrator deploys it once; users connect by authorizing through Redmine — no API keys or per-user setup required. It is built with FastMCP 3 and exposes tools and resources over Streamable HTTP.

How to use Redmine Fastmcp Server With Oauth?

Clone the repository, copy .env.example to .env, and fill in REDMINE_URL, REDMINE_CLIENT_ID, and REDMINE_CLIENT_SECRET. Install with pip install -e . and run mcp-redmine-oauth. Alternatively, use docker compose up --build. The MCP server is available at http://localhost:8000/mcp. Configure an MCP client (e.g., Claude Desktop, MCP Inspector) to use Streamable HTTP transport with that URL.

Key features of Redmine Fastmcp Server With Oauth

• OAuth 2.0 authentication – no API keys per user.
• Single admin deployment; users authorize via Redmine.
• Tools for issues, projects, time entries, and more.
• Resources for active projects, trackers, statuses, priorities, and current user.
• Scope-based access control per tool and resource.
• Runs as a Docker container or standalone Python service.

Use cases of Redmine Fastmcp Server With Oauth

• Fetch issue details with custom fields and journals from Redmine.
• Search and list issues with filters (project, assignee, status).
• Retrieve project details, versions, and time entries.
• Build custom MCP clients that interact with Redmine programmatically.
• Replace per-user API key management with centralized OAuth delegation.

FAQ from Redmine Fastmcp Server With Oauth

What are the prerequisites?

Python 3.11+, a Redmine 6.1+ instance with REST API enabled, and an OAuth application registered in Redmine with the required scopes.

How does OAuth work in this server?

The MCP client receives a FastMCP-issued JWT. The server exchanges it for a Redmine OAuth token stored in-memory. The Redmine token is never exposed to the client.

What tools and resources are available?

Tools: get_issue_details, search_issues, list_issues, get_issue_relations, get_project_details, get_project_versions, list_time_entries. Resources: redmine://projects/active, redmine://trackers, redmine://issue-statuses, redmine://enumerations/priorities, redmine://users/me.

How are OAuth scopes handled?

Each tool and resource declares required scopes via a decorator. The server automatically collects and requests all declared scopes during authorization. If your OAuth app only supports a subset, set REDMINE_SCOPES to an allowlist; tools missing required scopes will return a descriptive error at call time.

Can I run this server with Docker?

Yes. Use docker compose up --build. The container reads configuration from .env. Set MCP_BASE_URL to the externally-reachable URL and optionally MCP_HOST_PORT to change the host port.