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 clearly distinct purpose: fetching external API, greeting, long-running task, file management, and order processing. No overlap.
Three tools use verb_noun pattern (fetch_data, manage_file, process_order), but hello_world and long_running_task deviate with different structures. Inconsistent but still readable.
5 tools is well-scoped for a demo server illustrating various MCP patterns. Not too many or too few.
As a demo server, it covers common patterns (API call, async, file I/O, complex schema, simple greeting). Could include more patterns like resource subscriptions, but the set is reasonable.