--- name: connect-sendhey description: Set up the Sendhey remote MCP server in the current AI client. Detect the surface, use its native persistent setup when available, otherwise give the exact account or admin UI route, and verify tools before reporting success. --- # Connect Sendhey > Canonical version: https://sendhey.app/skills/connect-sendhey.md > Client facts last verified: 2026-07-13 Connect the Streamable HTTP MCP server at `https://sendhey.app/mcp`. Sendhey uses OAuth; never ask the user to paste an API key into chat when browser sign-in is available. ## Fast path Run this only if the terminal is on the same host as Codex or Claude Code and can persist that client's MCP configuration: ```bash npx -y @sendhey.app/setup@latest ``` The installer detects Codex or Claude Code, uses that client's native MCP command, and prints the remaining OAuth and verification steps. It never stores credentials or edits undocumented config files. A shell existing is not enough: do not run the installer in ChatGPT's temporary code-execution container, a Cowork task shell, CI, or another sandbox that cannot change the client's persistent connector inventory. Treat its **configured** result as step 1 below, not as proof that the connection is verified. If no supported local client or persistent authority is available, follow the matching route below. ## The outcome ladder Treat these as different states: 1. **Configured** — the endpoint is saved in the correct persistent client or account settings. 2. **Authenticated** — the user completed Sendhey OAuth. 3. **Connected** — the client can initialize the server. 4. **Verified** — `tools/list` succeeds and includes `publish_page`. Do not report “connected” at step 1. Do not publish a test link just to verify setup: publishing is an external write, creates a live link, and starts the Sendhey trial. Use the client inventory plus `initialize` / `tools/list`; publish the user's next real artifact under the host's normal write confirmation. ## Choose the route for the current surface ### Codex (desktop, CLI, or IDE on the same local host) Prefer the fast-path installer above. Its native fallback is: ```bash codex mcp add sendhey --url https://sendhey.app/mcp ``` Current Codex normally discovers OAuth during add. If authentication did not open, run `codex mcp login sendhey`. Verify with `codex mcp get sendhey --json` or `codex mcp list --json`, then start a fresh task if the tools are not present in this one. If filesystem, shell, or managed policy blocks the change, explain that restriction and use the manual Codex settings route instead of claiming success. ### Claude Code Prefer the fast-path installer above. Its native fallback uses user scope so “connect once” means all projects, not only the current repository: ```bash claude mcp add --transport http --scope user sendhey https://sendhey.app/mcp ``` Then open `/mcp` inside Claude Code, select Sendhey, and complete browser authentication. Verify with `claude mcp get sendhey` and the in-session `/mcp` status. Claude Code does not have a `claude mcp login` command. If managed policy blocks user-scoped servers, name the required admin change. ### Claude Cowork, Claude web or Desktop Do not assume a shell command inside Cowork can change the user's account connector registry. Remote connectors are account-brokered through Anthropic's cloud. - Individual Free, Pro, or Max: **Customize → Connectors → + → Add custom connector**. Paste `https://sendhey.app/mcp`, add it, and complete OAuth. Free accounts are limited to one custom connector. - Team or Enterprise: an Owner first uses **Organization settings → Connectors → Add → Custom → Web** and pastes the endpoint. Each member then opens **Customize → Connectors** and connects. - Enable Sendhey for a conversation or Cowork task from **+ → Connectors**. A reviewed Sendhey plugin can eventually collapse these steps across Claude surfaces. Until its source is publicly installable and clean-client tested, do not tell customers it is available. ### ChatGPT Work or regular ChatGPT chat ChatGPT may offer code execution, but that code runs in a temporary container and does not install an app into the user's ChatGPT account. Do not run the CLI there. Use ChatGPT's current developer-mode app route on the web instead. It supports full read and write MCP tools for **Pro, Plus, Business, Enterprise, and Education** accounts: 1. Open **Settings → Security and login** and enable **Developer mode**. 2. Open **Settings → Plugins** (or https://chatgpt.com/plugins), select the plus button, and create a developer-mode app. Name it **Sendhey**, paste `https://sendhey.app/mcp`, and choose OAuth. 3. Complete Sendhey OAuth. Confirm the draft app is present and refresh its tools if necessary; its inventory must include `publish_page`. 4. Start a new chat, choose **Developer mode** from the Plus menu, select Sendhey, and verify the tool is available before publishing the real artifact. Write actions require the host's normal confirmation by default. Free and Go are not listed as eligible for Developer mode in the current OpenAI documentation. Recommend Codex, Claude/Cowork, or an eligible ChatGPT account instead. A reviewed Sendhey plugin can eventually remove manual URL entry; do not claim that directory listing exists before approval and a clean-client test. ### Any generic MCP client If the client supports remote Streamable HTTP plus OAuth, add `https://sendhey.app/mcp` in its native server settings, complete OAuth, then verify `initialize` and `tools/list`. Do not write arbitrary config files unless the current client documents that exact location and this task has permission to change it. ### No MCP support If the current surface has **No MCP support**, it cannot publish through Sendhey directly. Do not pretend that fetching this guide connected anything. Recommend opening the same task in Codex or Claude Cowork, or give the matching manual connector steps above. The user's real artifact can be published only after a supported client is connected. ## After verification Fetch https://sendhey.app/skills/publish-with-sendhey.md for the publishing mental model. Continue with the user's next real artifact, choose only the access and analytics they asked for, respect the host's write confirmation, and return the live share URL. ## Official client references - Codex MCP: https://developers.openai.com/codex/mcp - ChatGPT Developer mode: https://developers.openai.com/api/docs/guides/developer-mode - ChatGPT app quickstart: https://developers.openai.com/apps-sdk/quickstart#add-your-app-to-chatgpt - Claude custom connectors: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp - Claude plugins: https://support.claude.com/en/articles/13837440-use-plugins-in-claude