Skip to content
YouCanBookMe logo

YouCanBookMe MCP server

YouCanBookMe is an online scheduling tool that helps you manage appointments and bookings efficiently.

YouCanBookMe is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
3
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the YouCanBookMe MCP server

Connect YouCanBookMe once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches YouCanBookMe and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

YouCanBookMe tools your AI can run

Once connected, your assistant can call any of these YouCanBookMe actions by asking in plain language.

  • Create Profile

    Create a new profile in YouCanBookMe

    8 fields

  • Retrieve Booking by ID

    Retrieve a booking by its ID from YouCanBookMe

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

YouCanBookMe events your agent can watch

These start a run the moment something happens in YouCanBookMe, so work gets picked up on its own.

  • New Booking

    Trigger when a new booking is made

    1 field

YouCanBookMe MCP, answered.

No. That is the point of it. One Activepieces server exposes YouCanBookMe alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect YouCanBookMe in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 3 tools, including Create Profile, Retrieve Booking by ID, Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.