Docs

Set up aft for your agent

Paste one line into your agent. It reads this guide and writes the MCP config for whichever client it's running in — no account, no key.

Paste this into your agent: Set up aft for me: https://aft.page/setup

Configure it by hand Read setup.md Quick start

What your agent does

aft.page is one remote MCP server at https://mcp.aft.page/mcp. Given the line above, a coding agent should:

  • detect which client it's running in — Claude Code, Cursor, Windsurf, Codex, or another MCP client;
  • add one server named aft-page at that URL (or install the plugin, where the client has one);
  • tell you which file it touched and how to undo it;
  • ask you to restart so the tools load.

There is no sign-in in any of that. Deploy tools work anonymously: the first URL is public for 60 minutes, and the claim link is what keeps it.

Reading the full instructions yourself: /setup.md.

Hosted assistants

ChatGPT, Claude.ai, and Grok can't edit files, so they can't configure themselves. Add aft.page as a custom connector — the URL is the whole setup: 

https://mcp.aft.page/mcp
  • Claude — Settings → Connectors → Add custom connector.
  • ChatGPT — turn on Developer mode (Settings → Security and login), then add it as a custom server.
  • Grok — grok.com/connectors → New connector → Custom.

Start a new conversation afterwards so the tools load.

By hand

Every client takes the same server URL. The entry a MCP host reads: 

{
  "mcpServers": {
    "aft-page": {
      "type": "http",
      "url": "https://mcp.aft.page/mcp"
    }
  }
}

Windsurf uses serverUrl instead of url. Claude Code can write its own config: 

claude mcp add --transport http --scope user aft-page https://mcp.aft.page/mcp

Per-client detail, including the plugin and connector paths: Connect your agent.

Restart & verify

New MCP servers usually need a fresh session. Restart the client (or start a new task), then ask: 

Deploy this to aft.page

You should get a live https://{slug}.aft.page URL back. If the tools never appear, the config went to a path that client doesn't read — check the file, then see the client list.

No MCP at all

The CLI publishes without any MCP config, which is the fallback when a client can't load a remote server: 

curl -fsSL https://aft.page/install | sh
aft deploy

No login to ship. aft deploy --json returns one result object for scripts and agents. CLI guide.