Ithura

com.ithuraPublished by ithura.comv1.0.1Updated Oct 24, 2026

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

Overview

AI-generated overview

Ithura's MCP server lets an assistant read and write tasks, sprints, projects, modules, comments and wiki pages in an Ithura workspace.

What you can do
List, read, create and update projects and tasks, including deleting tasks and adding comments to them. Manage sprints and modules: create them, add or remove tasks, and delete modules. Look up workflow metadata such as states and labels, and create labels. Search across the workspace. All tools return JSON field values rather than prose.
When to use it
Useful when a team tracks work in Ithura and wants an assistant to answer questions about the current sprint, file or update tasks, or summarize what moved to Done, without switching apps.
Requirements
Runs locally via npx, so Node.js is needed. Requires an Ithura workspace and an API token in ITHURA_API_KEY, created under Settings > API tokens, plus the workspace slug in ITHURA_WORKSPACE_SLUG. ITHURA_API_URL is optional and defaults to the hosted API; set it for self-hosting. Network access to the Ithura API is required.
Before you install
Writes are real: the assistant can create, update and delete tasks and modules, add comments, and change sprint membership. The token carries the permissions of the member who created it, so create it under a member with limited project access if the agent should stay in one corner of the workspace. The token is a secret passed by environment variable.

Installation

In SourceWeft

  1. Open Ithura in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

Links

License

MIT

Source: README.md at commit cba9aa2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts