MCP Compact
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| invokeC | Invoke an MCP tool through the compact projection surface. Use Available tool families: Example: invoke(ref={"server": "notes", "name": "echo_note"}, arguments={"title": "...", "body": "..."}) |
| readA | Read MCP resources through the compact projection surface. Use Direct resources:
Resource templates:
Example: read(ref={"server": "notes", "uriTemplate": "memo://notes/{slug}", "arguments": {"slug": "welcome"}}, mode="read") |
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
The two tools are clearly separated by purpose: invoke handles tool calls and read handles resource access. The descriptions provide explicit examples and modes to guide usage, though the generic proxy nature could occasionally blur the line between a tool and a resource.
Both tool names are single-word verbs in a consistent imperative style, making them predictable and easy to remember. There is no mixing of conventions or misleading synonyms.
With only two tools, the set is intentionally minimal but well-suited for a compact projection surface that forwards to a larger MCP ecosystem. While it feels thin compared to direct-integration servers, its purpose justifies the small count.
The server covers the core interaction patterns (invoking tools and reading resources) and includes validation/preview modes. However, it lacks an explicit discovery mechanism to list available servers, tools, or resource templates, which could be a significant gap for agents without prior knowledge.