Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REDMINE_URLYesURL of the Redmine instance, e.g. https://redmine.example.com
REDMINE_API_KEYYesAPI key of the dedicated Redmine bot user
REDMINE_TIMEOUTNoTimeout in seconds per request. Defaults to 30.30
REDMINE_TOOLSETSNoComma-separated list of toolsets to enable: standard, expert_helpdesk, expert_agile, redmineup, or all. Defaults to standard.standard
REDMINE_READ_ONLYNoSet to false to enable the write tools. Defaults to true (read-only).true
REDMINE_VERIFY_SSLNoWhether to verify SSL certificates. Defaults to true.true

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_current_userA

The Redmine user this server acts as, with its memberships.

list_projectsB

Projects visible to the server's Redmine user.

get_projectC

A project with its trackers, issue categories, enabled modules and time entry activities.

search_issuesA

Issues matching the filters (long descriptions are shortened, use get_issue for the full issue).

get_issueC

A single issue with its history (journals), attachments, relations and subtasks.

list_time_entriesD

Spent time entries.

list_versionsC

Versions (milestones/releases) of a project, including shared ones.

list_project_membersC

Members of a project with their roles.

list_wiki_pagesC

Index of the wiki pages of a project.

get_wiki_pageC

A wiki page with its text, optionally an older version.

searchC

Redmine full text search across issues, wiki pages, news, documents, changesets and forum messages.

list_reference_dataA

Ids and names needed for filters and changes: issue statuses, trackers, priorities, time entry activities, document categories, custom fields (admin only), saved queries, roles, groups (admin only).

get_attachmentB

Metadata of an attachment and, for text files, optionally its content.

redmine_getC

Any single Redmine resource by id (read-only).

redmine_listC

Any Redmine resource list, filtered or all (read-only). Unknown names return the list of resources.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 15 tools

Disambiguation3/5

The 13 specific tools (get_issue, list_projects, list_versions, etc.) have clearly distinct purposes, but the generic redmine_get and redmine_list overlap with almost all of them, creating real ambiguity about which to use. search vs. search_issues also blurs (full-text vs. filtered), further muddying selection.

Naming Consistency3/5

Most tools follow a clean verb_noun snake_case pattern (list_projects, get_issue, search_issues). However, redmine_get and redmine_list switch to a namespace-prefixed convention, and the bare 'search' breaks the verb_noun rhythm, making the set mixed.

Tool Count5/5

15 tools is well within the healthy range and each of the specific tools maps to a real Redmine resource. The two generic catch-alls add coverage without bloating the surface excessively.

Completeness4/5

The server is explicitly read-only and covers a broad surface (users, projects, issues, time entries, versions, wiki, attachments, search) plus generic get/list fallbacks. The main gap is the absence of write operations (create/update issues, wiki edits, time logging), though the generic tools partially compensate for reads.

Maintenance

ActivityMaintained
ResponsivenessNo issues