Every MeshMesh MCP tool, what it does, and its parameters
The tools your client sees depend on your role. Tools marked admin are hidden unless you are a workspace admin or owner. ? marks an optional parameter.
Start here. Most work is one loop: start_agent to kick off, get_agent_status to watch, get_plan / continue_agent to approve the plan and send follow-ups. The rest are for managing references, connections, and the Library.
Current state, what it's waiting for, a summary, recent messages, and artifacts
agentId
get_plan
Show an agent's plan and its approval state
agentId
edit_plan
Revise the plan with an instruction; the agent re-plans
agentId, instruction
Some agents can't be driven from MCP — for example ones started in an older version, or that use a desktop-only connection. list_agents flags these, and continue_agent explains why if you try.
Publishing a reference to your workspace isn't done over MCP — it goes through admin review (see the Library admin tools below). Ask an admin, or publish from the app.
See what others in your workspace are doing — a team-wide feed of recently completed agent runs, not just your own.
Tool
What it does
Parameters
get_workspace_activity_feed
Recent completed agent runs across your whole workspace
limit? (1–100), cursor?
Team activity isn't turned on for every workspace. If it's off for yours, this tool returns an error explaining that — reach out to your admin to enable it.