Servers
servers.yaml declares every server. Unless a server sets os or harnesses, it applies to all four harnesses (Claude Code, Codex, OpenCode and Pi) on every supported OS. The field reference is in the README.
| Server | Transport | Harnesses | OS | Needs |
|---|---|---|---|---|
playwright |
stdio |
all | all | the agent-browser skill |
playwright-auth |
stdio |
all | all | the agent-browser skill |
telegram |
http |
all | all | Docker |
safari-mcp |
stdio |
all | macOS only | /usr/bin/safaridriver |
playwright
An agent-only headless browser with an in-memory profile, for general web work.
- Transport:
stdio, started by~/.agents/skills/agent-browser/scripts/agent-browser-mcp, with a startup timeout of 30 seconds. - Harnesses: all four.
- Needs: the
agent-browserskill from fnayou/agent-skills.task installskips the server withMISSING: agent-browserand a hint when the script is absent. - Codex: the manifest sets
approval_mode: approveforbrowser_evaluate,browser_navigate,browser_clickandbrowser_close.
playwright-auth
An agent-only headed browser with a persistent profile, for sites the user signs in to. One agent at a time.
- Transport:
stdio, started by the sameagent-browser-mcpscript with the argumentauth, and a startup timeout of 30 seconds. - Harnesses: all four.
- Needs: the
agent-browserskill, as forplaywright.
telegram
Telegram account access through one shared HTTP server in Compose. It has read-only tools plus send_message and reply_to_message.
- Transport:
http, athttp://127.0.0.1:8765/mcp. One container serves all four harnesses, so Telegram sees one connection instead of one per client. - Harnesses: all four.
- Needs:
docker. The Compose servicetelegrammust be running:task telegram:up. - Source: chigwell/telegram-mcp, pinned to tag
v3.3.25and built from its upstream Dockerfile. - Setup: once per machine, with its own QR login. See Telegram: once per machine.
!!! warning "No authentication"
The port is published on 127.0.0.1 only, and the endpoint has no authentication. Any local process running as you can read and send messages with your account.
safari-mcp
Safari compatibility checks through Safari's built-in MCP server. One session at a time.
- Transport:
stdio, started with/usr/bin/safaridriver --mcp. - OS: macOS only (
os: [darwin]). The binary ships with macOS. - Harnesses: all four.
- Setup: enable Develop > Allow Remote Automation in Safari once.