Skip to main content
Glama
BenItBuhner

Cursor Cloud MCP

by BenItBuhner

Related Servers

Alternatives to Cursor Cloud MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables management of Brainbase agents, components, evals, tasks, and more via a remote MCP connection with OAuth authentication.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides OAuth-based MCP integration and client-side tooling for connecting agents to a remote service, with CLI and plugin support.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      Apache 2.0

    TDQS

    C2.4/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions clarify differences. The main overlap is list_agents vs list_agents_v0 (legacy version), with minor potential confusion between get_run/get_run_stream and PR-related tools, but these are mostly resolvable by descriptions.

    Naming Consistency3/5

    Most names follow snake_case verb_noun conventions (list_*, get_*, create_*, cancel_*), but several are noun-first or state-oriented (cursor_status, project_lineage, agent_lifecycle, prewarm_transcript), creating a mixed but still readable pattern.

    Tool Count2/5

    29 tools is heavy for the server's apparent scope. The set includes legacy variants (list_agents_v0) and many extended endpoints, pushing well beyond the 3-15 range that tends to be well-scoped.

    Completeness2/5

    A critical gap is the absence of a create_agent tool, despite list_models explicitly referencing create_agent. There is also no update_agent or initial run creation, leaving core lifecycle operations incomplete despite extensive read and extended coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues