MCP Servers
MCP (Model Context Protocol) is the standard interface for giving agents tools. flamel ships eight servers pre-wired — no configuration needed. Supported providers can use them in every session.
| Server | What it does |
|---|---|
flamel_mcp | Plans, file ops, shell commands, code search, UI interactions |
git_mcp | Git operations + GitHub/Gitea API (PRs, issues, CI runs) |
docs_mcp | Fetch library documentation by package name and topic |
db_mcp | Read-only queries against SQLite, PostgreSQL, and MySQL |
browser_mcp | Headless Chrome — navigate, screenshot, click, scrape, test |
viz_mcp | Render charts, diagrams, and metrics inline in chat |
memory_mcp | Persistent memory across sessions — tagged, searchable |
shell_mcp | Interactive terminals — long-running processes, stdin/stdout |
Adding custom MCP servers
You can connect any MCP-compatible server in Settings → MCP. Both stdio and SSE transports are supported. Custom servers are available alongside the built-in ones in every session on that server.
MCP servers run as separate processes managed by
flamel_server. They are spawned on demand and restarted automatically if they crash. Each server has access to session credentials (Git tokens, etc.) via injection — not environment variables.