Setup · 2 minutes
Connect once. After that your agent turns any deliverable into a polished, gated, tracked link — so it can hand finished work to your client without re-asking or manual uploads.
Set up sendhey: its MCP server is https://sendhey.app/mcp — add it as a Streamable HTTP connector and sign in with OAuth (there is no API key to paste). For client-specific setup steps you can read https://sendhey.app/skills/connect-sendhey.md as reference. Optional shortcut on Codex or Claude Code: run `npx -y @sendhey.app/setup@latest`. Once connected, use https://sendhey.app/skills/publish-with-sendhey.md to publish my next artifact.The AI reads the current setup guide first. It uses the CLI only when its terminal can actually persist this client's connector; ChatGPT, Cowork, and other isolated surfaces get their account-level route instead.
npx -y @sendhey.app/setup@latesthttps://sendhey.app/mcpDon't open this URL in a browser — it's a protocol endpoint for AI clients, not a web page.
One instruction for your agent
That's the whole mental model. When your agent finishes something for a client, have it publish through sendhey instead of pasting raw files — the recipient gets a dependable link, and you keep control and see when it's opened.
Use sendhey to deliver this to my client as a gated, tracked link, then give me the URL.Pick your client
npx -y @sendhey.app/setup@latestclaude mcp add --transport http --scope user sendhey https://sendhey.app/mcpOpen /mcp inside Claude Code, select sendhey, and complete browser OAuth. The user scope keeps it available across projects. Verify with claude mcp get sendhey; there is no claude mcp login command.
Cowork can lead you through setup, but a shell command inside its isolated task does not reliably change your Claude account connectors. Open Customize → Connectors → + → Add custom connector, paste the endpoint, and complete OAuth. Then enable sendhey for the task from + → Connectors.
On Team or Enterprise, an Owner first adds it under Organization settings → Connectors → Add → Custom → Web; members then connect individually.
Open Customize → Connectors → + → Add custom connector, paste the MCP endpoint above, and finish OAuth. Enable sendhey for a conversation from + → Connectors. Free accounts can add one custom connector; Pro and Max can add their own. Team and Enterprise require an Owner to add it for the organization first.
ChatGPT can guide the setup, but its code-execution sandbox is not the installation target. The sandbox may run npx, yet it cannot persist an app in your ChatGPT account. On ChatGPT web, full read and write MCP tools are currently available to Pro, Plus, Business, Enterprise, and Education through Developer mode.
Open Settings → Security and login and enable Developer mode. Then open Settings → Plugins (or chatgpt.com/plugins), select the plus button, and create a developer-mode app. Name it sendhey, paste the endpoint, choose OAuth, and complete sign-in. The app appears under Drafts; refresh its tools if needed and confirm publish_page is present.
Start a new chat, choose Developer mode from the Plus menu, and select sendhey. Write actions use ChatGPT's normal confirmation by default. Free and Go are not currently listed as eligible for Developer mode; use Codex, Claude/Cowork, or an eligible ChatGPT account instead. Until the reviewed sendhey plugin is published, it cannot be installed by name from the directory.
npx -y @sendhey.app/setup@latestcodex mcp add sendhey --url https://sendhey.app/mcpCurrent Codex normally discovers OAuth during add. If it does not, run codex mcp login sendhey. Verify with codex mcp get sendhey --json, then start a fresh task if the tools are not present in this one.
An admin adds it once for everyone: Integrations → Add Integration → Connect remote MCP → paste the MCP endpoint → choose OAuth → Test connection → select the sendhey tools → Save.
Paste the endpoint wherever your client accepts a remote Streamable HTTP MCP server, complete OAuth, and verify that tools/list includes publish_page. Client-specific settings and reload behavior still apply.
Set up sendhey: its MCP server is https://sendhey.app/mcp — add it as a Streamable HTTP connector and sign in with OAuth (there is no API key to paste). For client-specific setup steps you can read https://sendhey.app/skills/connect-sendhey.md as reference. Optional shortcut on Codex or Claude Code: run `npx -y @sendhey.app/setup@latest`. Once connected, use https://sendhey.app/skills/publish-with-sendhey.md to publish my next artifact.This surface cannot publish through sendhey directly. It also cannot become connected merely by fetching instructions. Continue the same task in Codex or Claude Cowork, or follow the matching manual connector path above.
What "connected" looks like
Wherever you paste the endpoint, a sendhey sign-in opens in your browser. Approve it and your client shows sendhey connected with its publishing tools available. Start a fresh chat or task so the connection loads — you only do this once.
Open the client's MCP or app inventory and confirm sendhey is connected, then list its tools and check that publish_page is present. Do not create a throwaway link just to test setup: a publish is a real external write and starts the trial.
Once verified, publish your next real artifact under the client's normal confirmation and manage or revoke the resulting link from your dashboard.
The setup router lives at https://sendhey.app/skills/connect-sendhey.md. Connected agents get the publishing model from https://sendhey.app/skills/publish-with-sendhey.md.
For servers, CI, or agents that can't complete a browser sign-in, use machine credentials (OAuth client_credentials) or a static API key as a Bearer token against the same endpoint. Create and revoke them under Settings → Developer access. Keep them out of public docs and prompts — treat them like passwords.
About · Privacy · Legal notice · Report illegal content · Terms · DSA