MCP Servers

MCP servers let you inject external Model Context Protocol tools into selected SwarmClaw agents.

Supported Transports

SwarmClaw supports:

  • stdio
  • sse
  • streamable-http

For stdio, configure a command and args.

For sse or streamable-http, configure a URL and any required headers.

Typical Workflow

  1. Create an MCP server definition.
  2. Test the connection.
  3. Inspect the discovered tools.
  4. Run conformance checks when needed.
  5. Assign the MCP server to one or more agents.
  6. Optionally disable individual MCP tools per agent.

What the UI Supports

  • connection testing
  • tool discovery
  • conformance checks
  • direct tool invocation for inspection
  • agent assignment through the agent editor

MCP tools appear alongside built-in tools during execution.

API

  • GET /api/mcp-servers
  • POST /api/mcp-servers
  • GET /api/mcp-servers/:id
  • PUT /api/mcp-servers/:id
  • DELETE /api/mcp-servers/:id
  • POST /api/mcp-servers/:id/test
  • GET /api/mcp-servers/:id/tools
  • POST /api/mcp-servers/:id/conformance
  • POST /api/mcp-servers/:id/invoke

CLI Examples

swarmclaw mcp-servers list
swarmclaw mcp-servers create --data '{"name":"Local MCP","transport":"stdio","command":"npx","args":["-y","some-server"]}'
swarmclaw mcp-servers test <serverId>
swarmclaw mcp-servers tools <serverId>
swarmclaw mcp-servers conformance <serverId>