Cantrip is the simple website builder at cantrip.io. There are two ways to manage your site by talking to an AI, depending on what your assistant supports:
For Claude (any plan — Free included), Cursor, Claude Code, and ChatGPT Developer Mode (Pro, Business, or Enterprise).
MCP endpoint URL (paste this into your AI client):
Authentication: OAuth. Authorize in your AI client and sign in to Cantrip when prompted. No API key to copy or paste.
Custom connectors need Developer Mode, which requires ChatGPT Pro, Business, or Enterprise — Free and Plus can't add one. Settings → Connectors → enable Developer Mode → Create / Add custom connector → paste the endpoint URL → choose OAuth → Authorize and sign in to Cantrip.
Works on every plan, including Free (capped at one custom connector there — Cantrip counts as it). Settings → Connectors → Add custom connector → paste the endpoint URL → Add → Authorize.
Add the snippet below to ~/.cursor/mcp.json (or the project .cursor/mcp.json), reload, then approve the OAuth prompt on first use.
Run the command below, then use /mcp inside Claude Code to complete the OAuth login.
For ChatGPT Free/Plus, Gemini, and any other tool that reads an OpenAPI schema instead of speaking MCP directly.
A curated, safe-write subset of the Cantrip API (list/get websites, pages, and sections; edit page and section content; switch themes; update appearance; generate AI content) described as an OpenAPI 3.1 schema, OAuth-protected by the same authorization server as the MCP endpoint. For AI platforms and clients that cannot add a live MCP connector.
Publishing, deleting, billing, domains, and team management stay MCP/portal-only for now.
Free and Plus plans can't add a custom connector, but they can use a Custom GPT someone else built and published — including one built on this schema. If you (or a developer you work with) have a paid ChatGPT account:
php artisan passport:client).Point any OpenAPI-aware tool (Gemini function calling/Extensions, LangChain, a custom agent) at the schema URL above. It's a standard OpenAPI 3.1 document with an OAuth2 authorization-code security scheme — no Cantrip-specific client library needed.
Once connected, ask your assistant:
OAuth is the only way in to the hosted MCP endpoint — it is behind the OAuth guard, so a Cantrip API token in an Authorization header is rejected before any tool runs. For headless automation, use the V1 REST API at /api/v1 instead: get a token with POST /api/v1/auth/token and send it as Authorization: Bearer <token>. The REST API covers the same capabilities as the MCP tools.
Machine-readable version of this page: /api/v1/mcp/connection
npx mcp-server-cantrip — it's guessing. Cantrip.io is hosted; always use the endpoint above.