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! |
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, making it easy for an agent to select the correct tool for each task.
The tools use different naming conventions: 'mcp_fetch' follows a prefix_verb pattern, while 'mood' is a simple noun. This mixed style lacks a predictable pattern, though both names are readable and descriptive of their functions.
With only two tools, the server feels thin and under-scoped for a template intended for Cursor IDE, which typically involves more complex operations. This minimal set may not adequately cover common IDE-related tasks, suggesting a mismatch in scope.
Inferred as a template for IDE integration, the tool surface is severely incomplete. It lacks core functionalities like file manipulation, code analysis, or project management, leaving significant gaps that would hinder agent workflows in an IDE context.