deed.page

This connector bridges deed.page's official remote MCP server (https://deed.page/mcp). deed.page is static web hosting built for AI agents: a page or a small site the AI writes (a report, a dashboard, a prototype, a document to share) goes live at https://<slug>.deed.page/ with one tool call. deed.page's own server provides the tools: publish and update sites, check a slug, list versions and restore one, large uploads by manifest, custom domains, a site password, analytics and webhooks. AnythingMCP puts them behind your MCP endpoint with OAuth for Claude and ChatGPT, per-tool roles and the audit log, next to your other systems.

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.

Setup (about 2 minutes):

1. Get an owner token. deed.page has no sign-up: the first publish without a token creates one and returns it once as token (it starts with deed_tok_). Publish any page once by following https://deed.page/docs, or with any MCP client connected to https://deed.page/mcp, and copy the token from the response.
2. Paste it as DEED_PAGE_TOKEN and install. 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.

The tools come from the server. At install AnythingMCP asks deed.page for its tools, so you get the current set. Open the connector and click Discover tools to pick up new ones later.

Ask before publishing: the AI should show the user what it is about to put online (the files, or a short summary of them, and the slug) and publish or update only after the user says yes. A ttl_seconds preview link is a good way to let them check it first. Don't run publishes from a schedule or another flow nobody is watching.

Working with it: call deed_page_publish_site with files (for example {"index.html": "<!doctype html>..."}) and an optional slug; it 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 the owner's 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 use deed_page_plan_upload and deed_page_finalize_upload, which skip files deed.page already has.

Errors: a taken slug returns slug_taken and a reserved one slug_reserved, each with a suggestion; a racing or stale update returns version_conflict; going over the plan's limits returns a quota error. When a plan limit error appears, tell the user which limit was reached; deed_page_whoami shows the current plan and its limits, and deed.page's paid plans and their limits are listed at https://deed.page/pricing.

Safety: deleting a site, rotating or revoking the token, managing Pro agent seats (creating a seat returns a new token), removing a custom domain and deleting a webhook install switched off. The billing and promotion tools (deed_page_get_upgrade_link, deed_page_claim_share_credit, deed_page_set_badge) install switched off too; an administrator can turn them on. Rotating or revoking through the connector would also break the token stored here, so do that at deed.page and paste the new token instead. Turn the others on per tool if the AI should be allowed to remove things.