Skip to main content

Overview

The ironclaw 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:
string
required
Server name (e.g., “notion”, “github”).
string
required
Server URL (e.g., “https://mcp.notion.com”).
string
OAuth client ID if authentication is required.
string
OAuth authorization URL (optional, can be discovered).
string
OAuth token URL (optional, can be discovered).
string
Comma-separated list of OAuth scopes to request.
string
Server description.
Examples:
Output:

remove

Remove an MCP server:
string
required
Server name to remove.
Example:
Output:

list

List configured MCP servers:
flag
Show detailed information including OAuth configuration.
Example:
Output (normal):
Legend:
  • ● - Enabled server
  • ○ - Disabled server
Output (verbose):

auth

Authenticate with an MCP server using OAuth:
string
required
Server name to authenticate.
string
default:"default"
User ID for storing the token.
Example:
OAuth Flow:
Dynamic Client Registration (DCR): If you add a server without --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:
string
required
Server name to test.
string
default:"default"
User ID for authentication.
Example:
Output (success):
Output (authentication required):
Output (connection failed):

toggle

Enable or disable an MCP server:
string
required
Server name.
flag
Enable the server.
flag
Disable the server.
If neither --enable nor --disable is specified, the server state will be toggled.
Examples:
Output:

Common MCP Servers

Popular MCP servers you can connect to:

Notion

Tools: Search pages, create/update pages, query databases, manage workspaces.

GitHub

Tools: Create issues, manage PRs, search repositories, update files.

Slack

Tools: Send messages, list channels, manage conversations.

Google Drive

Tools: Search files, read documents, list folders.

Configuration Storage

MCP server configurations are stored in:
  • Database: If connected, stored in the mcp_servers table
  • Disk fallback: ~/.ironclaw/mcp_servers.json
Authentication tokens are stored securely in the secrets store (encrypted with your master key).

Troubleshooting

If OAuth authentication fails:
  1. Verify the server URL is correct
  2. Check that your client_id is valid
  3. Ensure you have the required scopes
  4. Try re-authenticating: ironclaw mcp auth <name>
  5. Check server logs for errors
If ironclaw mcp test times out:
  1. Check your internet connection
  2. Verify the server URL is accessible
  3. Check firewall rules
  4. Try disabling VPN if applicable
If tools don’t show up after connecting:
  1. Verify authentication: ironclaw mcp test <name>
  2. Check server is enabled: ironclaw mcp list
  3. Restart the agent: ironclaw run
  4. Check agent logs for errors
If DCR fails:
  1. The server may not support DCR
  2. Register your application manually on the provider’s website
  3. Add the server with --client-id:

ironclaw tool

Manage WASM tools

ironclaw status

View MCP server count