cursor-bridge-mcp
Related Servers
Alternatives to cursor-bridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables programmatic control of Cursor's cloud-based AI agents for automated code generation and repository management via standardized MCP tools.15 npm6MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLM-powered code analysis, generation, debugging, and context management through MCP integration with IDEs like Cursor and Claude Desktop.-
- AlicenseAqualityCmaintenanceEnables Claude and Cursor to access agent memory, shared knowledge graphs, and decision audit through MCP.12MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to retrieve repository context through stdio-based MCP tools, including ranked repo maps, context packs, and live symbol search.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI tools to retrieve codebase context, summaries, decision notes, and file details via MCP, avoiding re-explaining the project.2MIT
- AlicenseAqualityDmaintenanceEnables the creation and execution of task-specific AI sub-agents defined in markdown across any MCP-compatible tool like Cursor or Claude Desktop. It integrates with execution engines such as Claude Code, Cursor CLI, and Gemini CLI to provide portable and reusable specialized agent workflows.1441 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct entity (rules, agents, skills, context index) with clear parameters. There is no overlap: get_active_rules and get_rule differ by specificity, and get_skill and get_skill_file differ by scope.
All tools follow a consistent 'get_' prefix followed by the entity name in snake_case. This uniform pattern makes it easy to predict tool names.
With 6 tools, the set is appropriately scoped for a read-only retrieval server. Each tool serves a necessary function without redundancy or bloat.
The tool set covers all primary retrieval operations for the domain: fetching active rules, individual rules, agents, skills, skill files, and listing all available context. No obvious gaps for a read-only interface.