openproject-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENPROJECT_URL | Yes | The root URL of the OpenProject instance (e.g., https://openproject.example.local) | |
| OPENPROJECT_API_TOKEN | Yes | An API token for authentication with the OpenProject instance. Can be used with Bearer or Basic auth. | |
| OPENPROJECT_AUTH_MODE | No | Authentication mode: bearer or basic. Defaults to bearer. | bearer |
| OPENPROJECT_ENABLE_WRITE | No | Set to 'true' to enable write operations (create_work_package, add_work_package_comment). Defaults to false. | false |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsC | List projects visible to the configured OpenProject API user. |
| search_work_packagesC | Search work packages with common OpenProject API v3 filters. |
| get_work_packageB | Get a single OpenProject work package by numeric id. |
| get_my_work_packagesC | Get work packages assigned to the configured OpenProject API user. |
| create_work_packageB | Create a work package. Requires OPENPROJECT_ENABLE_WRITE=true. |
| add_work_package_commentB | Add a comment to a work package. Requires OPENPROJECT_ENABLE_WRITE=true. |
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 6 tools
Most tools are clearly distinct: list_projects vs work package tools, and create/comment are unique actions. However, get_my_work_packages could potentially overlap with search_work_packages using an assignee filter, creating slight ambiguity.
All tool names follow a consistent verb_noun pattern (list, get, search, create, add), with get_my_work_packages being the only slight deviation but still within the pattern. No mixed conventions or chaotic naming.
With 6 tools, the server is well-scoped for an OpenProject integration, covering both projects and work packages without excessive fragmentation. The count is squarely in the ideal range.
The toolset provides basic work package lifecycle (create, get, search) and commenting, but lacks update and delete operations for work packages. Project creation is also missing, leaving notable gaps for full domain coverage.