Connect Yoya to your AI assistant

Use one server to manage your booking pages and another to let guests book through their AI assistants.

Last updatedSeptember 13, 2026

Yoya speaks the Model Context Protocol, so you can manage it from a compatible AI assistant, such as Claude Code, Cursor, Claude Desktop, Windsurf, and other MCP clients. Your agent sets up and manages your booking page. Guests can also use a compatible assistant to find an available time and book a meeting. Your plan’s booking limits still apply.

Step-by-step guides: Claude Code and Cursor. Both include a read-only connection check and the details to confirm before booking.

Two servers

  • Manage your Yoya https://yoya.ai/api/mcp. Sign in with your Yoya account when your client prompts you. Tools: create or update your booking page, set your weekly hours and date overrides, list your bookings, read meeting briefs, cancel or reschedule with your approval, get sharing links, and diagnose your setup.
  • Find & book (public, no sign-in) — https://yoya.ai/api/mcp/book. Tools: look up a booking page by its link, find times, preview and confirm a meeting, check its synchronization status, cancel, or reschedule with a private manage token. This is the side another person's agent uses to book with you.

Claude Code

Add either server from the terminal:

# Manage your Yoya (opens a browser to sign in)
claude mcp add --transport http yoya https://yoya.ai/api/mcp

# Find & book on Yoya pages (no sign-in)
claude mcp add --transport http yoya-book https://yoya.ai/api/mcp/book

Cursor and other remote MCP clients

For Cursor, merge these entries into your MCP configuration to add Yoya as a remote (Streamable HTTP) server:

{
  "mcpServers": {
    "yoya": {
      "url": "https://yoya.ai/api/mcp"
    },
    "yoya-book": {
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}

Some desktop clients don't yet speak remote MCP directly — in that case bridge with mcp-remote:

{
  "mcpServers": {
    "yoya": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://yoya.ai/api/mcp"]
    }
  }
}

Time zones and booking confirmation

Pass your IANA timezone when finding times. Responses include UTC timestamps and labels in that zone, with 20 results per page by default. Use from, to andnextCursor to narrow or continue the search. Callpreview_booking, review the details, then explicitly confirm. Calendar and notification status is reported separately from the reservation itself.

Signing in

The management server asks you to sign in and choose what your assistant can read or change. You can grant read access without allowing edits. Disconnect an app from Connected assistantsto revoke its access. After the authorization upgrade, existing connections need to reconnect once. Public guest booking needs no Yoya sign-in; private manage tokens authorize changes to individual bookings.

Codex

codex mcp add yoya --url https://yoya.ai/api/mcp
codex mcp login yoya

Interactive cards and compatibility

Clients with MCP Apps support can display a time picker and booking confirmation card. Other clients use the same tools in text. Yoya accepts MCP 2026-07-28 and stateless 2025 clients; OAuth supports CIMD and an explicit DCR compatibility option.

Connection troubleshooting

  • 401: reconnect and sign in again.
  • 403 with insufficient_scope: approve the specific permission your action needs.
  • 429: wait a minute before retrying.
  • No available times: ask the host to run diagnose_setup and check working hours and calendar access.
  • No cards: continue in text; availability depends on the client version and workspace policy.

Support

Questions? Email leo@yoya.ai.