mcp-mesh
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mesh_search_toolsB | Search for relevant tools across all aggregated MCP servers using natural language keywords (e.g. 'git commit', 'read file', 'query postgres'). Returns ultra-compact signatures and relevance scores. |
| mesh_describe_toolA | Inspect the full JSON schema and detailed parameter specifications of a specific tool before invoking it. |
| mesh_invoke_toolC | Directly execute any tool on a downstream MCP server. Pass server ID, target tool name, and input arguments dictionary. |
| mesh_statusA | Inspect real-time gateway statistics: connected downstream servers, total tools indexed, and estimated context token savings. |
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 4 tools
Each tool targets a distinct stage of the gateway workflow: search (discovery), describe (schema inspection), invoke (execution), and status (monitoring). There is no meaningful overlap, and boundaries are reinforced by clear verb choices.
All tools share a consistent 'mesh_' prefix with snake_case, and three follow a verb_noun pattern (describe_tool, invoke_tool, search_tools). mesh_status is a noun-style name, a minor deviation from the otherwise predictable convention.
Four tools is tightly scoped to the meta-server/gateway purpose: discover, inspect, invoke, and monitor. Each tool earns its place with no redundancy or filler.
The search -> describe -> invoke lifecycle is fully covered, with status for observability. Minor gaps exist, such as listing connected servers or refreshing the tool index explicitly, but agents can work around these via status and search.