redmine-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDMINE_URL | Yes | Required. URL of the Redmine instance, e.g., https://redmine.example.com | |
| REDMINE_TOKEN | No | Alias for REDMINE_API_KEY. | |
| REDMINE_API_KEY | No | Redmine API key for authentication (preferred). Aliases: REDMINE_TOKEN or REDMINE_ACCESS_TOKEN. | |
| REDMINE_PASSWORD | No | Password for HTTP Basic auth (requires REDMINE_USERNAME). | |
| REDMINE_USERNAME | No | Username for HTTP Basic auth (requires REDMINE_PASSWORD). | |
| REDMINE_ACCESS_TOKEN | No | Alias for REDMINE_API_KEY. |
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
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redmine_api_requestA | Call any Redmine REST API endpoint. This is the escape hatch for the complete Redmine API surface, version-specific endpoints, and plugin endpoints. Paths are resolved under REDMINE_URL. |
| redmine_paginated_requestB | Call a Redmine list endpoint and follow Redmine offset/limit pagination using total_count from the response body. |
| redmine_upload_fileA | Upload binary content to Redmine /uploads.json and return an upload token for later attachment to issues, documents, wiki pages, or project files. |
| redmine_current_userB | Get the authenticated Redmine user via /users/current.json. |
| redmine_searchC | Search Redmine with /search.json. Supports standard query params such as q, scope, all_words, titles_only, issues, news, documents, changesets, wiki_pages, messages, projects. |
| redmine_issuesC | Manage issues: list, get, create, update, add_note, delete. |
| redmine_issue_relationsB | Manage issue relations: list, create, delete. |
| redmine_issue_watchersC | Manage issue watchers: add, remove. |
| redmine_projectsC | Manage projects: list, get, create, update, delete, archive, unarchive. |
| redmine_membershipsA | Manage project memberships: list, get, create, update, delete. |
| redmine_versionsB | Manage project versions: list, get, create, update, delete. |
| redmine_time_entriesC | Manage time entries: list, get, create, update, delete. |
| redmine_usersC | Manage users: list, get, create, update, delete. |
| redmine_groupsC | Manage groups: list, get, create, update, delete, add_user, remove_user. |
| redmine_rolesC | Read roles: list, get. |
| redmine_trackersC | Read trackers: list. |
| redmine_issue_statusesC | Read issue statuses: list. |
| redmine_enumerationsC | Read Redmine enumerations: issue_priorities, time_entry_activities, document_categories. |
| redmine_custom_fieldsC | Read custom fields: list. |
| redmine_queriesC | Read saved issue queries: list. |
| redmine_wikiC | Manage project wiki pages: list, get, update, delete. |
| redmine_documentsC | Manage documents: list, get, create, delete. |
| redmine_filesC | Manage project files: list, create. |
| redmine_newsC | Read news: list, get. |
| redmine_attachmentsC | Manage attachments: get, delete. |
| redmine_issue_categoriesC | Manage issue categories: list, get, create, update, delete. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Each tool targets a distinct Redmine resource (issues, projects, users, etc.) with clearly separated actions. The only potential ambiguity is the generic redmine_api_request, but it is explicitly documented as an escape hatch for unsupported endpoints, so agents can distinguish it from the resource-specific tools.
All tools follow the pattern 'redmine_<resource>', using plural nouns for resources (e.g., redmine_issues, redmine_projects). Minor deviations exist: redmine_upload_file, redmine_paginated_request, and redmine_api_request include action words, but the prefix 'redmine_' is consistently applied, making the set predictable.
26 tools is on the upper end but appropriate for the comprehensive Redmine API surface it covers. The count reflects the many resource types (issues, projects, users, wiki, attachments, etc.), and no tool feels unnecessary. A slightly smaller set could be acceptable, but this is well-scoped.
The tool surface covers CRUD for most major resources and includes search, file upload, and enumeration reads. Minor gaps exist (e.g., custom_fields only list, news read-only) but are compensated by the redmine_api_request escape hatch, which agents can use for any missing endpoint.