Use this guide with any AI assistant

Download it as a prompt file, paste it into Claude, ChatGPT, Gemini or any LLM, and it will walk you through every step interactively.

PageMotor · AI

Ask your studio with Claude

Plain-English answers about your own business, straight from your site, on the Claude account you already have. No API key, no extra cost, nothing new to install. The free plan can do this too.

⏱ 5 minutes to connect 💳 Uses your own Claude plan, Free included 🔒 Read-only 🧩 Works in claude.ai, Desktop, Cowork June 2026 · updated August 2026

Your PageMotor site can answer questions about your business in plain English, using your own Claude account. It works because your site already speaks Claude’s connector language. You point Claude at your site once, sign in as the studio admin, and then you just ask.

What you need

A Claude account. Free, Pro, Max, Team and Enterprise all work. On the free plan you may hold only one custom connector, so your studio would be it. On Team and Enterprise an Owner adds the connector for the organisation, then each member switches it on for themselves.
Your PageMotor studio site (running the EP studio suite), on PageMotor 0.10 or later.
Your PageMotor admin login for that site.

Check your version first. The sign-in step below arrived in PageMotor 0.10. On 0.9.x there is no sign-in flow to complete, and worse, the connection appears to succeed: your site answers anonymously at read-only tier with no error, so you get a connector that looks fine and can see almost nothing. If you are on 0.9.x, upgrade before following this guide.

Connect it (claude.ai, in a browser)

Claude’s connector screen changed in August 2026. There are new choices about how Claude signs in, and one of them is labelled Recommended but does not work with PageMotor. The good news is that Claude now inspects your site and picks the right settings for you, so the job is mostly to check its work and leave it alone. The steps below are the current ones.

▶ Watch the whole thing (two minutes and thirteen seconds), or read the steps below. Narrated, with captions.

Read the transcript instead

The change. Claude’s custom connector screen changed in August 2026. If you connect a PageMotor site to Claude, two things are different, and one of them can stop you getting in.

Step one. Adding a connector is now two steps. First you give it a name, and the address of your site’s connector: your site’s web address followed by /mcp/, all lower case, keeping the trailing slash. Then Claude reads your site before it shows you anything else.

Step two. What comes back is a panel with the answers already filled in. Authentication is set to Always required, marked Detected. OAuth client is set to No client ID, register one automatically, also marked Detected. For a healthy PageMotor site both are correct, so change nothing and press Add.

The trap. The first OAuth option is labelled Recommended. It uses client details hosted by Anthropic, and PageMotor has no code for it, so sign-in stops on a page reading Unknown client. The label to trust is Detected, not Recommended. The third option, use your own OAuth client, fails differently, on a page reading Invalid resource. Leave both alone.

After sign-in. Every tool your site offers is listed, and each can be set to always allow, ask first, or never. A studio connector is read-only, so always allow is safe. If you would rather watch it work for a week, set the group to ask.

Open claude.ai and go to Customize → Connectors (straight there: claude.ai/customize/connectors).
Click Add, then choose Add custom connector. Give it a name like My Studio, and for the address enter your site’s connector URL: https://YOUR-SITE/mcp/, all lower case, trailing slash included. For the demo site that is https://sundial.solasyogastudio.com/mcp/.
Read the address back before you go further. It should be character for character what you typed, capital letters included. If it is not, see the box below.
Claude now reads your site and fills the rest of the dialog in by itself. It should look like this.

Add custom connector

My Studio

https://sundial.solasyogastudio.com/mcp/

Authentication

Always required Detected1 Each user signs in through the server’s OAuth flow before they can use any tools or resources.

Required when the server asks

None

OAuth client

Use Anthropic’s hosted client metadata Recommended! The server reads Claude’s client details from a URL Anthropic hosts (CIMD). Nothing to set up, but the server must support it.

No client ID — register one automatically Detected2 Claude registers OAuth clients with the server as users connect (DCR).

Use your own OAuth client ! Enter a client ID you registered with the server yourself.

Additional request headers 3

Leave empty. PageMotor needs none.

Advanced › Transport 3

Leave on Streamable HTTP. PageMotor has no SSE endpoint.

Back Add

1Always required is right for PageMotor 0.10 and later. Claude works this out from your site, which is itself a good sign: it means the discovery documents answered.
2No client ID is right for PageMotor. Your site mints Claude a client of its own on the spot.
!Do not touch either of the other two OAuth options, including the one marked Recommended. PageMotor supports neither, and both fail after you have already signed in. See the OAuth client traps.
3Nothing else needs changing. Headers stay empty, transport stays as it is.

The dialog as Claude fills it in for a healthy PageMotor site. If yours looks like this, press Add.

Press Add. Claude sends you to a sign-in page. Log in with your PageMotor admin account and approve access. That is what lets Claude read your studio data on your behalf.
Decide what it may do. The connector’s settings page now lists every tool your site offers, each set to always allow, ask first, or never. Your studio connector is read-only, so leaving them all on Always allow is safe and saves you a click per question. If you would rather see what it is doing at first, set the group to ask for a week.

My Studio

https://sundial.solasyogastudio.com/mcp/

Tool permissions

Choose when Claude is allowed to use these tools.

Other toolsAlways allow

studio overview✓✋⊘
upcoming schedule✓✋⊘
members at risk✓✋⊘
waiver gaps✓✋⊘

Every tool your site offers, each set to always allow (tick), ask first (hand) or never (crossed circle). The dropdown at the top of a group sets them all at once.

Start a new chat, click the + at the lower left of the message box, hover Connectors, and switch My Studio on for that chat. Then ask away.

It is the same in Claude Desktop and Cowork (Customize → Connectors → add custom connector), and in Claude Code you add it as an MCP server instead. Use whichever Claude you already use, with one plan note: claude.ai, Desktop and Cowork all work on the free plan, but Claude Code needs a paid plan (Pro, Max, a Team or Enterprise premium seat, or a Console account).

If sign-in fails, the message on the page tells you which of two things went wrong. A page reading “Unknown client” means the wrong OAuth client option is selected: go back and choose No client ID, whatever the Recommended label says. A page reading “Invalid resource” with an empty Received value is the address: claude.ai remembers a connector address per domain and can quietly substitute an older one for the address you just typed, often with a capital /MCP. The quickest fix there is to connect on the www form instead, https://www.YOUR-SITE/mcp/, which the stale entry cannot attach to. Full explanation of both, and the options for sites with no www: why it will not connect.

What you can ask

Anything the dashboard knows, in your own words:

“How is the business doing this month?”
“Who is most at risk of leaving, and why?”
“Which classes next week are nearly full or nearly empty?”
“Who has not signed a waiver before their next class?”
“Whose class-pass credits are about to expire?”
“What does payroll owe instructors, and who is teaching today?”

Claude pulls the live figures and answers in seconds.

It is read-only. Claude can see everything and tell you about it, but it cannot make a booking, grant a pass, run payroll or change a setting. It will point you to the right screen in your dashboard to do that yourself.

Good to know

It is your own Claude account doing the work. No API key and no per-question charge. Questions come out of the usage allowance your plan already gives you, so on the free plan expect to run out sooner on a long session of questions.
It is your data, your account. You sign in as your own admin, so Claude only sees what you would see.
Self-hosting on your own server? If Claude says it could not register with your site’s sign-in service, your web server is almost certainly serving /.well-known/ from disk instead of handing it to PageMotor. The stock Let’s Encrypt block does this. The MCP troubleshooting guide has the test and the two-line nginx fix (section 6d).
You stay in control. Disconnect any time from your site’s Settings → Connected Apps, or from Claude’s own connector settings.

Prefer it built into the Admin?

There is also an “Ask” box that lives right inside your PageMotor Admin, so you never leave the dashboard. That version uses a small Anthropic API key (a few pennies of usage a day for typical questions) instead of your subscription. Same questions, same answers, just baked into the admin screen rather than your Claude app. Use whichever suits you.