mcp-openproject-standalone
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENPROJECT_URL | No | Alternative for OPENPROJECT_BASE_URL. | |
| OPENPROJECT_API_KEY | Yes | API token from OpenProject. Alternatively, use OPENPROJECT_API_TOKEN. | |
| OPENPROJECT_BASE_URL | Yes | URL of your OpenProject instance (e.g., https://your-openproject-instance.com). Alternatively, use OPENPROJECT_URL. | |
| OPENPROJECT_API_TOKEN | No | Alternative for OPENPROJECT_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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all visible OpenProject projects |
| get_projectA | Get details of a specific project by ID |
| list_work_packagesA | List all work packages in a given project |
| get_work_packageA | Get details of a specific work package by ID |
| create_work_packageC | Create a new work package in a project |
| update_work_packageA | Update an existing work package. Automatically validates status transitions according to OpenProject workflow rules. If you try to set an invalid status (e.g., directly from "Новый" to "Выполнено"), it will return an error with available statuses. Use get_available_statuses to see valid transitions. |
| list_statusesA | List all available statuses in OpenProject |
| get_available_statusesA | Get available status transitions for a specific work package (workflow). Returns current status and all statuses that can be set for this work package. |
| add_commentB | Add a comment to a work package |
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 9 tools
Each tool targets a distinct resource and action: projects have list/get, work packages have list/get/create/update, statuses have list and available transitions, and comments have add. There's no overlap that would confuse an agent.
All tools follow the verb_noun pattern consistently: list_*, get_*, create_*, update_*, add_*. All names are lowercase snake_case, and the verbs clearly indicate the operation.
The 9 tools are well-scoped for the OpenProject domain, covering projects, work packages, statuses, and comments without excessive fragmentation or missing essentials.
Core work package lifecycle is covered (create, read, update), and status workflows are well supported. Missing delete operations and project creation are minor gaps that don't severely impact typical usage.