MCP swap

Replace direct calendar API calls in an MCP-based agent with Openavail in one config change.

What is MCP swap

If your AI agent uses the Model Context Protocol (MCP) to call calendar tools, you can swap the calendar MCP server for the Openavail MCP server without changing your agent's code. Your agent continues calling the same tool names (check_availability, book_meeting) but the requests now flow through Openavail's arbitration layer.

How it works

The Openavail MCP server exposes the same tool interface as the standard Google Calendar and Outlook MCP servers. Under the hood:

1. The agent calls check_availability → Openavail calls POST /v1/availability on the agent's behalf
2. The agent calls book_meeting → Openavail calls POST /v1/bookings/{hold_id}/confirm
3. All requests are authenticated, arbitrated, and audited exactly as if the agent had called the REST API directly

MCP tool definitions

The Openavail MCP server exposes:

Tool	Maps to
check_availability	POST /v1/availability
book_meeting	POST /v1/bookings/{hold_id}/confirm
cancel_meeting	DELETE /v1/bookings/{event_id} (v1.5)
get_audit_log	GET /v1/decisions (v1.5)

cancel_meeting and get_audit_log are available in v1.5.

Migration path

1. Register your agent in the Openavail dashboard
2. Replace your MCP server config with the Openavail MCP endpoint and your API key:

{
  "mcpServers": {
    "calendar": {
      "url": "https://mcp.openavail.com/v1",
      "headers": { "Authorization": "Bearer ak_01HX7QQM…" }
    }
  }
}

3. Remove the direct Google/Outlook MCP server from your config

Your agent will now route all calendar operations through Openavail automatically.