PageMotor × Claude
01 / 09
The MCP connector

Connect
your site
to Claude

A short walkthrough for linking your PageMotor site to Claude through the MCP connector — so Claude can read and run your site with its own tools.

←→ or click to move through
Why connect

One link, full reach

Once connected, Claude works your site directly — through the same actions your admin already uses. The link is authenticated and action-capable: every request signs in, and Claude acts at your access tier.

Content

Write & edit

Draft, update, restructure, and publish pages and posts.

Design

Build themes

Create and restyle themes — templates, blocks, CSS, design tokens.

Site

Manage setup

Install plugins, adjust settings, handle users and updates.

Pick your path

Two ways to sign in

Path A

One-click sign-in

For anything you drive in a browser — Claude Desktop or claude.ai. Paste a URL, log in, approve. Nothing to copy or store.

Recommended for most people
Path B

Bearer token

For headless clients with no browser — Claude Code, the Claude API, CI, and scripts. Create a token once and pass it in a header.

Both end in the same kind of token — one-click sign-in just issues it for you, through your browser.

One-click sign-in · the short version

Four moves, no terminal

01
Paste your
MCP URL
02
Click
Connect
03
Log into
your site
04
Click
Approve

Next, the same three slides take these one at a time.

Step 1

Open the connector settings

Settings›Connectors›Add custom connector

In Claude Desktop, that's the path above. On claude.ai in a browser, add a custom connector the same way.

Step 2

Paste your MCP URL

https://<your-site>/mcp/

Swap <your-site> for your own domain and keep the trailing /mcp/. Click Connect and your browser opens on its own.

Step 3

Log in, then Approve

If you're not already signed in to your site, you'll land on its login page, then a consent screen. Click Approve — and you're connected.

The connection acts as you — the person who approves it — at your access tier. Approve as an admin and Claude gets admin reach; approve as a producer and it gets producer reach.

Path B · the headless route

Bearer token

For Claude Code, the Claude API, CI, and scripts — anything with no browser to click Approve.

1

In your site, open Manage API Access, create a token, pick a tier (admin / producer / read-only), and copy it — it's shown once.

2

Hand it to your client. For Claude Code:

claude mcp add <name> --transport http https://<your-site>/mcp/ \ --header "Authorization: Bearer <your-token>"

For the Claude API, set authorization_token on your /mcp/ entry in the mcp_servers array.

Before you go live

Two things to check

Serve over HTTPS

One-click sign-in needs TLS. An https:// site is required for the OAuth flow to run.

Behind nginx? Free the discovery paths

On CloudPanel / Plesk, the stock ACME rule can swallow /.well-known/oauth-*, so sign-in 404s after the first redirect. Let those paths reach PageMotor — the reverse-proxy doc has the one-line fix.

Then you're set — Claude and your site are linked.

Manage or revoke any connection anytime under Manage API Access › Connected Apps.