← Registry

Productivity

yoya.ai

This MCP server enables scheduling and managing appointments via Yoya booking pages.

1 endpoint4 known toolsFirst detected September 1, 2026Last detected September 1, 2026

ENDPOINT 1

https://yoya.ai/api/mcp/book

No auth detected

MCP server metadata

Name
yoya-booking
Version
1.0.0
Capabilities
tools.listChanged

Known tools 4

get_booking_page

Look up a public Yoya booking page.

Inferred read-only
list_available_times

Return the open time slots for a booking page, identified by its slug or its full link.

Inferred read-only
book_meeting

Book a meeting on a host's page.

Inferred read-only
get_booking

Look up a booking by its manage token (the code in a yoya.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yoya-booking]
url = "https://yoya.ai/api/mcp/book"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "yoya-booking": {
      "type": "http",
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: yoya-booking
Remote MCP URL: https://yoya.ai/api/mcp/book

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "yoya-booking": {
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "yoya-booking": {
      "type": "http",
      "url": "https://yoya.ai/api/mcp/book"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "yoya-booking",
  "transport": "streamable-http",
  "url": "https://yoya.ai/api/mcp/book"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.