Skip to main content
emisar
Docs navigation

Get started

ChatGPT

Connect ChatGPT to emisar through Developer mode over remote MCP. OAuth signs you in, so 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 Claude.ai, see Claude.ai.

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 connect your LLM.
  • A publicly reachable HTTPS server URL. The URL connection in these guides cannot reach localhost or a private network address. If you run emisar privately, use a local AI client that can reach it instead.
  • 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#

ChatGPT reaches a custom MCP server through Developer mode. Access depends on your account and workspace policy.

  1. Open Connect an agent in emisar and select ChatGPT.
  2. In ChatGPT, open Settings and select Security and login.
  3. Turn on Developer mode. If the option is missing, check your account's eligibility or ask your workspace admin about access.
  4. Open ChatGPT Plugins and select + next to the search box.
  5. Fill the form:
    • Name: paste the name below
    • Description (optional): "Run approved infrastructure actions on my fleet."
    • Connection → Server URL: paste the URL below
    • Authentication: choose OAuth. There is no client ID or secret to paste; emisar registers the connector itself.

    Name

    emisar

    Remote MCP server URL

    https://emisar.dev/api/mcp/rpc

    Select Create, then review the discovered tools and metadata.

  6. ChatGPT opens the emisar sign-in page. Sign in, review the requested access, and choose Authorize. ChatGPT then lists the emisar tools.
  7. Review the connection permissions. emisar policy, approvals, and audit still apply to every call.
  8. Start a new chat. Add emisar from the tools menu. A listed tool means metadata access only: ChatGPT sees the tool but cannot call it yet. Adding the connection lets the chat call those tools.

If emisar's tools change, open its connection in ChatGPT Plugins and select Refresh before starting a new chat. See the ChatGPT connection guide.

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

Claude.ai

Next →

Agent sandboxes

Last reviewed September 6, 2026

Point your agent at real infrastructure — safely.

Set up a runner first, then connect ChatGPT 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.