Connect your agent · Claude Code

Give Claude Code a work inbox, not your mailbox.

Claude Code can check messages and prepare replies through a dedicated Connect mailbox. Add the remote MCP server from your terminal, sign in once, and keep the rest of your email account private from this connection.

For software developers who work in a terminal and want Claude Code to handle project-related email without opening their personal inbox.

Connect your agent See setup steps ↓
Set it up

Add Stacksona Connect from the terminal

The terminal command registers a remote server; browser sign-in supplies its authority.

  1. Create the mailbox

    Create a mailbox in Stacksona Connect for the project or agent. Set the mailbox’s contact and approval rules before allowing customer-facing sends.

  2. Register the remote server

    Run claude mcp add --transport http stacksona-connect https://connect.stacksona.com/mcp in your terminal. Replace the endpoint if your administrator gave you a different Connect host.

  3. Authenticate in Claude Code

    Run /mcp, select Stacksona Connect, and follow the browser sign-in. Review the requested mailbox permissions on the Connect consent screen before approving.

  4. Confirm the connection

    Use claude mcp list or claude mcp get stacksona-connect to inspect setup. Ask Claude Code to call connect_check_connection and report the granted permissions without reading messages.

Register the server for your user account

Run this command in the terminal where you use Claude Code.

claude mcp add --transport http --scope user stacksona-connect https://connect.stacksona.com/mcp
Provider instructionsClaude Code MCP documentation ↗
A practical workflow for developers

Use a project mailbox for project communication.

Route bug reports, release questions, or test account messages to the address assigned to the coding agent. Claude Code can access that mailbox through MCP while your personal inbox and its credentials remain outside the connection.

User-scoped setup

Your terminal config does not share your authorization.

Claude Code stores user-level MCP settings in your local environment by default. A project may describe the server to collaborators, but every person should complete their own sign-in rather than share a mailbox token.

Keep terminal authorization with the developer who signed in.

Claude Code stores its server registration in the local environment. Keep OAuth with the developer who signed in, check the active account in /mcp, and avoid copying local credentials into a repository when teammates need their own mailbox access.

The CLI configuration identifies Connect; the browser consent grants mailbox access.

Compare the available integration paths
Questions people ask about Claude Code

Claude Code terminal setup

What command adds Connect to Claude Code?

Run `claude mcp add --transport http stacksona-connect https://connect.stacksona.com/mcp`, then open `/mcp` and authenticate.

Can Claude Code use the same connector as Claude?

Claude Code can inherit eligible connectors from Claude’s account setup. Confirm which Connect mailbox is active so you do not add a duplicate or authorize a different address by mistake.

Does the MCP config include my email password?

No. The config names the remote Connect server. Browser OAuth grants selected scopes to the separate mailbox; it does not store your personal email-provider password in the project.

Related setup guides

The CLI entry belongs to your local environment unless you deliberately choose another scope.

Stacksona Connect

Connect your terminal agent

Create the mailbox in Connect, then add and authorize the server from Claude Code.

Create an agent mailbox