MCP Server Template for Cursor IDE
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_fetchC | Fetches a website and returns its content |
| moodA | Ask the server about its mood - it's always happy! |
| fetch_railway_docsC | Fetches the most recent Railway CLI documentation. Optionally, provide a custom URL. |
| fetch_railway_docs_optimizedB | Fetches the most recent Railway CLI documentation. Optionally, provide a custom URL. |
| apply_prompt_fixC | Provides a prompt for performing root cause analysis and fixing issues |
| apply_prompt_initialC | Provides an initial prompt template for starting a new project |
| apply_prompt_proceedC | Provides a prompt template for proceeding with a task or project |
| apply_prompt_changeC | Provides a prompt for systematically handling change requests |
| apply_prompt_fix_linterB | Provides a prompt for analyzing and fixing linter errors |
| apply_prompt_unit_testsC | Provides a prompt for generating unit tests for code |
| apply_prompt_infraC | Provides a prompt template for laying out system infrastructure and tool stack information |
| apply_prompt_dockerC | Provides a prompt template for Docker container configurations and orchestration |
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 12 tools
The tool set has significant ambiguity, particularly between the 'apply_prompt_*' tools which all provide prompt templates for different contexts but could easily be confused by an agent due to overlapping purposes (e.g., 'apply_prompt_fix' vs 'apply_prompt_fix_linter' for fixing issues). Additionally, 'fetch_railway_docs' and 'fetch_railway_docs_optimized' appear to do the same thing with unclear distinctions, leading to potential misselection.
Most tools follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'apply_prompt_change', 'fetch_railway_docs'), which aids readability. However, there are minor deviations: 'mood' breaks the pattern by being a single noun without a verb, and the duplication in 'fetch_railway_docs' vs 'fetch_railway_docs_optimized' introduces inconsistency in naming for similar functions.
With 12 tools, the count is borderline but reasonable for a template server aimed at Cursor IDE, which might cover various development tasks. However, the set feels slightly heavy due to redundant tools like the two Railway docs fetchers and multiple similar prompt tools, suggesting some consolidation could improve coherence without losing functionality.
The server's domain appears to be development assistance with prompt templates and documentation fetching, but there are significant gaps. For example, it lacks tools for code generation, debugging, or version control integration, which are common in IDE contexts. The inclusion of a trivial 'mood' tool further detracts from covering essential workflows, making the surface incomplete for practical agent use in development tasks.