Should I use http or stdio?

Use http for cloud or multi-instance deployments. stdio servers run as local subprocesses and are not shared across instances.

Are MCP server settings exported with an agent?

No. Agent configuration export includes identity files and skills, but never model keys, MCP servers or channels.

Integration · Runtime

Give FastClaw agents external tools through the Model Context Protocol — add http or stdio MCP servers per agent from the console.

Each agent has its own MCP list, so tools stay scoped to the agents that should have them.

Connect remote servers by URL with optional headers, or launch local servers as subprocesses with a command, args and env.

MCP tools sit next to built-in tools, installed skills and plugins in every conversation.

Let a team agent query your databases, ticketing or internal APIs — see FastClaw for teams.
Extend an agent beyond its skills with any MCP-compatible tool server.
Run tool-heavy work safely by combining MCP with a Docker or E2B sandbox.

Open the agent in the console and go to its MCP tab.
Click Add server, give it a name and choose a type:
- http — enter the URL and optional headers (one KEY=VALUE per line).
- stdio — enter the command, arguments and environment variables.
Save. The server's tools are available to the agent in its next conversation.