Skip to main content
Glama
ithura-mcp

ithura-mcp

Official
by Ithura

Ithura MCP server

npm MCP Registry license

A Model Context Protocol server for Ithura, a quiet project management workspace for deliberate teams.

Point Claude, Cursor, or any MCP client at your Ithura workspace and let it read and write real work: tasks, sprints, projects, modules, wiki pages, and intake.

"What is left in the current sprint?"
"Create a task for the login timeout bug and put it in this sprint."
"Summarise every task that moved to Done this week."

Listed in the official MCP Registry as com.ithura/mcp.

Install

No install step. Point your MCP client at npx:

npx ithura-mcp

Claude Desktop / Claude Code

Add to your MCP settings (claude_desktop_config.json, or .mcp.json in a project for Claude Code):

{
  "mcpServers": {
    "ithura": {
      "command": "npx",
      "args": ["-y", "ithura-mcp"],
      "env": {
        "ITHURA_API_KEY": "your-api-token",
        "ITHURA_WORKSPACE_SLUG": "your-workspace"
      }
    }
  }
}

Cursor

~/.cursor/mcp.json takes the same block.

Related MCP server: @isteamhq/mcp

Configuration

Variable

Required

Default

Notes

ITHURA_API_KEY

yes

Workspace API token, from Settings > API tokens

ITHURA_WORKSPACE_SLUG

yes

The slug in your workspace URL

ITHURA_API_URL

no

https://api.ithura.com

Point at your own host when self-hosting

Create the token in Ithura under Settings > API tokens. It carries the permissions of the member who created it, so create it as a user whose access matches what you want the agent to have.

Tools

23 tools across the work graph:

Area

Tools

Projects

list_projects, get_project, create_project, update_project

Tasks

list_issues, get_issue, create_issue, update_issue, delete_issue

Comments

list_issue_comments, add_issue_comment

Sprints

list_cycles, create_cycle, add_issues_to_cycle, remove_issue_from_cycle

Modules

list_modules, create_module, add_issues_to_module, delete_module

Metadata

list_states, list_labels, create_label

Search

search_workspace

Every tool returns JSON, so the model sees real field values rather than prose.

Notes

  • The API noun for a work item is issue in the HTTP API; the product calls them tasks. The tool names follow the API.

  • Writes are real. Consider a token scoped to a member with limited project access if you want the agent kept to a corner of the workspace.

  • Self-hosting: set ITHURA_API_URL to your instance and everything else works unchanged.

License

MIT

Available Tools

23 tools
add_issue_commentA

Add a comment to an issue

Inputs: issue_id (required), project_id (required), comment_html (required).

add_issues_to_cycleB

Add issues to a cycle

Inputs: cycle_id (required), issue_ids (required), project_id (required).

add_issues_to_moduleB

Add issues to a module

Inputs: issue_ids (required), module_id (required), project_id (required).

create_cycleB

Create a new cycle in a project

Inputs: name (required), project_id (required), end_date, start_date, +1 more.

create_issueB

Create a new issue in a project

Inputs: name (required), project_id (required), priority, state_id, +7 more.

create_labelB

Create a new label in a project

Inputs: name (required), project_id (required), color, description.

create_moduleC

Create a new module in a project

Inputs: name (required), project_id (required), status, start_date, +2 more.

create_projectA

Create a new project in the workspace

Inputs: name (required), identifier (required), emoji, network, +1 more.

delete_issueB

Delete an issue from a project

Inputs: issue_id (required), project_id (required).

delete_moduleB

Delete a module from a project

Inputs: module_id (required), project_id (required).

get_issueB

Get a single issue by ID

Inputs: issue_id (required), project_id (required).

get_projectA

Get a project by ID

Inputs: project_id (required).

list_cyclesA

List all cycles in a project

Inputs: project_id (required).

list_issue_commentsB

List comments on an issue

Inputs: issue_id (required), project_id (required).

list_issuesA

List issues in a project. Supports filtering by state, label, priority, assignee, cycle, module.

Inputs: project_id (required), cycle, label, state, +3 more.

list_labelsA

List labels for a project

Inputs: project_id (required).

list_modulesA

List all modules in a project

Inputs: project_id (required).

list_projectsA

List all projects in the workspace

Inputs: no named parameters.

list_statesA

List workflow states for a project

Inputs: project_id (required).

remove_issue_from_cycleC

Remove an issue from a cycle

Inputs: cycle_id (required), issue_id (required), project_id (required).

search_workspaceC

Search across the workspace for issues, projects, cycles, modules, etc.

Inputs: query (required).

update_issueC

Update fields on an existing issue

Inputs: issue_id (required), project_id (required), name, priority, +8 more.

update_projectC

Update a project

Inputs: project_id (required), name, emoji, network, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 23 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for is.team, enabling AI agents to interact with project boards, tasks, cards, sprints, integrations, and real-time notifications.
      100
      190 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A client-side MCP server that enables AI assistants to interact with the LiteJira issue tracking system for creating, searching, and managing issues via natural language.
      59 npm
      MIT