Cursor vs Claude Code setup for OfflineCreator MCP

Compatibility ledger verified from current documentation

As accessed on August 9, 2026, Cursor's MCP reference supports Streamable HTTP and OAuth, gives project and global `mcp.json` locations, and documents MCP logs in the Output panel. Claude Code's current reference recommends HTTP for remote cloud services, documents the `claude mcp add` syntax, and distinguishes a saved configuration from a connected server by requiring a later status check.

The validation level for this page is documentation-corroborated, not end-to-end accepted. The client vendors and OfflineCreator publish mutually consistent setup shapes, and the live endpoint publishes OAuth discovery metadata. No fresh run on named Cursor and Claude Code builds completed browser consent, listed OfflineCreator tools, invoked generation, refreshed a token, and revoked the connection. Do not interpret this ledger as a tested-build certification.

Cursor

Documentation-corroboratedOfficial client schema and OfflineCreator's Cursor example agree; fresh runtime acceptance remains open.

Claude Code

Documentation-corroboratedOfficial command/schema and OfflineCreator's package README agree; fresh runtime acceptance remains open.

Freshness

Sources accessed 2026-08-09Recheck monthly because client schemas, OAuth handling, and status interfaces can change.

Read the evidence in the order it can prove

Use each client vendor's reference to decide what that client parses and how it reports status. Use OfflineCreator's product page and published package to identify the actual server URL and product-specific recipe. Use the live protected-resource and authorization-server documents only for what the server currently advertises: resource identity, models/read/generate scopes, bearer headers, authorization-code and refresh-token grants, dynamic registration, and S256 PKCE.

Those source types are reciprocal but not substitutes. An advertised OAuth grant does not prove a particular client build completed consent, and a package README cannot establish the syntax of every future client release. The evidence therefore supports setup instructions and a documentation-level compatibility label while leaving runtime success, tool discovery, token refresh, and revocation as explicit acceptance-test gaps.

Cursor primary reference

Cursor MCP documentationDefines `mcp.json`, remote URL entries, OAuth support, config locations, and logs.

Claude Code primary reference

Claude Code MCP documentationDefines the HTTP add command, JSON `type`, scopes, status commands, and authentication flow.

OfflineCreator primary references

Product guide, npm release, and live OAuth metadataDefine the endpoint and recipes, then expose current server-advertised authorization capabilities.

Keep client configuration separate from server authorization

Cursor and Claude Code store or generate different client-side configuration, then both contact the same protected resource. OfflineCreator's live metadata identifies that resource as `https://mcp.offlinecreatorstudio.com/mcp`, names its authorization server, limits bearer-token delivery to the header method, and advertises models, read, and generate scopes. The authorization metadata advertises authorization-code and refresh-token grants plus S256 PKCE.

A URL-only Cursor entry and a Claude Code HTTP registration avoid placing a Studio API key in the published remote examples. That does not mean authentication is absent: browser OAuth supplies the authorization relationship. It also does not make generation local. OfflineCreator states that MCP remains an interface to its cloud Studio service and that selected models run through disclosed cloud providers.

Choose the setup surface, not a different OfflineCreator server

Both clients can point at the same hosted OfflineCreator endpoint, but their supported setup shapes are not interchangeable. Cursor documents a remote entry under `mcpServers` with a `url` in `.cursor/mcp.json` or `~/.cursor/mcp.json`. Claude Code documents the terminal command `claude mcp add --transport http offlinecreator https://mcp.offlinecreatorstudio.com/mcp`; if the equivalent entry is written as JSON, Claude Code requires `type: "http"` alongside the URL.

For a single operator who prefers a visible project file, Cursor is the shorter JSON example. For an operator who prefers registration and status checks from a shell, Claude Code supplies a first-party add command and server-management commands. This is a configuration comparison, not a claim that either client changes OfflineCreator's models, scopes, cloud processing, or credit rules.

Cursor remote shape

`mcpServers` → `offlinecreator` → `url`No transport field appears in the current OfflineCreator Cursor example.

Claude Code remote shape

`claude mcp add --transport http`Handwritten Claude Code JSON needs both `type: "http"` and `url`.

Shared destination

`https://mcp.offlinecreatorstudio.com/mcp`The published OfflineCreator package recommends this Streamable HTTP OAuth endpoint for both clients.

Match the client to the configuration workflow

Choose Cursor when the working context is already its editor or CLI and you want the same project or global `mcp.json` configuration across those surfaces. Cursor's CLI documentation says it shares the editor configuration and provides `agent mcp list`, `agent mcp list-tools`, and `agent mcp login` for inspection and authentication.

Choose Claude Code when the working context is terminal-first and you want an explicit add command with local, user, or project scope. The default add is local to the current project; `--scope user` makes it available across projects, while `--scope project` writes a shareable `.mcp.json` that requires workspace approval. Neither choice is automatically better for privacy or output quality because both recipes reach the same OfflineCreator cloud endpoint.

Continue with the exact client or comparison question

After choosing a surface, use the dedicated Cursor or Claude Code setup page for the operational walkthrough rather than translating the other client's syntax. Return to the comparison directory if the unresolved decision is transport, authentication, CLI versus MCP, or direct API access. The Claude Desktop comparison is separate because its connector UI and configuration lifecycle are not the Claude Code CLI workflow described here.

Editorial boundary

This page owns only the current Cursor-versus-Claude-Code setup distinction for OfflineCreator: config location, schema or command, scope, OAuth handoff, status checks, and validation level. It does not own a general product-quality comparison, model-performance ranking, pricing verdict, Claude Desktop connector guide, or proof that every current build completes OAuth. Refresh the client references, OfflineCreator package release, and live metadata before changing the compatibility label.