Connect

Hosts connect to one public Everyn MCP endpoint. Thin host packages may change install metadata, but they must not fork tools, authorization, errors, side effects, or workflow rules.

Endpoint

Use the URL above as the remote MCP server. Do not send Dataset bytes, export CSV, or arbitrary fetch URLs through the /mcp body. Uploads and downloads use constrained transfer descriptors; the client moves the bytes.

Supported hosts

V1 is headless and host-neutral. The same catalog is designed for:

• ChatGPT and Codex
• Claude (web, desktop, and Code)
• Cursor
• Generic MCP clients that speak Streamable HTTP
• The Official MCP Registry entry that points at this endpoint

Host directories and marketplace listings are external outcomes. They are not required to use the public endpoint.

Host install recipes

These recipes use the same Streamable HTTP URL, WorkOS OAuth, and one-organization grant. Do not send an API key. Do not request custom Everyn CIMD or DCR scopes.

Claude

Claude web, desktop, and Claude Code share one remote connector.

1. Add a custom remote MCP connector named Everyn.
2. Use URL https://mcp.everyn.ai/mcp and transport Streamable HTTP.
3. Complete OAuth and select exactly one Everyn organization.
4. Call get_context before mutating work.

Claude Code:

claude mcp add --transport http everyn https://mcp.everyn.ai/mcp

Codex

Codex uses the same remote URL. Add a remote MCP server named everyn with URL https://mcp.everyn.ai/mcp in Codex MCP settings or ~/.codex/config.toml. Complete OAuth and select exactly one organization. Thin Codex plugins are a later distribution slice; this recipe is the remote server only.

Cursor

Cursor uses a remote mcp.json entry for the same URL:

{
  "mcpServers": {
    "everyn": {
      "url": "https://mcp.everyn.ai/mcp"
    }
  }
}

Complete OAuth and select exactly one organization. Cursor Marketplace listing is a later review outcome, not a V1 runtime dependency.

Compatibility

Compatibility adapters may negotiate an older deployed client — for example a host that still initializes on an earlier protocol revision — without changing application schemas, side effects, authorization, or IDs.

V1 does not require:

• MCP Apps or a host-rendered UI
• ChatGPT-only file parameters
• URL-mode elicitation
• Host background tasks or MCP Tasks as the Run lifecycle

Those adapters may appear later. They must feed the same upload_csv, Run, and export_run handles.

Client registration

WorkOS AuthKit Standalone Connect is the public authorization server. Client identification uses CIMD. Dynamic client registration exists only as a bounded compatibility path for target hosts that still need it.

Hosts that use CIMD or dynamic client registration must request only the standard OIDC scopes WorkOS can advertise. See Authentication.

Connect checklist

1. Add the remote MCP server URL shown above.
2. Complete OAuth and select exactly one Everyn organization.
3. Call get_context before mutating work.
4. Follow the workflow.

If the host cannot move local CSV bytes, skip the transfer ticket and use the Datasets fallback described in Datasets.