AgentMesh MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTMESH_DATA_DIR | No | Directory for project state. Defaults to `.agentmesh` in the current working directory. | |
| AGENTMESH_DURABLE_WRITES | No | Enable stronger power-loss durability by syncing each temporary state file before replacement. Set to `1` to enable. |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_contextA | Read a compact project snapshot: active agents, tasks, unread messages, artifacts, and decisions. |
| agent_manageC | Register an agent runtime or update its presence in the shared project. |
| task_manageC | Create, list, claim, update, or complete durable project tasks. |
| agent_messageC | Send, list, or acknowledge durable messages between project agents. |
| artifact_manageC | Publish, list, or read durable project artifacts by reference. |
| multimodal_analyzeC | Create a bounded multimodal analysis record for text or a local asset. This MVP reports provider readiness and never pretends provider-required work is complete. |
| design_checkC | Run baseline centralized design-system and accessibility checks against a UI summary and optional tokens. |
| change_proposeC | Record a proposed code or workspace change for later review and approval. |
| review_requestC | Create a review artifact and notify a reviewer agent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan-task | Create a small, reviewable implementation plan for an AgentMesh task. |
| review-change | Review a proposed change for correctness, safety, and project consistency. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| project-state | Compact shared state for the active AgentMesh project. |
| design-system-guidance | Compact baseline rules for consistent UI and UX work. |
TDQS
Scored across 9 tools
Most tools have clearly distinct domain+action targets. There is some adjacency between change_propose/review_request and review_request/artifact_manage, and between project_context and the individual list operations, but the descriptions make intended use clear.
All names use snake_case and mostly follow an entity_action pattern such as task_manage, agent_manage, artifact_manage, and change_propose. project_context and agent_message deviate slightly with entity_noun forms, and multimodal_analyze uses a qualifier_action form, but the overall convention is readable and predictable.
Nine tools is well within the ideal 3–15 range for an agent collaboration server. Each tool maps to a core domain capability without obvious redundancy.
Core create/list/update/read flows for agents, tasks, messages, and artifacts are present. However, there is no explicit approve/reject or review-decision operation despite change_propose and review_request implying a review lifecycle, and no delete/archive operations.