Connect deed.page to ChatGPT via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → deed.page, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

deed.page + ChatGPT

Publish HTML pages and small static sites that your AI writes to a permanent public URL, update them in place, roll back versions and attach custom domains from Claude, ChatGPT or Copilot through deed.page's official MCP server.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

DEED_PAGE_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a deed.page owner token. deed.page has no sign-up: the first publish without a token creates one and returns it once.

1. Publish any page once without a token, following deed.page/docs or with any MCP client connected to https://deed.page/mcp. Copy the token from the response; it starts with deed_tok_.
2. Paste it into DEED_PAGE_TOKEN, without the word Bearer. AnythingMCP sends it as a Bearer token on every call, so every site the AI publishes through this connector belongs to that owner and can be updated, listed and deleted later. Leave the tools' own token argument empty.
3. Keep the token safe: whoever has it controls every site of that owner. A lost token cannot be recovered unless a recovery email was attached.
4. Install the connector and run deed_page_whoami: it shows your plan, its limits and how many sites the token owns.

The tools come from deed.page: the connector bridges deed.page's official remote MCP server (https://deed.page/mcp). At install AnythingMCP asks deed.page for its tools, so you get the current set. To pick up new ones later, open the connector and click Discover tools.

What it does: deed.page is static web hosting built for AI agents. A page or small site the AI writes (a report, a dashboard, a prototype, a document to share) goes live at https://<slug>.deed.page/ with one call to deed_page_publish_site, which returns the live url and a version. Publish to the same slug again, or use deed_page_update_site, to replace a page in place. deed_page_get_site checks whether a slug is live, deed_page_list_sites lists your sites, and deed_page_list_versions with deed_page_restore_version rolls a site back. Set ttl_seconds for a preview link that expires on its own. For many or large files the AI uses deed_page_plan_upload and deed_page_finalize_upload, which skip files deed.page already has. The connector can also attach custom domains, set a site password, show cookieless analytics and register webhooks.

Everything published is public: anyone with the URL can open a site unless it has a password, so never let the AI publish secrets, credentials or private customer data. Sites stay out of the public gallery unless listed is true. A password (deed_page_set_site_access) needs the Hobby or Pro plan.

Ask before publishing: the AI should show you what it is about to put online (the files or a short summary of them, and the slug) and publish or update only after you say yes. A ttl_seconds preview link lets you check it first. Don't run publishes from a schedule or a flow nobody is watching. Besides publishing and updating, deed_page_restore_version, deed_page_add_domain, deed_page_set_site_access, deed_page_set_listing and deed_page_create_webhook also change things on deed.page.

Switched off at install: deed_page_delete_site, deed_page_rotate_token, deed_page_revoke_token, deed_page_agent_seats (Pro agent seats; creating one returns a new token), deed_page_remove_domain and deed_page_delete_webhook, plus the billing and promotion tools deed_page_get_upgrade_link, deed_page_claim_share_credit and deed_page_set_badge. An administrator can turn them on per tool. Rotate or revoke the token at deed.page rather than through the connector, because doing it here would also break the token stored in DEED_PAGE_TOKEN; then paste the new token.

Limits: they depend on your plan (free, hobby or pro). Free keeps 10 versions per site, Hobby 50, Pro unlimited. Custom hostnames: Free 1, Hobby 3, Pro 20. Webhooks: Free 1, Hobby 5, Pro 20. Going over a limit returns a quota error; deed_page_whoami shows your current limits, and deed.page/pricing lists the paid plans.

Common errors: a taken slug returns slug_taken and a reserved one slug_reserved, each with a suggested alternative. A racing or stale update returns version_conflict and writes nothing. A revoked token returns 401 token_revoked.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in ChatGPT

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

ChatGPT adds MCP servers as plugins on its Plugins page, on the web and on paid plans. Developer mode is no longer needed. In a Business workspace only admins and owners can add one; in Enterprise and Edu an admin can grant the Create plugins with MCPs permission.

1. Go to chatgpt.com/plugins, click Add, then Add custom MCP server.
2. Enter a name, e.g. Name: deed.page.
3. Under Connection, enter the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID and keep Authentication on OAuth.
4. Select I understand and want to continue, then Create as a plugin. When ChatGPT asks, sign in to AnythingMCP and allow access.
5. Install the new plugin from your personal plugins, then type @ in a chat and pick it.

Available tools

FAQ

Does the free ChatGPT plan work with custom MCP servers? OpenAI documents custom MCP servers for paid plans only; the Free plan is not on its list.

Next steps

• Connector landing page
• Connect to Claude