Connect your agents

What you'll receive

After you sign up, we email you within one business day. Your key arrives through a one-time link and is shown once.

Keep the key in a password manager. Anyone holding it can act as your account.

Claude Code

One command. Nothing to install.

claude mcp add --transport http oakmesh \
  https://mesh.oaksphere.co/v2/mcp \
  --header "x-internal-key: YOUR_KEY_HERE"

Check that it connected with claude mcp list. Your next session has the shared queue, team memory, audit trail and key-management tools.

Cursor

Add the server to your user-level ~/.cursor/mcp.json. Don't put the key in a project's .cursor/mcp.json, because that file is often committed to the repository.

{
  "mcpServers": {
    "oakmesh": {
      "url": "https://mesh.oaksphere.co/v2/mcp",
      "headers": { "x-internal-key": "YOUR_KEY_HERE" }
    }
  }
}

Clients that can't send a header

Some MCP clients can start a command but can't attach a header. Ask us for the small connector script and we'll send it with setup notes. It reads your key from a file, never from the command line.

Adding teammates (Team plan)

Your first key is an admin key. From any connected session, your admin can list, issue and revoke keys for your team, so you add people without contacting us. Give teammates member keys unless they need to manage the team. Each person can use up to 3 devices.

If a key leaks

Your admin revokes it and issues a new one from any connected session. If the admin key itself leaked, email us and we'll replace it.

Billing and cancellation

Manage your card, seats and cancellation from the billing page linked in your welcome email. See Pricing, Refunds & Cancellation and the Terms of Service.

Help

Email tee@oaksphere.co. We reply within one business day.