FreeSince v1.4.0

Connect your AI

Let the assistant you already use run this site by talking to it — take a booking, add a service, set someone's hours. It is off until you turn it on, and it can only do what you switch on.

Updated November 16, 2026. Applies to Schedopia 1.5.6.

The Connect your AI tab showing the status card with the endpoint, and the three-step set-up rail
Schedopia → Settings → Connect your AI.

What this is

Assistants like Claude, Cursor and Codex can use tools on your behalf. They find those tools through a standard called MCP — the Model Context Protocol. Schedopia publishes its admin screens as MCP tools, so once a client is connected you can write what you want instead of clicking through the admin:

  • “What’s on today, and is anyone free at four?”
  • “Book Sam in with Maya tomorrow at eleven for a cut and finish.”
  • “Add a Hair spa service, 45 minutes, $35, under a new Hair category.”
  • “Maya works Tuesday to Saturday, ten till six, with an hour at one.”
  • “Block next Monday — the studio is closed.”
  • “How did last month compare with the one before?”

The assistant is not given a copy of your data. Each question becomes a call to this site, answered live, and every call is written to the call log.

The honest other half: whatever the assistant reads in an answer is seen by the company that makes it — the client you chose and approved, and nobody else. Nothing is sent anywhere beyond that. What it can read at all is decided by the Permissions switches, so if customer records should never leave the site, leave the customer tools off.

Those switches are also the only per-tool control you get. A connection carries whatever your WordPress account can do; it is the switches, not the connection, that decide which of the 51 tools an assistant may touch.

Fifty-one tools

Everything you can do on the admin screens, an assistant can do too — bookings, services, add-ons, staff, working hours, customers, payments, venues, events, seat layouts, the booking form's design and your settings. The full list is on the next page.

A booking an assistant takes is an ordinary booking: it goes through the same path as one made on your form, so the customer gets the same confirmation email and the same reminder before the appointment — nothing is silent.

Before you start

You need Why
WordPress 6.9 or newer The tools are registered through the Abilities API, which arrived in 6.9. On anything older the tab shows “Needs WordPress 6.9” and the switch is disabled.
An AI client that speaks MCP Claude Code, Cursor, Codex, Claude Desktop, claude.ai and ChatGPT all do. Others that support “custom MCP servers” work the same way.
HTTPS, ideally Everything works over plain http except the clients that sign in — see below. A certificate is usually free from your host.
A WordPress account with Schedopia permissions The assistant acts as you. It can never do something your own account could not.

Already run the WordPress MCP Adapter for other plugins? Schedopia’s tools are registered as WordPress Abilities, but they are not offered through the adapter, and there is no switch for that in the admin in 1.5.1. Connect to the endpoint on this page instead; it works with or without the adapter installed.

Turning it on

  1. Open the tab
    Go to Schedopia → Settings → Connect your AI. Since 1.5.5, Connect your AI is also in Schedopia’s sidebar, under Utility.
  2. Switch on “Allow AI clients to connect”
    The badge at the top of the card changes from Paused to Ready.
  3. Note the endpoint
    The address underneath is what a client connects to — https://your-site.com/wp-json/schedopia/mcp. There is a copy button beside it. It is not a secret, and it answers nothing without a credential.

Nothing is exposed by the switch alone. A client still has to be given a credential, and a tool still has to be switched on, before anything happens.

Connecting a client

Two routes, and your client decides which one you take.

  • Using claude.ai, Claude Desktop or ChatGPT? → Sign in. No terminal, and nothing to copy.
  • Using Claude Code, Cursor or Codex? → Connect with a command.

There is a third route for scripts and for read-only access — a token you make by hand. Two words cover everything here: a connection is what the wizard creates for you, and a token is one you create yourself. Underneath, a connection is either a WordPress application password or a Schedopia token, chosen for you by what your site supports; you never have to know which.

Signing in — claude.ai, Claude Desktop, ChatGPT

These clients cannot be given a header. They sign in to your site instead, the same way an app signs in with Google. Add the endpoint as a custom connector in the client, and it will:

  1. send you to your own WordPress login screen,
  2. show a consent screen naming the client and listing what it is asking for,
  3. connect once you approve — acting as the account you logged in with.

Nothing is created in advance and nothing is copied anywhere. You can withdraw a client at any time under Clients & activity, and it has to be approved again.

Under the surface this is ordinary OAuth 2.1 — dynamic client registration, so the client enrols itself with no key for you to paste, and PKCE with S256, so the approval cannot be intercepted and replayed. It is the same flow a hosted MCP server uses, running inside the plugin: no proxy, no Node process, nothing to install.

These clients require HTTPS

They refuse to sign in to a site that is not on HTTPS — that is their rule, not Schedopia's, and the tab says so when it applies. Use the command below instead, or ask your host for a certificate. On a local machine, define WP_ENVIRONMENT_TYPE as local in wp-config.php.

ChatGPT additionally needs Developer Mode, which is available on its paid plans.

Connecting with a command — Claude Code, Cursor, Codex

Under Set up there are three steps. The first picks your client, the second makes the connection, and the third gives you a command to paste into a terminal with the connection’s secret already in it.

  1. Choose your client
    Claude Code, Codex or Cursor. The command in step 3 changes to match.
  2. Create the connection
    Give it a name you will recognize later — “Laptop,” “Studio iMac.” Leave the box blank and it is numbered for you.
  3. Run the command
    Copy it and paste it into a terminal. In Claude Code, type /mcp afterward and schedopia is listed. In Codex, restart it first. In Cursor, look under Settings → MCP.
The credential is shown once

It is embedded in the command on screen and never shown again. Copy the command before you leave the page. Losing it costs nothing — create another connection and revoke the old one.

The command, per client:

Claude Code

claude mcp add --transport http schedopia \
  https://your-site.com/wp-json/schedopia/mcp \
  --header "Authorization: Basic …"

Then type /mcp in Claude Code to confirm schedopia is connected.

Codex

codex mcp add schedopia -- npx -y mcp-remote \
  https://your-site.com/wp-json/schedopia/mcp \
  --header "Authorization: Basic …"

Restart Codex afterward; schedopia then shows up under /mcp.

Cursor

cursor mcp add schedopia \
  --url https://your-site.com/wp-json/schedopia/mcp \
  --header "Authorization: Basic …"

Check Settings → MCP in Cursor.

The tab writes your real address and your real credential into these — the versions above are only here to show the shape. Copy from the tab, not from this page.

More than one connection

Create one per machine or per client, and name each one. That way revoking your old laptop does not disconnect your desktop. Where you revoke one depends on what it was made from — the tab says which when it creates it, and the next page lists all three places.

Tokens, made by hand

Under Clients & activity there is a third way in: a token you create yourself and send as Authorization: Bearer …. Use one when you want something the one-click button does not offer:

  • Read-only access. A token can be marked read, write, or both. A connection cannot — it carries whatever your account can do, governed by your switches.
  • An expiry date. Set a number of days and it stops working on its own.
  • A script rather than an assistant — anything that can send a header.

Like a connection, a token is shown once. Each one lists what it can do, whose account it acts as, when it was last used and when it expires, and has its own Revoke button.

A credential over plain http can be read on the way

On a site without HTTPS, anything sent as a header travels in the clear. It works, and it is the right choice on a machine of your own, but it is not what to run a real business on.

Testing the connection

Test connection, next to the create button, makes a throwaway credential, asks this site to call its own endpoint with it, deletes the credential and tells you what happened. Nothing is left behind whether it passes or fails.

Result What it means
It answered The endpoint is reachable and the credential arrived intact. A client will work.
The header was stripped Your web server drops Authorization before WordPress sees it. How to fix it.
Unreachable The site could not call itself. Usually loopback requests are blocked on the host.

Run checks, at the top of the page, is the wider version: it runs the three Site Health checks and reports anything failing inline. See Site Health checks.

Next