MCP Server Starter Kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MY_API_KEY | Yes | API key for accessing external services (example from Claude Desktop config) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echo back a message. Use to verify the MCP server is working. |
| fetch_urlA | Fetch the text content of a URL. Returns up to 100KB of content. Useful for reading web pages, APIs, or any HTTP endpoint. |
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
Echo and fetch_url are completely distinct in purpose—one verifies connectivity, the other retrieves web content. There is no overlap or ambiguity between them.
Both names are imperative and lowercase, but one is a bare verb (echo) while the other follows a verb_noun pattern (fetch_url). This mixed convention, while readable, is not fully consistent.
Two tools is appropriate for a starter kit that aims to demonstrate basic MCP functionality, but the count feels thin compared to typical servers that offer more comprehensive operations.
The tool set covers the intended purpose of a starter kit: verifying server operation and fetching URL content. There are no obvious gaps for this narrow scope, though it lacks broader capabilities.