Hosted server

info

The hosted server needs a Pro or Pro+ account. Headless use with a deploy token needs Pro+.

Micropage also runs the MCP server for you. Your AI app connects to it over HTTPS and signs in with your Micropage account, so there is nothing to install and no CLI login. It offers the same tools as the local server, with the differences listed below.

The server URL is:

https://mcp.micropage.sh/mcp

How signing in works

The first time your app connects, it opens a Micropage sign-in page in your browser. After you sign in, a consent screen at app.micropage.sh shows:

the app's name and the address it will send you back to (only approve if you started the connection from that app);
the account you are signed in as, and its plan;
three extra permissions, all off. See Permissions.

Approve connects the app. Deny sends you back with nothing granted. On a Free account, the consent screen says that connecting AI apps requires the Pro plan and offers only Deny. The server also checks the plan on every call: if the account moves to Free after connecting, every tool except whoami and get_markup_reference is refused with PLAN_REQUIRED.

Apps register themselves the first time you connect, so the server URL is all you need. Because any app can register, the consent screen shows where it will send you back and warns when that isn't an app Micropage recognises. Only approve requests you started yourself.

Add it to your app

claude.ai, Claude Desktop, and Claude mobile

These three share one connector list, so adding the connector in one adds it in all of them.

Open Settings → Connectors → Add custom connector.
Enter a name (for example micropage) and the server URL above.
Select Add, then Connect, then sign in and approve.

Leave Advanced settings empty. If automatic registration ever fails, you can set OAuth Client ID there to 14aaf8eb-e95a-4218-860d-c1755cdcee7b and leave the secret empty.

Claude Code

claude mcp add --transport http micropage https://mcp.micropage.sh/mcp

Then run /mcp in Claude Code, select micropage, and choose to authenticate. A browser window opens for sign-in and consent.

To share the setup with a project, use .mcp.json:

{
  "mcpServers": {
    "micropage": {
      "type": "http",
      "url": "https://mcp.micropage.sh/mcp"
    }
  }
}

If automatic registration fails in your environment, use the pre-registered client instead: add --client-id f1176948-266f-42af-9fe6-b285e023421c --callback-port 33418 (or "oauth": {"clientId": "f1176948-266f-42af-9fe6-b285e023421c", "callbackPort": 33418} in .mcp.json). That client only accepts the exact redirect http://localhost:33418/callback, so the port must be 33418.

Other AI apps

Any MCP client that supports OAuth for remote servers can connect with just the server URL. Add it the way that app adds a remote MCP server, then sign in and approve.

The consent screen recognises these apps by where they send you back, and names them:

ChatGPT
Cursor
VS Code (GitHub Copilot)
Perplexity

Apps that sign in through a port on your own computer, such as Gemini CLI, Zed, Goose, the Cursor desktop app and the MCP Inspector, are shown as an app on your own computer.

Other apps still work, but the consent screen warns that Micropage doesn't recognise them. Approve only if you started the connection from that app.

Headless and CI: deploy token

For an agent with no browser, skip OAuth and send a deploy token (Pro+) as two headers:

Authorization: Bearer <deploy token>
X-Micropage-Project: <project uuid>

In Claude Code:

claude mcp add --transport http micropage \
  https://mcp.micropage.sh/mcp \
  --header "Authorization: Bearer $MICROPAGE_DEPLOY_TOKEN" \
  --header "X-Micropage-Project: $MICROPAGE_PROJECT_UUID"

The server is then pinned to that project and offers the same reduced tool set as the local deploy-token mode. All three permissions are off and cannot be turned on with a deploy token.

Check that it works

Ask "Which micropage account are you connected to?". whoami reports your email, your plan, and auth_mode: "oauth" (or "deploy_token").

Permissions

The local server's three environment switches become switches on each connection. Every switch is off when you first connect:

Switch	Off (default)	On
Let it send newsletter emails	`publish_post` refuses any post that would email a list. Web-only posts still publish.	`publish_post` can email the list.
Let it delete projects	`delete_project` is not offered.	`delete_project` is offered.
Let it read form submissions (may include personal data)	`list_submissions` is not offered. `list_forms` still gives counts.	The assistant can read what visitors typed into your forms.

Set them on the consent screen, or later in Account → Connected AI apps (app.micropage.sh/account/connected-apps). Each connected app has its own switches, so turning one on for Claude Code does not turn it on for claude.ai.

A change takes effect within about a minute. If a tool you just allowed is still missing, start a new conversation or reconnect so the app fetches the tool list again.

The AI app cannot change these switches itself, even though it acts as your account. Only you can, signed in to Micropage in your browser.

Disconnect

In Account → Connected AI apps, select Disconnect next to the app. The server stops accepting the app's access within about a minute, and the app cannot renew it. To use the app again, connect it again from the app.

Removing the connector inside the AI app does not revoke access on the Micropage side. Disconnect it in Micropage too.

Differences from the local server

No local files. upload_asset takes source.url or source.base64; source.path is not offered.
Uploads are capped at 4 MB (10 MB locally). Prefer source.url for an image that is already online: base64 passes through the model's context and is slower and more costly.
URL uploads only reach public hosts. Addresses on private or internal networks, and Micropage's own infrastructure, are refused.
Rate limit. About 120 calls per minute per user (or per deploy token). Beyond that, calls are answered with HTTP 429 until the minute is up.
Permissions are per connection, set in your account, not in a config file. See Permissions.

Troubleshooting

Symptom	Cause and fix
HTTP 401, or the app says the connector needs to be reconnected	The authorization expired, was revoked, or was disconnected. Reconnect: in claude.ai, Settings → Connectors → micropage → Connect; in Claude Code, `/mcp`, select `micropage`, and authenticate again.
Sign-in fails with a redirect or callback error in Claude Code	If you used the pre-registered client ID, the callback port must be `33418`. Otherwise remove and re-add the server without `--client-id` so it registers itself.
Sign-in fails in claude.ai	Remove the connector and add it again with only the URL. If it still fails, set OAuth Client ID under Advanced settings to `14aaf8eb-e95a-4218-860d-c1755cdcee7b`.
`PLAN_REQUIRED`	The account is not on Pro or Pro+ (Pro+ for a deploy token). Upgrade, then retry.
A tool says emailing, deleting, or reading submissions is turned off, or the tool is missing	The matching permission is off. Turn it on in Connected AI apps, wait a minute, and start a new conversation.
HTTP 429	The rate limit was hit. Wait a minute.
A deploy-token call is rejected	Check that `X-Micropage-Project` is the uuid of the project the token belongs to, and that the token has not expired or been revoked.

Security

Read Safety for what revoking does and does not stop, and which tools not to auto-approve.

How signing in works​

Add it to your app​

claude.ai, Claude Desktop, and Claude mobile​

Claude Code​

Other AI apps​

Headless and CI: deploy token​

Check that it works​

Permissions​

Disconnect​

Differences from the local server​

Troubleshooting​

Security​