Add OfflineCreator as a Claude custom connector

Verified against current connector documentation

This setup was checked on August 9, 2026 against OfflineCreator Studio's live MCP page, OAuth discovery metadata, the published package README, and Anthropic's current custom-connector help. It is documentation-verified, not a claim that this research pass completed a fresh end-to-end connection inside every Claude plan and client.

Recommended endpoint

https://mcp.offlinecreatorstudio.com/mcpHosted Streamable HTTP with browser OAuth; do not add an API key to the URL.

Verification date

August 9, 2026Refresh monthly because Claude connector navigation and server metadata can change.

What this research could and could not verify

Source-backed setup boundary: OfflineCreator's current first-party page and package identify the public endpoint and stdio fallback; its discovery documents name the OAuth metadata; and Anthropic documents the custom-connector navigation. These sources support the setup instructions, but they are not a substitute for a hands-on Claude acceptance run.

Research-process note, not publishable product or community evidence: the last30days pass returned 60 records. It found generic Claude connector walkthroughs, but no practitioner report about OfflineCreator itself; most records were unrelated Claude, MCP, or prefix-match results. Reddit was partial, arXiv timed out, Instagram failed, and optional X access was not configured, so community coverage remains insufficient rather than proving silence.

For an authentication failure, Anthropic's troubleshooting guidance says to disconnect and reconnect from Customize > Connectors. Team and Enterprise members should also confirm that an Owner or Primary Owner added the custom connector for the organization before members connect individually.

Add OfflineCreator to Claude

For an individual Claude account, open Customize, choose Connectors, select the plus button, and choose Add custom connector. Name it OfflineCreator, enter https://mcp.offlinecreatorstudio.com/mcp, and add it. OfflineCreator's published setup says the recommended endpoint uses browser sign-in and consent, so the normal path does not place a personal API key in the connector URL or client configuration.

After the connector appears, select Connect and complete the Studio authorization flow. In a conversation, open the plus menu, choose Connectors, and enable OfflineCreator for that conversation. Availability in the list and a completed authorization are separate from enabling the connector in a particular chat.

Name

OfflineCreatorA local display name for the custom connector.

Remote MCP URL

https://mcp.offlinecreatorstudio.com/mcpUse this exact public endpoint without query-string credentials.

Advanced OAuth fields

Leave blank for the documented default flowAnthropic exposes optional client ID and secret fields, while OfflineCreator publishes browser OAuth on the endpoint itself.

Review the OAuth boundary

OfflineCreator's live protected-resource metadata identifies the MCP resource and advertises models, read, and generate scopes with bearer tokens in the Authorization header. Its authorization-server metadata advertises authorization-code and refresh-token grants, dynamic client registration, token revocation, and S256 PKCE. These records verify the server's discovery contract; they do not prove that a specific Claude account has granted every scope.

Review the consent screen before authorizing. Anthropic warns that custom connectors are not verified by Anthropic and can expose tools that read data or take actions. Enable only the tools needed for the conversation, and disconnect the connector if the requested permissions or tool behavior are unexpected.

models

Advertised scope nameThe metadata lists this string without defining its permission semantics.

read

Advertised scope nameThe metadata lists this string without defining its permission semantics.

generate

Advertised scope nameThe metadata lists this string without defining its permission semantics.

Use stdio only when the connector path is unavailable

Claude custom connectors are remote: Anthropic's cloud connects to the public MCP server even when you use Claude Desktop. If organization policy prevents adding the connector, or if you specifically need Claude Desktop's local MCP mechanism, the published @offlinecreator/mcp package documents a stdio fallback in claude_desktop_config.json.

The fallback requires OFFLINECREATOR_API_KEY in the process environment section. Keep that secret out of chat messages, URLs, and source control. The remote connector and local stdio configuration are different mechanisms; do not paste the stdio JSON into Claude's Add custom connector URL field.

Command

npxRuns the published package as a local stdio server.

Arguments

["-y", "@offlinecreator/mcp"]Use the package name exactly as published.

Environment

OFFLINECREATOR_API_KEYStore the personal key only in secret configuration; never append ?api_key= to a URL.

Continue with the right next step

Use the client directory for a different MCP host, the configuration-location guide for local files, or the reload guide when a saved connection is not visible.

Page boundary

This page owns the Claude custom-connector flow and its documented Claude Desktop stdio fallback. It does not own Claude Code terminal setup, a general client capability matrix, or a universal compatibility guarantee. Keep those details on their dedicated pages, and retain this page as a draft until editorial review and a fresh hands-on Claude acceptance run are complete.