Connect Claude to Tempx

Give Claude a disposable inbox of its own. Tempx speaks MCP over HTTPS with proper browser pairing: when Claude connects, your browser opens tempx.uk, you sign in with Google or GitHub, pick one inbox and approve. No token is ever pasted into a chat, a shell or a config file.

Option 1 — one command (Claude Code)

claude mcp add --transport http tempx https://tempx.uk/mcp

Run it once. On first use Claude Code opens your browser at tempx.uk/oauth/authorize; sign in, choose the inbox, the permissions (read / search / wait / send) and an expiry, and approve. The credential is stored by Claude Code itself.

Option 2 — ChatGPT and Z.ai

ChatGPT: Settings → Apps & connectors → enable Developer mode → Add a custom connector → paste https://tempx.uk/mcp. ChatGPT runs the same browser sign-in (requires a plan with connectors). Z.ai: in chat.z.ai add a custom MCP server (Streamable HTTP) with the URL https://tempx.uk/mcp and an Authorization: Bearer <token> header from your account page.

Option 3 — manual token (any MCP client)

Create a connection on your account page and copy the ready-made client snippets (Claude Code with a header, Claude Desktop via the mcp-remote bridge, or plain JSON). Fine for clients without OAuth — but the token is a secret you then have to handle yourself.

What your agent can do with it

• Receive verification codes. wait_for_email long-polls server-side and returns the moment a matching message arrives.
• Read and search. List messages, open one by id, search by sender or subject — all inside the chat.
• Test email flows end to end. With the optional send permission, send_email composes mail that is captured in the same inbox for testing (sandbox SMTP / Mailtrap style) — templates, notifications, signup flows — and create_smtp_credential mints SMTP credentials that capture the same way. Nothing is ever delivered to a real recipient.

What it can never do: deliver real mail to anyone, delete anything, or read any inbox other than the one you approved. Sending is capture-only by construction, everything is rate-limited per token, and every pairing is revocable in one click on your account page.

Pair your agent with an inbox

Inbox, browser pairing, working agent — about three minutes.

Create an inbox