Documentation Index
Fetch the complete documentation index at: https://mintlify.com/logicminds/ironclaw/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Theironclaw mcp command manages Model Context Protocol (MCP) servers. MCP servers are hosted tool providers that expose capabilities through a standardized API.
MCP allows you to connect to external services like Notion, GitHub, Slack, and more without installing separate tools.
Subcommands
add
Add a new MCP server:Server name (e.g., “notion”, “github”).
Server URL (e.g., “https://mcp.notion.com”).
OAuth client ID if authentication is required.
OAuth authorization URL (optional, can be discovered).
OAuth token URL (optional, can be discovered).
Comma-separated list of OAuth scopes to request.
Server description.
remove
Remove an MCP server:Server name to remove.
list
List configured MCP servers:Show detailed information including OAuth configuration.
●- Enabled server○- Disabled server
auth
Authenticate with an MCP server using OAuth:Server name to authenticate.
User ID for storing the token.
--client-id, IronClaw will attempt Dynamic Client Registration:
Not all MCP servers support Dynamic Client Registration. If DCR fails, you’ll need to register your application manually and add the server with
--client-id.test
Test connection to an MCP server and list available tools:Server name to test.
User ID for authentication.
toggle
Enable or disable an MCP server:Server name.
Enable the server.
Disable the server.
If neither
--enable nor --disable is specified, the server state will be toggled.Common MCP Servers
Popular MCP servers you can connect to:Notion
GitHub
Slack
Google Drive
Configuration Storage
MCP server configurations are stored in:- Database: If connected, stored in the
mcp_serverstable - Disk fallback:
~/.ironclaw/mcp_servers.json
Troubleshooting
Authentication fails
Authentication fails
If OAuth authentication fails:
- Verify the server URL is correct
- Check that your
client_idis valid - Ensure you have the required scopes
- Try re-authenticating:
ironclaw mcp auth <name> - Check server logs for errors
Connection timeout
Connection timeout
If
ironclaw mcp test times out:- Check your internet connection
- Verify the server URL is accessible
- Check firewall rules
- Try disabling VPN if applicable
Tools not appearing
Tools not appearing
If tools don’t show up after connecting:
- Verify authentication:
ironclaw mcp test <name> - Check server is enabled:
ironclaw mcp list - Restart the agent:
ironclaw run - Check agent logs for errors
Dynamic Client Registration fails
Dynamic Client Registration fails
If DCR fails:
- The server may not support DCR
- Register your application manually on the provider’s website
- Add the server with
--client-id:
Related Commands
ironclaw tool
Manage WASM tools
ironclaw status
View MCP server count
