Developers & AI Agents
Aircover Developer & Agent Resources
Everything an AI agent or developer needs to work with Aircover: a remote MCP server, OAuth 2.0 authentication with scoped permissions, machine-readable site content, and self-serve onboarding.
MCP Server
Connect Claude, ChatGPT, and other agents to Aircover
Aircover exposes a remote Model Context Protocol (MCP) server over Streamable HTTP. Once connected, an agent can query meetings, transcripts, AI agent results, deal qualification data, reports, and indexed documents on behalf of an authenticated Aircover user.
Endpoint
https://api.aircover.ai/mcp
Transport: Streamable HTTP · Auth: OAuth 2.0 (PKCE, dynamic client registration) · Manifest: /.well-known/mcp.json
Available tools
Add to Claude Code
claude mcp add --transport http aircover https://api.aircover.ai/mcp
Add to claude.ai / other MCP clients
Add a custom connector with the URL https://api.aircover.ai/mcp. The client discovers OAuth automatically and walks the user through sign-in. An Aircover account is required — new users receive a trial license on sign-up.
Authentication
OAuth 2.0 with scoped permissions
API access is authorized via OAuth 2.0 authorization code flow with PKCE (S256) and dynamic client registration (RFC 7591) — agents can register a client, request only the scopes they need, and refresh tokens without human intervention beyond user consent.
Discovery endpoints
https://api.aircover.ai/.well-known/oauth-authorization-server
https://api.aircover.ai/.well-known/oauth-protected-resource
Both are also reachable from this domain — www.aircover.ai/.well-known/… redirects to the authorization server.
Scopes & permission model
mcp — grants access to the MCP tool surface only: read access to meetings, transcripts, AI agent results, deal qualification, reports, teams, and indexed documents. It does not grant account administration, billing, user management, or write access to CRM integrations.
Permissions are layered: a token's scope caps what the client may request, and every request is additionally bounded by the authorizing user's own role and organization — an agent can never see data the user themselves could not. Tokens are revocable at any time via the revocation endpoint.
Grant types: authorization_code, refresh_token · Response type: code · Token endpoint auth: client_secret_basic, client_secret_post · Scopes are requested at authorization time; request only what you need.
End-user sign-in supports Google OAuth, Microsoft OAuth, and enterprise OIDC/SSO. Personal email domains are not permitted — sign up with a work email.
Machine-Readable Site
Built for agents to read
- /llms.txt — full product context, when-to-use guidance, and integration docs for LLM agents.
- /.well-known/mcp.json — MCP server manifest (registry server.json format).
- /sitemap.xml — every page on this site.
- Markdown content negotiation — request any page on this site with Accept: text/markdown and receive clean markdown instead of HTML (acceptmarkdown.com convention).
- Real 404s — nonexistent paths return HTTP 404 with recovery links, never a soft-200.
curl -H "Accept: text/markdown" https://www.aircover.ai/platform
API Reference
OpenAPI specification & example requests
The public agent API — OAuth endpoints and the MCP endpoint — is described in an OpenAPI 3.0 specification with typed schemas, operation IDs, and descriptions on every operation (function-calling compatible): https://www.aircover.ai/openapi.json
1 · Discover the authorization server
curl https://api.aircover.ai/.well-known/oauth-authorization-server
2 · Register a client (RFC 7591 — no manual key issuance)
curl -X POST https://api.aircover.ai/oauth/register \
-H "Content-Type: application/json" \
-d '{"client_name": "My Agent", "redirect_uris": ["https://example.com/callback"],
"grant_types": ["authorization_code", "refresh_token"], "scope": "mcp"}'
3 · Authorize (browser) and exchange the code
curl -X POST https://api.aircover.ai/oauth/token \
-d grant_type=authorization_code -d code=$CODE \
-d redirect_uri=https://example.com/callback \
-d code_verifier=$PKCE_VERIFIER \
-d client_id=$CLIENT_ID -d client_secret=$CLIENT_SECRET
4 · Call the MCP endpoint
curl -X POST https://api.aircover.ai/mcp \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'
Webhooks (calendar, meeting lifecycle) and the full customer REST API are available to Aircover customers — contact [email protected].
Getting Started
Free trial, self-serve
Every new user gets a free trial license automatically on self-serve sign-up — no sales call, no contact form, no manual approval. Sign up with a work email via Google or Microsoft:
https://api.aircover.ai/login_google/?source=developers
https://api.aircover.ai/login_ms/?source=developers
Everything at Aircover is API-driven. For REST API access, custom integrations (Salesforce, HubSpot, Zoom, Teams, Meet, Highspot, Genesys, Outreach), or webhook documentation, contact [email protected] — or book a demo for a guided walkthrough.