hermes-oh-my-pi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUN_BIN | No | Path to the Bun binary if installed somewhere custom | |
| OMP_BIN | No | Path to the omp binary if not just 'omp' |
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 |
|---|---|
| promptC | Run oh-my-pi (omp) in one-shot mode and return the result as text or JSON. |
| doctorA | Check whether the local oh-my-pi and bun runtime are available. |
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, 'doctor' and 'prompt', have clearly distinct purposes: one checks environment setup and the other runs the main functionality. There is no overlap or confusion between them.
Both tool names are single words but do not follow a consistent verb_noun pattern. While simple and clear, they lack a predictable naming convention across the set.
With only 2 tools, the server is at the lower boundary of acceptable size. For a simple one-shot execution server, this may be appropriate, but it feels thin compared to typical MCP servers.
The tool surface covers checking availability and executing the main command, but misses other potential operations like configuration or version info, leaving minor gaps for more complex agent workflows.