Skip to main content
Glama
tygart-media

cursor-cloud-agents-mcp

by tygart-media
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to cursor-cloud-agents-mcp

No user-submitted related servers found.

    Related Servers

    • cloud-agent-mcp

      mciver87
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Cursor Cloud Agent operations as native MCP tools, letting MCP-capable clients launch new agents, list and inspect recent ones, send follow-up prompts to resume them, and cancel running runs. Tool arguments are validated with Zod schemas and results include agent ID, URL, and final assistant output.
      MIT

    • wb-cursor-bridge

      jsyzc2019
      A
      license
      A
      quality
      B
      maintenance
      Enables a supervisor agent to dispatch, monitor, follow up on, cancel, and inspect Cursor CLI code tasks through a governed MCP interface, with permission tiers, workspace allowlists, isolated git worktrees, and auditable artifacts. It also exposes an A2A-compatible HTTP endpoint for agent discovery and scheduling.
      9
      MIT

    • cursor-mcp

      ebrindley
      A
      license
      A
      quality
      B
      maintenance
      Enables delegating coding tasks to Cursor Cloud Agents from Claude Code, Codex, or Grok, with scoped repository access, progress monitoring, follow-ups, and result reporting.
      23
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct lifecycle action: launch, status, followup, result, cancel, list, models, whoami, usage. The overlap between cursor_status and cursor_result is explicitly resolved in descriptions (result is a convenience wrapper that waits server-side). No real ambiguity.

    Naming Consistency5/5

    All tools follow a consistent cursor_<verb/noun> snake_case pattern (cursor_launch, cursor_status, cursor_followup, cursor_list, cursor_models, etc.). Predictable and uniform throughout, and prefixing avoids collision with other servers.

    Tool Count5/5

    Nine tools is well-scoped for a cloud agent orchestration server. Each earns its place: launch/poll/followup/cancel cover the run lifecycle, plus auxiliary helpers (models, list, whoami, usage) that are genuinely useful rather than filler.

    Completeness4/5

    Full agent lifecycle is covered: model discovery, launch, status, follow-up, result, cancel, list, auth check, and usage. Minor gaps exist such as no explicit archive/delete agent or run-logs streaming tool, but core workflows are complete and descriptions preempt common dead ends (idempotency, unknown status reconciliation).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources