Skip to main content
Claude Code can reach Wirebox as a remote HTTP MCP server, or run the stdio bridge locally. Use the CLI to add it, or commit a project-level .mcp.json so every session in the repository has it.

Connect with the CLI

By default the server is added to the current project’s local scope. Add --scope user to make it available in every project, or --scope project to write it into the shared .mcp.json.

Connect with a project config

Commit a .mcp.json in the repository root so the whole team gets the same server:
Anyone using this file should use their own key — or an identity-scoped key if the project should act as a single agent.

Connect over stdio

If you prefer a local process, run the published bridge instead:
The bridge connects back to the hosted endpoint by default, so the tool catalog matches the remote setup.

Verify

List the configured servers, then ask Claude to call wirebox_whoami:
Inside a session, /mcp shows connection status and the tools each server exposes. wirebox_whoami returns the identity the connection acts as — if it is not the agent you expected, update WIREBOX_IDENTITY or switch to an identity-scoped key.

What Claude Code can do

  • List, search, read, send, reply to, and delete email in the agent’s mailbox
  • List and read iMessage conversations, and send iMessages
  • Check which identity the connection acts as
Sends follow the identity’s mail rules and policy, and nothing happens until Claude calls a tool.

Troubleshooting

See Wirebox MCP Server for the full tool catalog, environment variables, and identity locking.