MCP servers
Attach remote Model Context Protocol servers as tools
No coding required. If you have never used an API key before, follow the walkthrough below step by step. Developers can skip to Quick reference at the bottom
Connect in Airbox
- Dashboard → Connections → + MCP server
- Enter the MCP server URL your tool provides
- For a hosted server with OAuth (e.g. Linear, Sentry): leave the token blank, save, then click Authorize — you'll be redirected to approve access (Airbox registers itself automatically via Dynamic Client Registration)
- For a server with a static token: paste it as the authorization token
- In inbox routing, check this server under MCP attachments
- Your LLM provider connection still runs the model — MCP supplies tools
Open the dashboard in a new tab if you want to follow along
Route your inbox
Your Airbox address does not use a connection until you attach one:
- In the Inboxes card, find your Airbox address
- Click the gear icon (⚙) on that address to open routing settings
- Under "AI, LLM or MCP provider", choose the connection you just added from the dropdown
- Leave "Email a reply back" checked if you want results in your inbox (recommended)
- Click "Save"
Try it — send an email
Subject: (* @claude #summarize *)
New to commands? See copy-paste examples and the syntax cheat sheet
Quick reference
| Dashboard type | mcp |
| Email targets | @linear, @your-server |
| Default model | — |
| Auth | URL and credentials from your MCP server operator |
Short checklist
- Add mcp connection with the server URL
- Authorize (OAuth) or paste a static token
- Attach on inbox
What you get
- Provider-agnostic tools (any inbox LLM)
- OAuth (RFC 9728/8414/7591 + PKCE) or static-token auth
- Hosted servers (Linear, Sentry, …) and custom internal servers
Notes
- OAuth tokens are refreshed automatically; secrets are encrypted at rest.
- Some hosted servers (e.g. Vercel MCP) only allow vendor-approved clients and may reject Dynamic Client Registration.