Skip to main content
Glama
Sign In
cueapi-mcp

cueapi-mcp

Official
by cueapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cueapi-mcp

No user-submitted related servers found.

    Related Servers

    • moo-tasks

      shekarsiri
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.
      16 npm
      3
      MIT
    • genpark-managed-agent-fleet-lifecycle-supervisor-skill

      genpark-managed-agent-fleetofficial

      Alpha-Park
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables enterprise agent fleets to register workers, dispatch tasks by capability, monitor continuous heartbeat telemetry, trip automated circuit breakers, and recover from checkpointed state through a zero-dependency MCP server.
      MIT

    • task-orchestrator

      jpicklyk
      A
      license
      Not graded
      quality
      B
      maintenance
      Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what agents must produce — the server blocks the call if they don't. Works with any MCP-compatible client.
      214
      MIT

    • Agent Harness Kit

      Busra530
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that runs structured multi-agent workflows by owning task claims, action logs, handoffs, and server-side health gates over a shared filesystem and database. It enables coordinated Explorer, Consultant, Builder, and Reviewer roles with tracked specifications and audited completion evidence.
      29 npm
      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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific operations on cues or executions. There is no overlap: create, delete, get, list, pause, resume, list_executions, and report_outcome are all unique actions with well-defined boundaries.

    Naming Consistency5/5

    All tools follow a consistent 'cueapi_verb_noun' pattern with snake_case throughout. The naming is predictable and uniform, making it easy to understand each tool's function at a glance.

    Tool Count5/5

    With 8 tools, the server is well-scoped for managing cues and executions. Each tool earns its place, covering core CRUD operations, lifecycle management (pause/resume), and accountability features without being overwhelming.

    Completeness5/5

    The toolset provides complete coverage for the CueAPI domain: full CRUD for cues (create, get, list, delete), lifecycle control (pause/resume), execution tracking (list_executions), and accountability (report_outcome). There are no obvious gaps, enabling agents to handle all typical workflows.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources