Skip to main content
emisar
Docs navigation

Get started

Claude.ai

Connect Claude.ai to emisar over remote MCP. OAuth signs you in — you do not need to copy an agent key.

Using Claude Code, Cursor, Claude Desktop, or a CLI instead? Those connect through the emisar-mcp stdio bridge — see Connect a CLI agent. For ChatGPT, see ChatGPT.

Before you start, you need:
  • An account with at least one runner online. Otherwise the agent signs in fine and finds an empty catalog with nothing to call. New here? Run the quickstart first, then come back to wire in your LLM.
  • Runners that do not require signed dispatch. Claude.ai and ChatGPT do not create emisar dispatch signatures, so a runner that requires one needs the local MCP bridge with a signing key and certificate instead.

Add the connector#

  1. Open Settings → Connectors (on Pro/Max it is Customize → Connectors).
  2. Click + → Add custom connector.
  3. Fill in the Connector name and the URL field:

    Connector name

    emisar

    Remote MCP server URL

    https://emisar.dev/api/mcp/rpc
  4. Leave Advanced settings (OAuth Client ID / Client Secret) empty — emisar registers your client for you via Dynamic Client Registration. Click Add.
  5. Claude opens an emisar tab. Sign in, review what the connector is asking for, and click Authorize. The connector flips on.
  6. Optional. Open Settings → Connectors → emisar. Under Tool permissions, set both Read-only tools and Write/delete tools to Always allow. This removes Claude's own per-tool prompts. Emisar policy, approvals, and audit still apply.
  7. Turn it on for a chat. The + button (lower-left of the composer) → Connectors → toggle emisar.

On Claude Team or Enterprise: this is a setting in Claude's workspace, not emisar. Only a Claude organization owner can add the connector, under Settings → Organization settings → Connectors → Add → Custom → Web. Everyone else then opens Customize → Connectors and clicks Connect to run the same sign-in.

Verify the connection#

  1. Ask the client to run linux.uptime on any one of the connected runners.
  2. Confirm that the client returns the action output.
  3. Open Audit. Confirm that the event records the client, runner, action, and reason.

What the sign-in grants#

The consent screen mints a key bound to your membership. The connector acts as you. Every call is attributed to you and the agent you are using. It reaches only the runners and actions your own access already allows (how a key inherits its operator's scope). Revoke it any time from AI agents in the console, or from the connector settings in Claude or ChatGPT.

← Previous

CLI agent

Next →

ChatGPT

Last reviewed August 21, 2026

Point your agent at real infrastructure — safely.

Set up a runner first, then connect Claude.ai to your account's MCP endpoint and let policy decide what runs.

Start free Read the quickstart

Three runners. Seven-day audit. No credit card.