Setup

Connecting a client to the Ema MCP server takes about a minute: add the server, authenticate once through your browser, and verify it's connected. This page covers the Claude Desktop app, Claude Code, Codex, and any other MCP client.

Before you start

• An Ema account with builder access (see Access).
• The MCP client you want to connect.
• The environment you want to use. Pick the endpoint for the environment where your AI Employees live:

The examples below use the Dev endpoint. Substitute the Staging, Prod, or Demo URL — and a matching connection name — to connect to those environments instead.

Claude Desktop app

Ema is available as a built-in connector in the Claude Desktop app, so there's no URL to paste.

1. Select the + button → Connectors → Manage Connectors.
2. Search for Ema in the search box, then select the connector for your environment: Ema Dev, Ema Staging, Ema Prod, or Ema Demo.
3. Select Connect, then authenticate (see Authentication).

Once connected, you can use Ema in all Desktop app modes: Chat, Cowork, and Code.

Claude Code

1. In a terminal, add the server for your environment:

   # Dev
   claude mcp add --transport http ema-mcp-dev --scope user https://dev.ema.ai/api/v1/agent-harness/mcp
   
   # Staging
   claude mcp add --transport http ema-mcp-staging --scope user https://staging.ema.ai/api/v1/agent-harness/mcp
   
   # Prod
   claude mcp add --transport http ema-mcp-prod --scope user https://app.ema.ai/api/v1/agent-harness/mcp
   
   # Demo
   claude mcp add --transport http ema-mcp-demo --scope user https://demo.ema.ai/api/v1/agent-harness/mcp

2. Open Claude Code and run /mcp. Select Authenticate for the server you just added, then complete sign-in in the browser (see Authentication).
3. Run /mcp again to confirm — it should show the server as authenticated.

The MCP is now ready to use from Claude Code.

Codex

1. In a terminal, add the server for your environment:

   # Dev
   codex mcp add ema-mcp-dev --url https://dev.ema.ai/api/v1/agent-harness/mcp
   
   # Staging
   codex mcp add ema-mcp-staging --url https://staging.ema.ai/api/v1/agent-harness/mcp
   
   # Prod
   codex mcp add ema-mcp-prod --url https://app.ema.ai/api/v1/agent-harness/mcp
   
   # Demo
   codex mcp add ema-mcp-demo --url https://demo.ema.ai/api/v1/agent-harness/mcp

2. Log in and authenticate to the server you added (use the same name — ema-mcp-dev, ema-mcp-staging, ema-mcp-prod, or ema-mcp-demo) by running:

   codex mcp login ema-mcp-dev

3. Run codex, then type /mcp to confirm — it should show that you're authenticated and list the Ema tools.

The MCP is now ready to use from Codex.

Other MCP clients

Any client that supports streamable HTTP transport with OAuth can connect. Add a new MCP server pointing at the environment endpoint above, with the transport set to HTTP (sometimes labelled "streamable HTTP"), then complete the OAuth sign-in your client prompts for. Consult your client's documentation for where MCP servers are configured.

Authentication

The Ema MCP server uses OAuth: the first time you connect, your client opens a browser window where you sign in to Ema. There are no tokens or API keys to copy.

• Sign in as yourself. Use your normal Ema credentials. The connection acts as you — it sees and changes only what your role and tenant allow.
• One environment per connection. Each connection is tied to the environment you added and authenticates independently.
• You stay signed in. The connection refreshes automatically in the background, so you don't re-authenticate each time. You're only prompted to sign in again after an extended period or if your access is revoked.

What's next

• Capabilities — what you can do once connected.
• Troubleshooting and Limits — if a connection or sign-in doesn't work.