ithura-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ITHURA_API_KEY | Yes | Workspace API token, from Settings > API tokens | |
| ITHURA_API_URL | No | Point at your own host when self-hosting | https://api.ithura.com |
| ITHURA_WORKSPACE_SLUG | Yes | The slug in your workspace URL |
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_projectsA | List all projects in the workspace |
| get_projectA | Get a project by ID |
| create_projectA | Create a new project in the workspace |
| update_projectC | Update a project |
| list_issuesA | List issues in a project. Supports filtering by state, label, priority, assignee, cycle, module. |
| create_issueB | Create a new issue in a project |
| get_issueB | Get a single issue by ID |
| update_issueC | Update fields on an existing issue |
| delete_issueB | Delete an issue from a project |
| list_statesA | List workflow states for a project |
| list_labelsA | List labels for a project |
| create_labelB | Create a new label in a project |
| list_cyclesA | List all cycles in a project |
| create_cycleB | Create a new cycle in a project |
| add_issues_to_cycleB | Add issues to a cycle |
| remove_issue_from_cycleC | Remove an issue from a cycle |
| list_modulesA | List all modules in a project |
| create_moduleC | Create a new module in a project |
| delete_moduleB | Delete a module from a project |
| add_issues_to_moduleB | Add issues to a module |
| list_issue_commentsB | List comments on an issue |
| add_issue_commentA | Add a comment to an issue |
| search_workspaceC | Search across the workspace for issues, projects, cycles, modules, 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 23 tools
Each tool targets a distinct resource and action, with clear separation between list/get/create/update/delete operations per entity. Overlap is minimal even for similar operations like list_issues vs get_issue, which are unambiguously scoped.
Most tools follow a consistent verb_noun snake_case pattern (e.g., create_issue, delete_module). However, a few tools use a different structure like add_issues_to_cycle and remove_issue_from_cycle, introducing a minor stylistic inconsistency.
With 23 tools, the server exceeds the typical well-scoped range of 3-15. The broad domain justifies many operations, but the count feels heavy given that several resources have only partial CRUD coverage.
The tool set provides full CRUD for issues only. Labels lack update/delete, cycles lack get/update/delete, modules lack get/update, comments lack update/delete, and projects lack delete. These missing operations create significant gaps in lifecycle management.