MCP Server Starter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (HTTP mode only) | 3000 |
| CORS_ORIGIN | No | CORS allowed origins (HTTP mode only) | * |
| STARTER_TRANSPORT | No | Transport mode: stdio or http | stdio |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoC | Echo back the provided text |
| fetchC | Fetch a stub document by id and return full text |
| searchB | Search stub documents and return minimal results (id, title, url) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code-analyzer | Analyze code for security, performance, style issues, and bugs |
| generate-readme | Generate a README file for a project |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| System Information | Get basic system information about the server |
| ISO 8601 format | Get current timestamp in various formats |
| Unix timestamp | Get current timestamp in various formats |
| Human-readable format | Get current timestamp in various formats |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: echo handles text reflection, fetch retrieves specific documents by ID, and search performs document queries with minimal results. There is no overlap in functionality, making tool selection straightforward.
All tool names follow a consistent, simple verb pattern (echo, fetch, search) without any deviations in style or convention. This uniformity enhances predictability and usability.
With only 3 tools, the server feels minimal for a 'starter' purpose, potentially lacking depth for more complex tasks. While not extreme, it borders on being too thin for broader utility.
The tool set is severely incomplete for a document management domain, missing essential CRUD operations like create, update, or delete. Agents will face dead ends when trying to modify or manage documents.