Skip to main content
Glama
Ithura

ithura-mcp

Official
by Ithura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ithura-mcp

No user-submitted related servers found.

    Related Servers

    • litejira-mcp

      UNTAG-LAB
      A
      license
      Not graded
      quality
      C
      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.
      15 npm
      MIT

    • jira-mcp-server

      Hopcos
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server enabling AI assistants to interact with Jira projects, issues, sprints, users, attachments, and worklogs via natural language, with support for both local stdio and remote HTTP transports, dual authentication methods, and enterprise-grade security controls.
      2
      Apache 2.0

    • planning-task-mcp

      sergioramosv
      A
      license
      Not graded
      quality
      F
      maintenance
      Full autonomous project management MCP server enabling AI assistants to manage projects, sprints, tasks, bugs, proposals, and team collaboration via natural language.
      13 npm
      MIT

    • @isteamhq/mcp

      isteamhq
      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
      8 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources