Skip to main content
IronClaw connects to Model Context Protocol servers, giving your agent access to external tools and data sources without writing custom integrations.

Quickstart


Transports

HTTP with OAuth

Many hosted MCP servers require OAuth 2.1 authentication. IronClaw implements the MCP Authorization spec with PKCE:
OAuth tokens are stored securely via IronClaw’s secrets store and refreshed automatically.

stdio with Environment Variables

Stdio servers often need API keys or configuration via environment variables:

Configuration File

Server configs are stored in ~/.ironclaw/mcp-servers.json:
You can edit this file directly, or use ironclaw mcp add / ironclaw mcp remove to manage it.

Custom Headers

For servers that use API key authentication instead of OAuth:

Built-In Servers

IronClaw ships with a built-in registry of hosted MCP servers. A few examples: Browse more servers at:

Troubleshooting