Airspeed MCP Server
Last updated: September 11, 2026
The Airspeed MCP server connects your AI assistant (Claude, and other MCP-capable clients) to your Airspeed data. Ask questions about calls, playbooks, and agent runs from the tool you already use.
You sign in with your Airspeed account. The server is read-only: it never creates, edits, or deletes anything in Airspeed.
Before you begin: If you previously set up the API-key MCP (see legacy documentation here), remove that connection first — delete the old connector in Claude before adding the new one. Running both at once causes duplicate tools and sign-in conflicts.
Connect
Server URL: https://mcp.goairspeed.com/mcp-oauth
Auth: sign in with your Airspeed account in the browser. No install, no API key.
Claude
Open Claude (web or desktop).
Go to Customize → Connectors and add a custom connector.
Paste https://mcp.goairspeed.com/mcp-oauth as the server URL.
Sign in with your Airspeed account when prompted.
[SCREENSHOT: Claude "Add custom connector" dialog with the server URL https://mcp.goairspeed.com/mcp-oauth pasted into the URL field]
To check it worked, ask: "List my 5 most recent Airspeed calls." If you see real titles, you're connected.
Other clients
Any client that supports a remote MCP server with OAuth can connect the same way: add the server URL, then sign in with Airspeed when asked. Claude is the client we support today.
What you can access
MCP never gives your assistant more access than you have in Airspeed. Calls are available only when you can read them in full. This includes private calls you participated in. Agent run outputs are limited to your own runs, including for admins.
Data | Available |
|---|---|
Call list, details, and transcript snippets | Yes, for calls you can read in full, including summaries, extracted insights, and transcripts |
Recordings | Yes, as a link that expires after 24 hours |
Private calls | Only calls you participated in |
Playbooks | Yes |
Agent runs | Your own scheduled or event-triggered run outputs |
If you ask for a call you don't have access to, the assistant simply won't find it. The server never reveals that a call exists.
What you can ask
A few starting points:
List my 5 most recent Airspeed calls.
Summarize my last call with Acme.
What came up in this week's calls about pricing?
Show me the playbook for discovery calls.
Behind the scenes, the assistant uses these tools:
To… | Tools |
|---|---|
Find calls |
|
Read a call |
|
Read playbooks |
|
Read agent runs |
|
Limits
Up to 100 results per request.
Call recordings are temporary links (24 hours).
Permissions and security
You sign in as yourself. The server uses your Airspeed identity. There is no shared organization key.
You only receive data you are allowed to access in Airspeed. Private calls are participant-only; agent run outputs are owner-only.
All tools are read-only.
Call transcripts contain what people said on the call. Treat the assistant's answers as information, not as instructions to follow.
Troubleshooting
Sign-in fails or drops: try connecting again. The handshake sometimes needs a retry.
No tools appear: disconnect the connector and add it again.
Your organization uses an allowlist: ask IT to allow
mcp.goairspeed.com.
If you have questions about the MCP server, reach out to support@airspeed.ai.