MCP Server
MCP Server
Drive MeshMesh agents from Slack, Claude, or any MCP client
MeshMesh exposes a remote MCP server so you can start and steer agents, manage references, and browse your Library from any Model Context Protocol client — Slack, Claude, or one you build yourself.
You connect your MCP client to MeshMesh; the client's model then calls MeshMesh tools on your behalf. Everything runs against your own workspace, scoped to your identity and role.
Not the same as a Custom MCP. Adding a custom MCP (Adding Integrations) connects an outside MCP server into MeshMesh so your agents can use its tools. The MeshMesh MCP server is the opposite direction: it lets an outside client drive MeshMesh.
What you can do
- Run agents — start one, approve its plan, send follow-ups, and switch between plan and build mode.
- Track work — check agent status, read plans, and open artifacts.
- Manage references & connections — create, update, and attach them to agents.
- Browse the Library — search references, skills, and collections; admins can review and curate.
- See what your team is doing — a workspace-wide feed of recently completed agent runs (where enabled).