Everything finch does, for anyone who signs up: services, machines and keys, OAuth connectors, streaming, the CLI and the agent guide. Signing up takes you to your fleet page, where your machines and services show up once finch is installed.
Create a free accountLocalhost, with a front door.
finch gives the MCP server on your Mac or Linux machine a stable https address, with keys or OAuth at the door. Your machine calls out to finch, so nothing on it is left open.
- A tools/call from Claude, with its key
- finch, with the key already taken off
- The answer, streamed back as it is written
Left to right: your machine, the finchmcp.com relay, then Claude, Cursor and ChatGPT.
Every service gets a band that stays put
Birders ring a bird once and know it wherever it lands. finch does the same for your server: one address that stays the same across restarts, reboots and new networks.
sunny-wren-42- your account address (finch picks it)
.finchmcp.com- the relay
/notes- the name you chose
/mcp- where clients connect
It streams for as long as your tool keeps talking
Each mark is one event from a long tools/call: progress, partial results, the final answer. finch passes them through the moment they arrive, and there is no 30-second cutoff.
Turn the dial to choose who gets in
A key per client
Mint one for each client that should get in. Revoke one and that client is turned away on its next request. The others keep working.
finch keys mint cursor --service notesHand your agent one paragraph
It installs finch, publishes your server, proves it works and connects it to itself. The one step that needs you is a tap on your phone.
Read https://finchmcp.com/agents.md and use finch to publish my MCP server on http://127.0.0.1:8000 as notes. Show me the sign-in link when you get it. Run it as a background service, check it with finch test, then connect it to this agent.
curl -fsSL https://finchmcp.com/install | sh
finch login
finch add notes --service http://127.0.0.1:8000
finch service install$ curl -fsSL https://finchmcp.com/install | sh
finch: installed to /usr/local/bin/finch
$ finch login --start --json
{"schema_version":1,"expires_in":600,"interval":3,"user_code":"QKTM-8FWD",…}
Open finchmcp.com/cli and approve QKTM-8FWD
$ finch login --poll --json
{"schema_version":1,"account":"you@example.com","status":"approved"}
$ finch add notes --service http://127.0.0.1:8000 --json
{"schema_version":1,…,"url":"https://sunny-wren-42.finchmcp.com/notes/mcp"}
$ finch service install --json
{"schema_version":1,…,"installed":true,…,"running":true,…}
$ finch test notes --json
{"schema_version":1,"ok":true,"service":"notes","tools":[{"description":"…","name":"search_notes"},…]}
$ finch connect notes --client claude-code --json
{"schema_version":1,"client":"claude-code",…,"name":"notes",…,"url":"https://sunny-wren-42.finchmcp.com/notes/mcp"}
notes is live and connected. Reload MCP servers to use it.Everything finch writes down
This is the whole record of a call, and finch logs notes shows it to you. Bodies pass through and are never stored. Traffic is encrypted on both hops, and Cloudflare decrypts it at its edge to route it, so finch is not end-to-end encrypted. The full privacy boundary
| Time | Status | Took | Caller | Route |
|---|---|---|---|---|
| 2026-09-27 14:02:05 | 200 | 212ms | claude-code on studio | /notes/mcp |
| 2026-09-27 14:01:26 | 200 | 48ms | oauth:user_2mXf8Q | /notes/mcp |
| 2026-09-27 14:00:47 | 200 | 1340ms | cursor on studio | /notes/mcp |
| 2026-09-27 14:00:08 | 200 | 96ms | claude-code on studio | /notes/mcp |
| 2026-09-27 13:59:29 | 200 | 3870ms | nightly-script | /notes/mcp |
| 2026-09-27 13:58:50 | 200 | 61ms | claude-code on studio | /notes/mcp |
| 2026-09-27 13:58:22 | 200 | 530ms | oauth:user_2mXf8Q | /notes/mcp |
Free. Enterprise when you need it in writing.
For companies running finch across many machines that need an SLA, priority support or a security review. Email Aviary, the maker of finch, at hello@aviary.run and a person will reply.
Email us