Skip to main content
Glama
daiji-sshr

redmine-mcp-stateless

by daiji-sshr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REDMINE_MCP_PORTNo8000

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsB

Returns a list of Redmine projects.

get_projectC

Returns details of the specified project.

Args:
    project_id: Project ID or identifier
list_issuesC

Returns a list of issues.

Args:
    project_id: Project ID (all projects if omitted)
    status_id: Status ID or "open" / "closed" / "*"
    assigned_to_id: Assignee ID
    limit: Number of results (max 100)
    offset: Starting offset
get_issueB

Returns details of the specified issue, including comments and attachments.

Args:
    issue_id: Issue number
create_issueC

Creates a new issue.

Args:
    project_id: Project ID or identifier
    subject: Subject
    description: Description
    tracker_id: Tracker ID
    status_id: Status ID
    priority_id: Priority ID
    assigned_to_id: Assignee ID
update_issueC

Updates an issue.

Args:
    issue_id: Issue number
    subject: New subject
    description: New description
    status_id: New status ID
    priority_id: New priority ID
    assigned_to_id: New assignee ID
    notes: Comment
update_journalB

Edits a journal (comment) on an issue. Requires Redmine 5.0+.

Args:
    journal_id: Comment ID (journals[].id from get_issue response)
    notes: New comment content
list_statusesB

Returns a list of available issue statuses.

list_trackersB

Returns a list of available trackers.

list_prioritiesA

Returns a list of available issue priorities. Used for priority_id in create_issue / update_issue.

search_issues_fullA

Full-text search for issues by keyword. Returns results with description and all comments. Searches across subject, description, and all comments.

Args:
    query: Search keyword
    project_id: Filter by project ID (all projects if omitted)
    limit: Maximum number of results (all results if omitted)
list_issues_with_journalsB

Returns a list of issues with all comments. Useful for reviewing progress per assignee.

Args:
    assigned_to_id: Assignee ID (obtain via list_users)
    project_id: Project ID (all projects if omitted)
    status_id: Status ID or "open" / "closed" / "*"
    limit: Number of issues to fetch (max 100)
    offset: Starting offset
list_usersA

Returns a list of Redmine users. Useful for looking up assignee IDs by name. Note: May require Redmine administrator privileges.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 13 tools

Disambiguation4/5

Most tools have distinct purposes, but list_issues and list_issues_with_journals have significant overlap in functionality and parameters, which could cause confusion. The other tools are clearly differentiated by their target resources and actions.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern with snake_case throughout. The naming is predictable and readable, with clear action-resource pairs like create_issue, list_projects, and update_journal.

Tool Count5/5

With 13 tools, this server is well-scoped for Redmine issue and project management. The count is appropriate, covering core operations without being overwhelming, and each tool serves a clear purpose in the domain.

Completeness4/5

The toolset provides strong coverage for issue and project management, including CRUD operations for issues, listing resources, and search. A minor gap is the lack of project creation/deletion tools, but agents can still perform core workflows effectively.

Maintenance

ActivityInactive
ResponsivenessSlow

Resources