cursor-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_rulesA | Returns rules that apply to a given set of files and/or task description. Call at session start or when switching file context. |
| get_context_indexA | Returns a lightweight menu of all available context — rules, agents, and skills — with descriptions only, no content. |
| get_ruleA | Fetches the full content of a specific rule by name. |
| get_agentB | Fetches the full definition of a Cursor agent by name. |
| get_skillC | Fetches the full content of a skill package. |
| get_skill_fileA | Fetches a specific supporting file from within a skill directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.