Daemon-based architecture replacing slow MCP stdio servers with persistent UNIX socket daemons.
Main Repo • Docs • Quick Start
LLM agents make many sequential tool calls. MCP stdio servers spawn a new process for each call (~2.3s overhead). FGP keeps daemons warm and ready.
| Repository | Description | Status |
|---|---|---|
| fgp | Monorepo with all daemons and docs | ⭐ Start here |
| daemon | Rust SDK for building FGP daemons | Stable |
| daemon-py | Python SDK for building FGP daemons | Stable |
| protocol | FGP protocol specification | Stable |
| cli | CLI for managing FGP daemons | Beta |
| Repository | Integration | Speedup vs MCP |
|---|---|---|
| browser | Chrome DevTools Protocol | 292x |
| gmail | Gmail API | 69x |
| calendar | Google Calendar API | Beta |
| github | GitHub GraphQL + REST | 75x |
| fly | Fly.io deployments | Alpha |
| neon | Neon Postgres | Alpha |
# One-liner install
curl -fsSL https://raw.githubusercontent.com/fast-gateway-protocol/fgp/master/install.sh | bash
# Or install specific daemon
cargo install fgp-browser
# Start daemon (stays warm)
browser-gateway start
# Use it (sub-10ms responses)
browser-gateway open "https://example.com"
browser-gateway snapshot # Get ARIA tree┌─────────────┐ UNIX Socket ┌──────────────┐
│ AI Agent │ ◄──────────────────► │ FGP Daemon │
│ (Claude, │ NDJSON protocol │ (browser, │
│ Cursor, │ ~10-50ms latency │ gmail, │
│ etc.) │ │ etc.) │
└─────────────┘ └──────────────┘
Key design decisions:
- UNIX sockets — Zero network overhead, file-based permissions
- NDJSON protocol — Human-readable, streaming-friendly
- Per-service daemons — Independent scaling, fault isolation
- Rust core — Sub-millisecond latency, ~10MB memory per daemon
MIT