MCP server: One MCP server.

Ithura MCP

@ithuraRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

Manage tasks, sprints, projects, and wiki pages in your Ithura workspace.

Issue trackingv1.0.1MITTypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: creates or changes data: records, files, settings.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmithura-mcpv1.0.1

Run

npx -y ithura-mcp

MCP client config

{
  "mcpServers": {
    "ithura-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ithura-mcp"
      ]
    }
  }
}
README2 min read

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:

bash
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):

json
{
  "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.

Configuration

VariableRequiredDefaultNotes
ITHURA_API_KEYyesWorkspace API token, from Settings > API tokens
ITHURA_WORKSPACE_SLUGyesThe slug in your workspace URL
ITHURA_API_URLnohttps://api.ithura.comPoint 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:

AreaTools
Projectslist_projects, get_project, create_project, update_project
Taskslist_issues, get_issue, create_issue, update_issue, delete_issue
Commentslist_issue_comments, add_issue_comment
Sprintslist_cycles, create_cycle, add_issues_to_cycle, remove_issue_from_cycle
Moduleslist_modules, create_module, add_issues_to_module, delete_module
Metadatalist_states, list_labels, create_label
Searchsearch_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

Similar modules

Browse Issue tracking