MCP TypeScript Boilerplate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | The API key for the service (required). | |
| TIMEOUT | No | Request timeout in milliseconds (optional). | |
| BASE_URL | Yes | The base URL of the API (required). |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_exampleA | Fetch an example resource by ID. |
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 1 tool
There is only one tool, so no ambiguity exists. An agent cannot confuse it with another tool.
With a single tool, naming consistency is not a concern; there is no inconsistency to evaluate.
As a boilerplate server, one tool is appropriate for its demonstration purpose. It is minimal but not unreasonable.
For a boilerplate, the single tool serves as an example. However, it lacks any create, update, or delete operations, which limits its completeness.