OpenProject MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ai_tasksA | Get list of tasks ready for AI development from OpenProject. Returns tasks from 'Баги' and 'Готово к разработке' columns that have ai_dev flag set to true. Each task includes: id, url, subject, description, type, status, priority, assignee. |
| get_taskB | Get detailed information about a specific task by its ID. Returns full task details including description, status, assignee, etc. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a single task by ID, the other lists filtered tasks based on specific criteria. No overlap in functionality.
Both tool names follow a consistent 'get_noun' snake_case pattern, making them predictable and easy to understand.
With only two tools for a project management server, the count is too low. A typical server for this domain would require additional tools for CRUD operations and broader querying.
The tool surface is severely incomplete: it lacks any create, update, or delete operations, and fails to support common workflows like listing all tasks or searching by other criteria.