Skip to main content
IronClaw can connect to any Model Context Protocol (MCP) server and expose its tools to the agent. MCP is an open standard for tool servers, with a growing ecosystem of pre-built servers covering databases, APIs, cloud services, and more.
IronClaw connects to MCP servers over HTTP transport using JSON-RPC 2.0. The stdio transport (subprocess pipes) is not yet supported.

​
Add a Server

To add a MCP server you can either directly request your agent to use it, or configure it via CLI:

​
Authentication

If your MCP server requires authentication, use the following command:

​
Listing Available MCP Servers

Once connected, MCP tools appear in the agent’s tool list alongside built-in tools. You can see them:

​
Removing an MCP Server

Remove a server with:

​
WASM vs MCP: When to Use Each

For integrations that handle sensitive credentials or untrusted external data, prefer WASM tools. The network proxy and credential injection model give you stronger isolation guarantees than an MCP server running as a separate process.