Claude Code

Add the server URL, then authenticate from the in-session MCP panel. The browser opens at the Authenticate step, not at add time. API keys still work as a fallback.

1. 1

   Add the server

   Run once. This only saves the URL — no browser opens yet.

   Shell

   claude mcp add --transport http unitpost https://mcp.unitpost.com/mcp

   Use -s user to install for every project. claude mcp list now shows unitpost as ! Needs authentication — that is expected.

2. 2

   Authenticate with OAuth (recommended)

   Start a Claude Code session, run /mcp, select unitpost, and choose Authenticate. Your browser opens to Unitpost — pick a workspace, approve the scopes, and you're connected. No key to copy. Your client opens Unitpost in the browser — pick a workspace, approve the scopes, and you're connected. Tokens refresh automatically.

   If the browser doesn't open automatically, copy the URL shown in the terminal and open it manually. Tokens refresh automatically; if auth ever lapses, repeat this step.

3. 3

   Verify

   Run claude mcp list (or /mcp in a session). unitpost should show connected with its tools listed — no ! Needs authentication flag.

   Don't see it? Fully quit and reopen the client — closing the window is often not enough — then check again.

4. 4

   Send a test

   Ask Claude to send an email from a verified domain and confirm it in Unitpost Activity.