OfflineCreator MCP compatibility with Cline

Treat Cline compatibility as a qualified setup candidate

Cline's current documentation accepts hosted MCP servers and recommends Streamable HTTP. OfflineCreator publishes a Streamable HTTP endpoint with OAuth metadata. Those protocol declarations align, but this research pass did not complete browser authorization or a tool call in a current Cline build.

Use the configuration below as a documentation-backed acceptance candidate, not as a promise of support. Keep the page in draft until a dated Cline run records the client surface, version, completed authorization, visible tools, and one tool response after reviewing that tool's current schema and documented effects.

Documentation result

Transport and OAuth prerequisites alignCurrent first-party sources support attempting the connection.

Acceptance result

Not testedNo successful OfflineCreator authorization or tool invocation in Cline was observed.

Add the explicit Streamable HTTP configuration

In the Cline IDE extension, open MCP Servers, choose Configure, and either use the Remote Servers tab or edit the JSON under `mcpServers`. Set the transport explicitly: Cline documents that a remote entry without `type` falls back to legacy SSE for backward compatibility.

For Cline CLI, the documented settings file is `~/.cline/mcp.json`; the interactive `cline mcp` wizard can add a remote URL. Use the same server object when editing that file directly. Do not add a fixed Authorization header to the recommended OAuth candidate.

Server name

offlinecreatorA local label used by Cline.

Recommended JSON

{"mcpServers":{"offlinecreator":{"type":"streamableHttp","url":"https://mcp.offlinecreatorstudio.com/mcp","disabled":false,"autoApprove":[]}}}The explicit type avoids Cline's documented legacy-SSE default.

CLI settings

~/.cline/mcp.jsonUse `cline mcp` if you prefer the current interactive configuration path.

Complete OAuth only when Cline offers authorization

Save or add the remote server, then inspect its status in Cline. If the client offers an authorization action, complete the Studio browser flow and return to Cline. OfflineCreator's live metadata advertises dynamic client registration, authorization-code and refresh-token grants, and S256 PKCE; its protected-resource document names the exact `/mcp` URL and the `models`, `read`, and `generate` scopes.

A current Cline Desktop release says remote MCP servers can authorize from Settings and supports both dynamic registration and servers that require a pre-registered client. That is fresh evidence for Cline Desktop, not proof that the IDE extension or CLI completed OfflineCreator's flow in this environment.

Expected boundary

Cline authorization action, browser consent, return to clientDo not substitute a personal key in the URL.

Client-surface warning

Desktop release evidence is not IDE or CLI acceptanceRecord the exact Cline surface and version during testing.

Verify discovery before any generation

Cline's setup guide says to verify that tools appear and test one tool call. After authorization, confirm that the server is enabled and ask Cline to identify the tools provided by the `offlinecreator` server. Before invoking any tool, inspect its current schema and documented effects in the connected client.

The current OfflineCreator package documents nine named tools. Separately, the live protected-resource metadata advertises the `models`, `read`, and `generate` scopes. Neither source directly proves how granted scopes affect Cline's visible tool list, so record what Cline actually shows and leave `autoApprove` empty during acceptance.

First check

List the tools available from the offlinecreator MCP server.Confirm discovery and names before invoking a tool.

Tool-call gate

Review the current schema and effects before invocationThis research does not establish that `list_models` cannot spend credits or initiate generation.

Separate transport, authorization, and tool failures

If the server does not connect, first confirm the full HTTPS URL and the explicit `streamableHttp` type. If Cline behaves as though the server were SSE, re-open the saved entry and check that the type was not omitted. Cline's current settings documentation also provides enable, disable, restart, timeout, and remove controls.

If the server connects but tools do not appear, confirm that browser authorization completed and the entry is enabled, then restart the server from Cline. If tools appear but a call is denied, record the granted scopes and the exact error without sharing tokens, browser data, prompts, or media.

Continue with the right next action

Return to the client directory to choose another host, use the verification checklist to record a dated acceptance result, or compare reload and tool-cache behavior before changing a working configuration.

Page boundary

This page owns only the OfflineCreator setup candidate and acceptance boundary for Cline. It does not generalize Cline configuration to other clients, claim that matching OAuth declarations guarantee interoperability, or promise successful authentication, tool discovery, generation, account access, or reliability.