Synopsis
Description
mcp manages connections to external MCP (Model Context Protocol) servers and can run profClaw itself as an MCP server. MCP servers expose tools that agents can call during execution. profClaw can connect to multiple MCP servers simultaneously, making all their tools available to agents.
Subcommands
| Subcommand | Alias | Description |
|---|---|---|
status | - | Show connection status for all configured MCP servers |
list-tools | tools | List all tools from connected MCP servers |
connect <name> | - | Connect to a configured MCP server |
disconnect <name> | - | Disconnect from an MCP server |
serve | - | Start profClaw as a standalone MCP server (stdio mode) |
mcp status
Output as JSON with server name, transport, connection status, and tool count.
mcp list-tools
Lists all tools currently available from connected MCP servers, grouped by server.
Output as JSON with tool name, server, and description.
mcp connect <name>
Name of the MCP server as defined in your profClaw config.
Output connection result as JSON.
mcp disconnect <name>
Name of the MCP server to disconnect.
mcp serve
Starts profClaw as a standalone MCP server over stdio. Use this to connect profClaw’s tools to Claude Desktop, Cursor, or any other MCP-compatible client. Requires a production build (pnpm build).
Examples
MCP Server Configuration
Configure MCP servers inconfig/settings.yml:
Claude Desktop Integration
To use profClaw tools in Claude Desktop, add toclaude_desktop_config.json:
Related
profclaw tools- Built-in tools (no MCP server needed)profclaw plugins- Plugins can also provide tools- MCP Integration Guide - Setting up MCP connections