MCP servers

Connect Model Context Protocol servers from the catalog or with custom entries.

Catalog and custom servers

Enable MCP servers from the curated catalog or define custom entries. The daemon writes enabled servers into the agent configuration.

Curated entries ship with the daemon and only need a credential — pick one, paste a token, and it works. Custom entries are for self-hosted or per-install services where the connection itself is configuration, not a secret (your own Postgres URL, a self-hosted Firecrawl, a local Ollama).

Transports

MCP servers can use streamable HTTP, SSE, or stdio. Stdio servers run as subprocesses in the agent container and may declare packages that must be installed into the Docker image.

Tool filters

Use tool filters to allow or deny specific MCP tools. Safe defaults are useful when a server exposes both read-only and write-capable tools.