emisar documentation

Point Claude.ai and ChatGPT at your catalog over remote MCP and OAuth — no key to manage.

Wire Claude Code, Cursor, Claude Desktop, and the CLIs in with the emisar-mcp bridge or a raw API key.

The full runner install: every flag, the service it creates, the config file, and the user it runs as.

Run the runner in a container — what it can see, the two shared mechanics, and a sidecar.

One runner per node as a DaemonSet, with the pod spec as your blast-radius dial.

A Nomad system job placing one runner on every client node, with a worked HCL spec.

Enroll ephemeral runners from one reusable key as autoscaling groups — GCP MIG, AWS ASG, Azure VMSS — boot and terminate hosts.

Go from one runner to a governed fleet, with a phased rollout and a checklist.

Risk-tier defaults, per-action overrides, approvals, and standing grants.

Saved, versioned action sequences your LLM can read and run, gated per step.

The run list and filters, every lifecycle status, live output and byte caps, cancellation, and how one dispatch's runs group.

Roles, invitations, per-member runner scopes, MFA, sessions, and API keys.

OIDC sign-in with Google Workspace, Okta, Keycloak, or any compliant provider.

SCIM 2.0 provisioning and group→role mapping — offboarding in your IdP revokes access.

Groups and labels, enrollment keys, pack credentials, updates, and removal.

How an MCP key inherits its operator's runner scope, minting, rotating, and revoking keys, and keeping the emisar-mcp bridge supported.

Make a runner run only actions a real person signed in their MCP client.

What gets recorded, the dashboard, NDJSON export, and the runner journal.

Plan limits, feature entitlements, upgrades and downgrades, invoices, and payment failures.

Action YAML reference: declared args, validation, limits, and redaction.

Write, validate, install, and trust a pack you maintain.

Run a private registry on GCS, S3, or any static host with packctl.

Methods, parameters, idempotency, and errors — the MCP server contract.

The on-host emisar binary's operator verbs — connect, packs, events, audit, and signing — with their key flags.

Trust boundary, searchable audit, hash-chained journal, redaction on egress.

The output, MCP, audit-export, and retention caps emisar enforces — and what happens at each.

The supported product is the hosted emisar control plane today; plans and audit retention are on the pricing page.