MCP

Both sides of the protocol.

Fathom speaks Model Context Protocol in both directions: workers can consume tools from configured external MCP servers and expose the currently registered built-in tools to MCP clients. Browser and computer tools appear only when their CDP or COMPUTER_URL integrations are configured and reachable.

Client

Consume any MCP server

stdio and Streamable HTTP transports, dynamic tool discovery and reconnect for configured external servers. Tools of connected MCP servers become first-class agent tools — no code changes.

# ~/.fathom/config.toml
[[mcp.servers]]
name = "postgres"
transport = "stdio"
command = "npx"
args = ["-y", "@modelcontextprotocol/server-postgres"]

[[mcp.servers]]
name = "remote"
transport = "http"
url = "https://mcp.example.com"

Server

Expose the whole toolbox

fathom mcp-serve exposes the registered built-in tools over MCP and executes tools/call — an MCP client can drive configured web, extraction and memory workflows through Fathom; browser automation is available when CDP is configured and reachable, with side effects subject to governance.

Browse the tools

fathom mcp-serve

# tools/list → registered tools such as
#   web_search, memory_search, hub, daemon, …
#   browser_* appears when CDP is configured/reachable
# tools/call → execution subject to policy and approvals

Transports

stdio for local servers, Streamable HTTP for remote — both client and server side.

HTTP auth

Configured HTTP MCP servers can use the authentication settings supported by their transport.

Discovery

Tools are discovered dynamically at startup and after reconnects.

Reconnect

Configured stdio/HTTP servers may reconnect after a drop, depending on transport and runtime settings.