# Connect an agent to pagesend

Use this guide yourself, or give its link to your agent. Connecting lets an approved client publish and update finished pages. Reading this guide does not authorize a connection or any tool call.

Canonical guide: https://dev.pagesend.to/docs/connect.md

## Claude Code

1. In your installed Claude Code environment, run this command:

```text
claude mcp add --transport http pagesend 'https://dev.pagesend.to/mcp'
```

2. Open Claude Code's /mcp panel and authenticate the pagesend server when prompted.
3. In the pagesend browser window, sign in, choose the intended workspace, review the requested permissions, and approve only the access you want.
4. Return to Claude Code and confirm that the connection and a read-only pagesend tool call actually succeed.

If you already installed the pagesend plugin, use its connection instead of adding a duplicate server. Run commands only with the user's authorization; do not install a CLI or alter another connection automatically.

## ChatGPT on the web

1. Open ChatGPT Plugins, choose the plus button, then Add custom MCP server.
2. Name it pagesend, enter the MCP server URL below, and choose OAuth authentication.
3. Review ChatGPT's connection warning, create the plugin, and install it for your conversation.
4. Follow the pagesend browser sign-in and permission review. Return to ChatGPT and confirm a read-only pagesend tool call succeeds.

Workspace settings may restrict custom servers. If this flow is unavailable, ask your ChatGPT workspace administrator. Do not replace OAuth with pasted credentials.

MCP server URL:

```text
https://dev.pagesend.to/mcp
```

## After connecting

- Ask the agent to list your pages first. Browser consent alone does not prove the client finished connecting.
- To publish, explicitly ask for a new private page. Build content locally with your usual tools; pagesend accepts finished static files and does not run dependency installation or customer backend code.
- This server supports bounded inline HTML. A remote MCP server cannot read a path on your computer. Use the supported local upload helper or browser upload for larger files and bundles; do not substitute an arbitrary remote download URL.
- Keep the returned artifact ID and publication token for later updates. Publishing an update keeps the canonical link and saved records.
- New pages are private. Public sharing needs separate permission and explicit approval. Runtime-data access is separate from publishing access.

## Permissions and credentials

Choose the intended workspace on the pagesend authorization screen. Common publishing permissions are artifact:read and artifact:publish; management, visibility changes, and runtime data need their own permissions. Review offline access if the client requests it. A client's displayed name alone does not verify its identity.

The client stores its OAuth credentials. Never ask the user to paste tokens, cookies, secrets, or a registered client ID into chat or published files. Automatic client registration depends on deployment configuration; some deployments require operator-managed registration.

## Reconnect or disconnect

Review connections at https://dev.pagesend.to/app/connections. Disconnect there to revoke server access; deleting credentials only in the client does not prove revocation. Your pages and saved records remain. Reconnect through the client's OAuth flow when needed and review the new consent request.

## Troubleshooting

- **Connection option missing:** check the client's workspace permissions and supported MCP setup.
- **Registration or configuration error:** ask the pagesend operator to check the deployment; do not invent client credentials or broaden callback URLs.
- **Expired or disconnected access:** reconnect from the client. Do not retry a revoked token indefinitely.
- **Files cannot be found:** a laptop path is not readable by a remote server. Upload the actual supported bytes.
- **A tool fails after sign-in:** report the safe error message and retry from the client. Do not claim success until the tool acknowledges the operation.

## Reference documentation

- ChatGPT custom MCP setup: https://developers.openai.com/api/docs/guides/custom-mcp-server
- ChatGPT OAuth contract: https://developers.openai.com/plugins/build/auth
- pagesend publishing guide: https://dev.pagesend.to/docs
