Multiple MCP Servers Framework
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the FastAPI server | 10000 |
| API_KEY | No | API key for authentication (optional) | |
| LOG_DIR | No | Directory for storing log files | logs |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoC | A simple echo tool |
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
With only one tool, there is no possibility of confusion between tools.
A single tool name 'echo' is self-consistent, so the naming pattern is coherent by default.
The server is named 'Multiple MCP Servers Framework', yet provides only one trivial echo tool, which is a severe mismatch between name and functionality.
A single echo tool provides no meaningful coverage for any domain; the tool surface is severely incomplete for the implied purpose.