Connect an LLM

Claude (claude.ai)

1. Open Settings → Connectors (on Pro/Max it's Customize → Connectors).
2. Click + → Add custom connector.
3. Paste the Remote MCP server URL above into the URL field.
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. Turn it on for a chat: the + button (lower-left of the composer) → Connectors → toggle emisar.

Team / Enterprise: only an Owner can add the connector, under Settings → Organization settings → Connectors → Add → Custom → Web. Members then open Customize → Connectors and click Connect to run the same sign-in.

ChatGPT

ChatGPT now calls custom MCP connectors apps. Developer mode exposes the app-creation flow for your own MCP server. Available on Plus, Pro, Business, Enterprise, and Education.

1. Enable it once: Settings → Apps & Connectors → Advanced settings → turn on Developer mode.
2. Open Settings → Connectors and click Create.
3. Fill the form:
   • Connector name — emisar
   • Description — e.g. "Run approved infrastructure actions on my fleet."
   • Connector URL — https://emisar.dev/api/mcp/rpc
   • Authentication — choose OAuth
4. Click Create. ChatGPT sends you to an emisar sign-in → Authorize. If ChatGPT shows a token or header field, switch the authentication type back to OAuth.
5. Use it from a new chat: click the + button near the composer, choose More, then select emisar. Seeing actions in settings only proves ChatGPT fetched metadata; this step adds the app to the conversation context so the model can call it.
6. After changing emisar's tool metadata, open the connector in settings and choose Refresh before testing again.

ChatGPT connects to remote HTTPS MCP servers only — there is no stdio option. The emisar endpoint is already remote, so nothing extra to host.

What the sign-in grants

The consent screen mints a key bound to your membership. The connector can only run actions your policy already permits, every call is attributed to you in the audit log, and anything needing approval still waits for a human. Revoke access any time from LLM agents in the dashboard, or from the connector settings in Claude / ChatGPT.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "emisar": {
      "command": "/usr/local/bin/emisar-mcp",
      "env": {
        "EMISAR_URL": "https://emisar.dev",
        "EMISAR_API_KEY": "emk-..."
      }
    }
  }
}

Restart Claude Desktop. Tools appear under the tool icon as "emisar".

Cursor

Same bridge. Cursor reads ~/.cursor/mcp.json:

{
  "mcpServers": {
    "emisar": {
      "command": "emisar-mcp",
      "env": {
        "EMISAR_URL": "https://emisar.dev",
        "EMISAR_API_KEY": "emk-..."
      }
    }
  }
}

Recent Cursor builds also speak remote MCP — point them at /api/mcp/rpc directly (step 1) if you'd rather skip the bridge.

Claude Code

One-line register, user scope (every project):

$ claude mcp add emisar /usr/local/bin/emisar-mcp \
    --scope user \
    -e EMISAR_URL=https://emisar.dev \
    -e EMISAR_API_KEY=emk-...

Verify with claude mcp list.

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "emisar": {
      "command": "/usr/local/bin/emisar-mcp",
      "env": {
        "EMISAR_URL": "https://emisar.dev",
        "EMISAR_API_KEY": "emk-..."
      }
    }
  }
}

ChatGPT Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.emisar]
command = "/usr/local/bin/emisar-mcp"
env = { EMISAR_URL = "https://emisar.dev", EMISAR_API_KEY = "emk-..." }