mcp-blanko
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | HTTP port for SSE transport | 3001 |
| MCP_FILES_DIR | No | Base directory for the file operation tool | cwd |
| MCP_TRANSPORT | No | Transport mode: stdio or sse | 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_worldA | A simple greeting tool. Takes a name and returns a personalized greeting. |
| process_orderD | Demonstrates a tool with a rich input schema: nested objects, enums, optional fields, and error handling. |
| long_running_taskC | Demonstrates an async tool that simulates a long-running operation (e.g., data processing, report generation). |
| fetch_dataC | Placeholder for a tool that calls an external API. Replace the handler with your own API logic. |
| manage_fileC | Demonstrates reading and writing local files. Operates within a configurable base directory. |
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 5 tools
Each tool has a distinct purpose (API call, greeting, async task, file management, order processing), so there is little risk of confusion. However, 'fetch_data' is vaguely named and could overlap with 'long_running_task' in concept.
All tool names use lowercase with underscores, following a consistent pattern. The names are descriptive and predictable.
With 5 tools, the count is reasonable for a small demonstration server. It is slightly below the typical 3-15 range for a focused domain, but acceptable for a placeholder set.
The tools are unrelated demonstrations covering disparate domains (API, greeting, file I/O, order processing). There is no coherent domain, so coverage is severely incomplete for any real-world use case.