Connect an AI agent to your link-in-bio page over MCP.
Snapto hosts an MCP server, so an agent can read and update your page directly. No local process to run, no wrapper to install.There are two ways to connect: a key-in-URL token that works with any MCP client, and OAuth for Claude. Both need an active paid plan, Lite or above. The 7 day free trial counts.
It speaks Streamable HTTP with JSON-RPC 2.0. The fastest way to connect: in the dashboard, go to Settings then Agents, pick your client, and click Connect. The dialog shows the full URL and the setup command for that client, once. To mint a token with custom abilities instead, use Settings then API.
The token is embedded in the URL, because most MCP clients cannot send custom headers. Treat the entire URL as a secret. Revoke the token to cut off access.
Install the official plugin. It bundles the connection plus a skill that makes Claude a careful page manager, and prompts for your token on install:
claude plugin marketplace add snaptolink/snapto-claude-pluginclaude plugin install snapto-profile-manager@snapto-plugins
Or add the server directly:
claude mcp add --transport http snapto https://snapto.link/mcp/YOUR_TOKEN
Connect over OAuth so there is no token to paste. Go to Settings then Connectors, click Add custom connector, and enter https://snapto.link/api/mcp. See Connect from Claude with OAuth below.
Go to Settings then MCP then Add server. Choose the HTTP transport and paste the same URL. The Connect dialog on the Agents settings page also gives you a one-click install link.
Add a custom connector pointing at the URL. This needs a ChatGPT plan that supports connectors.
Claude, on the web and desktop, can connect over OAuth instead of a key-in-URL token, so there is no secret to paste or rotate. In Claude, go to Settings then Connectors, click Add custom connector, and enter the OAuth endpoint:
https://snapto.link/api/mcp
Claude registers itself and sends you to a Snapto consent screen. Approve it and the connection is live. Claude groups the tools into read-only and write, so you can decide what it may do on its own.Manage these connections from Settings then Connected apps in your Snapto dashboard. Revoking one cuts off the agent immediately.
The MCP server enforces the same token abilities as the REST API. A read-only token can list and read, but any attempt to write comes back as a tool error. Give an agent a read-only token when you only want reporting.
An agent acts with the full power of the token you hand it. Deleting an element is irreversible. Grant elements:write and profiles:write only when you actually want the agent changing your page, and review what it changed.
