mcp-server-scaffold
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROOT | No | The folder that file tools are allowed to touch, passed as `--root ./sandbox`. Auto-created if missing. | . |
| NO_LOGGING | No | Set via the `--no-logging` flag to silence the stderr diagnostics (e.g. `--no-logging` or NO_LOGGING=true). | false |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Repeats your message back, optionally shouting (uppercase). The simplest example of a working MCP tool. |
| note_writeB | Writes a note to a markdown file inside the sandbox folder. If the file already exists it is backed up first, never overwritten blindly. |
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 2 tools
echo and note_write have clearly distinct purposes: one repeats a message, the other writes a markdown note. There is no realistic risk of an agent confusing them.
The two names follow different conventions: echo is a bare verb, while note_write is a compound noun_verb-style name. Both are readable, but the set does not establish a predictable naming pattern.
Two tools is thin for a general-purpose MCP server, though it may be acceptable for a scaffold/demo server. Each tool does earn its place, but the surface is borderline minimal.
If the likely domain is note-taking, note_write supports creation but there is no read, list, update, or delete operation. The echo tool is unrelated to note workflows, leaving significant gaps for practical note management.