Skip to main content
Glama
CodecoolGlobal

runn-mcp

by CodecoolGlobal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to runn-mcp

No user-submitted related servers found.

    Related Servers

    • Caddy MCP

      euisuh
      A
      license
      A
      quality
      B
      maintenance
      MCP server for safely inspecting and operating a local Caddy admin API. Provides read-only tools and dry-run mutations for config management.
      7
      MIT

    • mobilerun-mcp

      droidrun
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Mobilerun platform, exposing tools for device control, workflow automation, task management, and platform operations via a stateless HTTP or stdio interface with bearer-token authentication and policy-based access control.
      Apache 2.0

    • Gripp MCP

      maxancedecot
      F
      license
      A
      quality
      B
      maintenance
      MCP server for the Gripp API, enabling CRUD operations on Gripp entities with built-in confirmation safety for mutations.
      9
      7 npm
      1
      -

    • cml2-mcp

      higebu
      A
      license
      A
      quality
      C
      maintenance
      Thin MCP server for Cisco CML2 that exposes the live OpenAPI specification and a generic API call tool, enabling models to interact with CML2 by reading the spec first.
      2
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.4/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action combination. Even closely related tools like runn_list_people vs runn_list_placeholders are clearly separated by entity, and runn_list_actuals vs runn_bulk_actuals are list vs create/update. No two tools appear to do the same thing.

    Naming Consistency3/5

    Most tools follow the `runn_<verb>_<noun>` pattern (e.g., runn_create_project, runn_list_phases). However, several deviate: runn_report_totals_project, runn_report_hours_project, runn_bulk_actuals, runn_server_info, and runn_whoami are not clearly verb_noun. This mixed convention slightly reduces predictability.

    Tool Count2/5

    32 tools is well above the recommended range for a coherent set. Even accounting for the broad domain (projects, phases, milestones, assignments, actuals, workstreams, reports, auth), the count feels heavy and could overwhelm agents. Some consolidation might be possible.

    Completeness4/5

    The set covers the core lifecycle for projects, phases, milestones, assignments, actuals, workstreams, and people. Minor gaps exist (e.g., no delete_project, no update_assignment, no delete_milestone), but these may reflect API constraints and are typically workable (e.g., delete and recreate assignment). Reports cover the key planning vs. actuals use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources