Connect Claude Code to OfflineCreator MCP

Add OfflineCreator with Claude Code's HTTP transport

Run `claude mcp add --transport http offlinecreator https://mcp.offlinecreatorstudio.com/mcp` from the project where you want the connection. Anthropic's current basic HTTP syntax places `--transport http` before the server name. The command uses Claude Code's default local scope, so the entry is private to you and limited to the current project.

The endpoint matches OfflineCreator's live protected-resource metadata, current product documentation, and published package README. This documentation match establishes the configuration to try; it does not establish that OAuth or tool discovery succeeded in a live Claude Code client.

Recommended command

claude mcp add --transport http offlinecreator https://mcp.offlinecreatorstudio.com/mcpMatches Anthropic's current basic HTTP syntax; no API key is placed in the command or URL.

Optional user scope

claude mcp add --transport http offlinecreator --scope user https://mcp.offlinecreatorstudio.com/mcpUse only if you want the connection available across your projects.

Complete OAuth without adding a bearer header

After adding the server, run `claude mcp login offlinecreator` in an interactive terminal, or open `/mcp` inside Claude Code and select the server to start browser authorization. Claude Code supports OAuth 2.0 for remote HTTP servers and can discover an authorization server from the protected resource metadata.

OfflineCreator's live metadata advertises the `models`, `read`, and `generate` scopes, bearer tokens in the Authorization header, authorization-code and refresh-token grants, and S256 PKCE. Let Claude Code manage that flow. Do not add a fixed Authorization header unless you intentionally choose a documented API-key fallback.

Verify configuration, authentication, and discovery separately

An `Added ...` message confirms that Claude Code wrote the configuration; it does not prove a working connection. Run `claude mcp list` and look for `Connected` rather than `Needs authentication` or `Failed to connect`. Use `claude mcp get offlinecreator` for the stored server details, then open `/mcp` to confirm the server's status and visible tool count.

OfflineCreator's immutable 0.1.2 package record documents nine MCP tools, including model listing, credit lookup, generation submission, status and wait operations, download, cancellation, and recent-generation listing. That package record does not establish the tool list exposed after an OAuth grant in Claude Code, which still requires hands-on verification.

Configuration written

claude mcp get offlinecreatorConfirms the stored name, transport, URL, and scope.

Connection health

claude mcp listDistinguishes Connected, Needs authentication, and Failed to connect.

Tool discovery

/mcpInspect the server status and tool count inside an interactive Claude Code session.

Diagnose the failure state before changing transport

If the server shows `Needs authentication`, use `/mcp` or `claude mcp login offlinecreator`; changing to stdio does not fix an unfinished OAuth flow. If it shows `Failed to connect`, inspect `claude mcp get offlinecreator` for the reported HTTP status or server error and confirm the exact HTTPS endpoint. If the add command rejects an option, compare it with the installed client's help and Anthropic's current basic HTTP example instead of assuming one universal position for every option.

This research pass verifies the current Anthropic syntax and live OfflineCreator metadata, but it is not a hands-on acceptance result: Claude Code was not installed in the research environment, so browser consent and actual tool discovery were not executed. Keep the page as an unreviewed draft until a dated end-to-end client run confirms both.

Choose the next client setup step

Return to the client directory for another client, compare current capability evidence, or check configuration-file ownership before sharing a project-scoped MCP entry.

Editorial boundary

This page owns only the Claude Code-specific command, scope, authentication, status, and discovery path. It does not claim that a documentation match equals successful OAuth, tool invocation, media generation, or compatibility with every Claude Code build. Client acceptance remains not run and must be added only from a dated hands-on record.