F
licenseC
qualityD
maintenanceA starter template for building MCP servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants to create custom tools, resource providers, and prompt templates.
2
0-
MCP Server Example
The MCP Server Example allows you to retrieve weather-related information:
Get weather alerts for a specific U.S. state using its two-letter code
Get weather forecasts for a specific location using latitude and longitude coordinates
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server Examplewhat's the weather forecast for Austin this weekend?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Example
This project is a very basic MCP server ready to be consumed by Cursor or other tools.
Modify index.ts and add any tools you want, or keep the default ones.
Then build the project:
pnpm run buildAnd run it:
pnpm run startNow add a .cursor/mcp.json file in your project, and paste the following;
{
"mcpServers":{
"weather":{
"command": "node",
"args": ["[path]/build/index.js"]
}
}
}Replace [path] with the absolute path to this project. Run pwd in the project folder for that. For example, in my case it is:
{
"mcpServers":{
"weather":{
"command": "node",
"args": ["/Users/ivanbtrujillo/Development/mcp-server-spike/build/index.js"]
}
}
}Now go to "Settings" in cursor. You should be able to see the MCP server there. Enable it (click on the top right)
Now go to the chat, switch to Agent mode and select claude-3.7-sonnet as your model.
Type the following:
What is the weather in Texas?It will use the MCP to get first the weather alerts, and then the forecast Here is an example of how the chat interface looks when querying the weather in Texas:
Available Tools
2 toolsget-alertsC
Get weather alerts for a state
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | Two-letter state code (e.g. CA, NY) |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on traits like rate limits, authentication needs, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'weather alerts' entail (e.g., types, severity, format) or behavioral aspects like permissions or errors. For a tool with no structured data beyond the input schema, more context is needed for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with the parameter 'state' fully documented in the schema (two-letter code, examples). The description adds no additional parameter semantics beyond implying the tool is state-specific, so it meets the baseline of 3 where the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and resource 'weather alerts' with scope 'for a state', making the purpose specific and understandable. However, it doesn't explicitly differentiate from its sibling 'get-forecast' (which presumably provides weather forecasts rather than alerts), so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus its sibling 'get-forecast' or any alternatives. It mentions the scope ('for a state') but doesn't clarify use cases, prerequisites, or exclusions, leaving the agent without contextual decision-making help.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get-forecastC
Get weather forecast for a location
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| latitude | Yes | Latitude of the location | |
| longitude | Yes | Longitude of the location |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It states the basic function but doesn't mention important behavioral aspects like whether this is a read-only operation, if it requires authentication, rate limits, data freshness, or what format the forecast returns. For a tool with no annotations, this is insufficient transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise - a single sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple tool and front-loads the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there are no annotations and no output schema, the description should provide more context about what the tool returns and its behavioral characteristics. A weather forecast tool could return various data formats (hourly, daily, current conditions) and may have important constraints, but none of this is mentioned. The description is too minimal for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents both parameters (latitude and longitude). The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get weather forecast') and resource ('for a location'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get-alerts' (which presumably provides weather alerts rather than forecasts), so it doesn't reach the highest score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. There's no mention of the sibling tool 'get-alerts' or any context about when a forecast is more appropriate than alerts. The description simply states what the tool does without usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- First observed
get-alerts - First observed
get-forecast
TDQS
B3.1/5.0
Disambiguation5/5
The two tools have clearly distinct purposes: one retrieves weather alerts for a state, and the other retrieves weather forecasts for a location. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the need for alerts versus forecasts.
Naming Consistency5/5
Both tools follow a consistent verb-noun pattern with hyphens (get-alerts, get-forecast), using the same verb 'get' and descriptive nouns. This predictable naming scheme enhances readability and reduces confusion for agents.
Tool Count2/5
With only two tools, the server feels thin for a weather domain that typically involves more operations, such as current conditions, historical data, or radar imagery. This limited set may not fully support comprehensive weather-related tasks.
Completeness2/5
The tool set is severely incomplete for a weather server, lacking essential operations like getting current conditions, historical weather data, or radar images. This creates significant gaps that could lead to agent failures in handling broader weather queries.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
MCP server for AI dialogue using various LLM models via AceDataCloud
An MCP server for weather information by @kulybaba
Related MCP Servers
- FlicenseAqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers create their own AI assistant integrations.716-
- FlicenseAqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers quickly create their own MCP servers.716-
- FlicenseNot gradedqualityDmaintenanceA template MCP server that provides weather forecasting functionality by fetching current and hourly temperature data from the Open Meteo API for any given latitude and longitude coordinates.-
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ivanbtrujillo/mcp-server-spike'
If you have feedback or need assistance with the MCP directory API, please join our Discord server