MCP Server Template for Cursor IDE
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug mode | false |
| MCP_USER_AGENT | No | Custom User-Agent for website fetching | |
| MCP_SERVER_HOST | No | Host to bind the server to | 0.0.0.0 |
| MCP_SERVER_PORT | No | Port to run the server on | 8000 |
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! |
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 2 tools
The two tools have completely distinct purposes: one fetches website content, while the other returns a static mood response. There is no overlap or ambiguity between them.
The naming is inconsistent: 'mcp_fetch' uses a prefix and verb_noun pattern, while 'mood' is a single noun with no verb. This mixed convention lacks a predictable pattern.
With only two tools, the server feels thin and under-scoped for a template intended for Cursor IDE, suggesting it might not cover enough functionality for typical IDE use cases.
The tool surface is severely incomplete for an IDE template, lacking core operations like file manipulation, code analysis, or project management. The existing tools do not form a coherent workflow.