OfflineCreator MCP client setup directory

Client configuration directory

Do not copy one client's object shape into another. Cursor uses mcpServers with a url field in .cursor/mcp.json or ~/.cursor/mcp.json. Claude Code's supported command is claude mcp add --transport http offlinecreator https://mcp.offlinecreatorstudio.com/mcp. VS Code uses a servers object with type set to http in .vscode/mcp.json or its user MCP configuration.

For Windsurf's legacy Cascade agent, use ~/.codeium/windsurf/mcp_config.json and an mcpServers entry with serverUrl or url. Client versions, policy controls, and reload behavior can still affect the connection. Other clients stay outside this draft until their current primary documentation and an acceptance run can support a dedicated entry.

Cursor

{"mcpServers":{"offlinecreator":{"url":"https://mcp.offlinecreatorstudio.com/mcp"}}}First-party schema match; no fresh end-to-end client acceptance test in this article.

Claude Code

claude mcp add --transport http offlinecreator https://mcp.offlinecreatorstudio.com/mcpCommand syntax corroborated by Anthropic's current MCP documentation.

VS Code / Copilot

{"servers":{"offlinecreator":{"type":"http","url":"https://mcp.offlinecreatorstudio.com/mcp"}}}Use .vscode/mcp.json or the MCP user configuration; VS Code does not use Cursor's mcpServers wrapper.

Windsurf Cascade

{"mcpServers":{"offlinecreator":{"serverUrl":"https://mcp.offlinecreatorstudio.com/mcp"}}}Current Windsurf documentation says serverUrl or url is accepted for remote HTTP; its page warns this file applies to legacy Cascade.

OAuth scopes and fallback boundary

The live protected-resource metadata names models, read, and generate as supported scopes and requires bearer tokens in the Authorization header. Its authorization-server metadata advertises authorization-code and refresh-token grants plus S256 PKCE. This verifies discovery data at the endpoint; it does not prove that every listed client completes the full flow.

If remote OAuth is unavailable, the published @offlinecreator/mcp package provides a local stdio fallback using OFFLINECREATOR_API_KEY. The registry currently reports version 0.1.1. Keep fallback keys out of URLs and source control, and use the narrower client-specific guide instead of guessing at environment interpolation.

models

Advertised OAuth scopeListed by the live protected-resource metadata.

read

Advertised OAuth scopeListed by the live protected-resource metadata.

generate

Advertised OAuth scopeListed by the live protected-resource metadata.

Continue with a client-specific setup

Choose the next page by the client you are configuring, or return to the MCP and CLI hub for transport and package context.

What this article covers

This article explains the setup directory and configuration routing, not a universal compatibility guarantee. Keep client-specific commands, acceptance dates, reload behavior, and known failures on their narrower pages. Consolidate this directory into /mcp-cli if it can no longer maintain a source-backed compatibility ledger and package reference.

This article does not treat community or social retrieval as proof of OfflineCreator quality, pricing, or customer results. Product statements stay limited to documented Studio routing, quotes, and provider disclosure for offlinecreator mcp client setup.

Coverage remains degraded. Reddit returned 14 records before HTTP 429, Instagram failed with HTTP 404, and X was unavailable because optional credentials were not configured. The YouTube records were undated in the raw export and showed zero captured views, likes, or comments; most covered building generic MCP clients or servers rather than configuring OfflineCreator. Generic setup tutorials and popularity threads cannot replace current client-primary documentation or hands-on acceptance runs.