Skip to main content
Glama
sandraschi

cursor-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to cursor-mcp

No user-submitted related servers found.

    Related Servers

    • cursor-usage

      ofershap
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps Cursor Enterprise API to enable AI agents to answer questions about team spending, usage, and model adoption.
      17
      22 npm
      2
      MIT

    • mcp_quickstart_server

      jonmarrs
      A
      license
      Not graded
      quality
      C
      maintenance
      A FastMCP server that enables AI engineers to run a production-ready MCP endpoint with in-memory token-bucket rate limiting and strict Pydantic v2 input validation. It connects to Claude Desktop, Cursor, and custom agent runners over stdio for safe tool execution.
      1
      MIT

    • cursor-otel

      smith
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that instruments Cursor AI agent interactions with OpenTelemetry traces and logs to monitor agent turns and performance. It enables tracking of user queries, assistant responses, and tool usage through GenAI-compliant telemetry spans.
      MIT

    • Cursor Agent MCP

      lipey1
      A
      license
      B
      quality
      B
      maintenance
      A fast, hardened MCP server that lets any MCP host drive the Cursor Agent CLI for heavy repo-aware tasks like search, analysis, planning, and edits, keeping host context small and token costs low.
      10
      1
      MIT

    • mnemos

      ncz-os
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing persistent memory, semantic search, versioned storage, webhook fanout, and unified LLM routing for AI agents via FastAPI runtime with multiple backend options.
      33
      Apache 2.0
    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

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct domain: cloud agents, documentation, help, inter-agent inbox, SDK guidance, and billing. No overlap in purpose, clear boundaries.

    Naming Consistency5/5

    All tools follow a consistent 'cursor_<noun>' pattern with lowercase snake_case, making them easily predictable and grouped.

    Tool Count5/5

    Six tools is well-scoped for the server's purpose, covering key Cursor ecosystem areas without being too sparse or bloated.

    Completeness4/5

    Covers cloud agent inspection, documentation, help, inbox messaging, SDK guidance, and billing. Minor gap: cloud agent management lacks create/delete, but this is likely intentional.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources