> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sendrealm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP client compatibility

> Connect Claude, Codex, Cursor and Grok using scoped personal keys and standard MCP transports.

Sendrealm exposes standard MCP tools through **Streamable HTTP** and **local stdio**. Compatibility depends on the client application's transport/authentication support, rather than the underlying model. Configure one named, scoped personal access key per client. OAuth is deferred and must not be advertised as available.

Client documentation was checked on **October 15, 2026**. The entries below establish documented transport/authentication compatibility. They do not claim completed end-to-end testing in every vendor application.

| Client | Connection | Official setup reference |
| - | - | - |
| Claude Code | Streamable HTTP with an Authorization header, or stdio | [Claude Code MCP](https://code.claude.com/docs/en/mcp) |
| Claude web / Desktop remote connector | Public hosted URL with a fixed request header | [Claude custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) |
| Claude Desktop local MCP | Local stdio configuration or a desktop extension | [Claude local MCP](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop) |
| Codex | Streamable HTTP with `bearer_token_env_var`, or stdio | [Official OpenAI MCP documentation](https://developers.openai.com/codex/mcp) |
| Cursor | Remote URL with request headers, or stdio | [Cursor MCP](https://cursor.com/help/customization/mcp) |
| Grok API | Remote HTTP with `authorization` or request headers | [xAI remote MCP tools](https://docs.x.ai/developers/tools/remote-mcp) |
| Grok Build | HTTP with a static authorization header, or stdio | [Grok Build MCP](https://docs.x.ai/build/features/mcp-servers) |
| Grok chat custom connector | Public MCP URL; confirm that the available connector UI accepts the required API-key/header configuration | [Grok connectors](https://docs.x.ai/grok/connectors) |

The hosted endpoint is `https://mcp.sendrealm.com/mcp`. Send `Authorization: Bearer YOUR_PERSONAL_ACCESS_KEY` through the client's credential/header settings. Never put the credential in a prompt, tool argument, URL, or committed project configuration. In a shared connector, a fixed credential represents the key owner's access for every connector user; scope it accordingly. Separate per-user keys are preferable when the client supports them.

## Codex

Configure the hosted server in the user's MCP configuration:

```toml theme={null}
[mcp_servers.sendrealm]
url = "https://mcp.sendrealm.com/mcp"
bearer_token_env_var = "SENDREALM_API_KEY"
```

Set `SENDREALM_API_KEY` in the environment available to Codex. The value is the scoped personal key, without an additional `Bearer` prefix. Do not set a connection-level project selector.

## Claude, Cursor, and other JSON-configured clients

For remote clients that accept headers, use the hosted URL and put the bearer key in the client's protected credential configuration. Claude's custom connector setup has request-header configuration; Claude Code also accepts an HTTP server with a bearer header. Cursor's MCP configuration accepts `url` and `headers`.

A local stdio configuration uses the same package across supported clients:

```json theme={null}
{
  "mcpServers": {
    "sendrealm": {
      "command": "npx",
      "args": ["-y", "@sendrealm/mcp"],
      "env": {
        "SENDREALM_API_KEY": "YOUR_PERSONAL_ACCESS_KEY"
      }
    }
  }
}
```

Replace the placeholder only in a private configuration. Use the client's environment or secret substitution feature where available. Local stdio requires Node.js 20 or later. A chat/cloud client cannot launch a process on the customer's laptop; use the hosted connection there.

## Portable workflows

* Discover the account, teams and projects; pass `project_id` explicitly on every project tool call.
* Preserve `tools/list` continuation cursors and data-page cursors. Key scopes and deployment feature flags filter discovery.
* Imports use ordinary job polling with `poll_after_ms`. They do not require optional MCP Tasks support, sampling, elicitation, or local filesystem access.
* Chat-only clients can append bounded typed batches or return an authenticated upload handoff. Coding agents can use streaming SDK/CLI helpers.
* Prepared actions are ordinary tools: inspect effects, then execute with `prepared_action_id` and a stable `idempotency_key`. Client approval prompts do not replace server-side authorization, readiness, or receipt checks.
* Text results accompany structured results so clients can still read outcomes when they do not render structured output specially.

## Verification and limits

The automated suite checks supported HTTP protocol-version negotiation, successful standard HTTP and stdio connections, tool discovery, project calls, strict schemas, authentication errors, pagination and fixture-backed journeys. These are protocol-level tests, not vendor-app certification or live model evaluations.

Before claiming a specific client/version as verified, record its application version, transport, authentication mode, discovery across all pages, an authorized read, a staged import, a reviewed mutation/retry, and permission-denial recovery using isolated test data. Live actions require separate explicit scope and task authorization. Do not use a production broadcast as a compatibility check.

Legacy SSE-only clients are not supported by the hosted endpoint; choose Streamable HTTP or local stdio. Browser-origin clients must use an explicitly allowed Origin; server-to-server connectors ordinarily connect without a browser Origin. Preserve the origin/host protections when configuring deployments.

New UI-parity features remain subject to their rollout flags and release status. Protocol compatibility does not imply every planned workflow is already available. Billing remains excluded.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.