Configure OfflineCreator MCP in VS Code and Copilot

Use VS Code's MCP schema

Create `.vscode/mcp.json` for a VS Code workspace connection, or run `MCP: Open User Configuration` for a profile-wide connection. VS Code's current format uses a top-level `servers` object, not the `mcpServers` key used by some other clients.

When Agent Host is enabled, VS Code forwards configured servers except entries that require interactive inputs, but Agent Host does not read `.vscode/mcp.json` directly. For a configuration portable across Agent Host and other Copilot tools, Microsoft recommends workspace `.mcp.json` or user `~/.copilot/mcp-config.json`, which Agent Host reads natively.

Add OfflineCreator as an HTTP server with the exact endpoint shown here. Microsoft requires `type` and `url` for this server class and says VS Code tries Streamable HTTP before falling back to SSE.

Workspace configuration

.vscode/mcp.jsonUse for the VS Code workspace path; VS Code forwards eligible entries when Agent Host is enabled.

Portable Copilot configuration

.mcp.json or ~/.copilot/mcp-config.jsonUse when the same non-secret server definition must be read natively by Agent Host or other Copilot tools.

Configuration

{"servers":{"offlinecreator":{"type":"http","url":"https://mcp.offlinecreatorstudio.com/mcp"}}}Uses the current VS Code `servers` schema and OfflineCreator's recommended remote endpoint.

Keep authentication out of the file

Do not add an API key or fixed Authorization header to the recommended remote configuration. OfflineCreator's live protected-resource metadata points to its authorization server, and the authorization metadata advertises dynamic client registration, authorization-code and refresh-token grants, and S256 PKCE.

Start the server from VS Code and complete any browser consent it presents. This is the documented configuration to test, not a fresh acceptance result: this research pass did not complete the browser flow in a live VS Code and GitHub Copilot client.

Verify startup and tool discovery separately

Open the Command Palette and run `MCP: List Servers`, then select `offlinecreator`. VS Code exposes actions to start, stop, restart, or show output for a configured server. Confirming that the JSON parses is only the first checkpoint; inspect the server state and output before asking Copilot to use a tool.

After connection, open Chat and use Configure Tools to inspect and toggle the available tools. The current OfflineCreator package documents nine MCP tools, but this research did not verify that all nine appear after an OAuth grant in VS Code.

Configuration

VS Code accepts the `servers` entryConfirms schema and file location only.

Connection

MCP: List ServersInspect status and use Show Output when startup or authentication fails.

Discovery

Chat > Configure ToolsConfirm which OfflineCreator tools are actually available to Copilot.

Diagnose the observed failure state

If the server does not start, choose Show Output from `MCP: List Servers` before changing transport or copying another client's schema. VS Code requires a trust decision for a new or changed server configuration, and an untrusted server does not start.

If the connection succeeds but Copilot shows an old or incomplete tool list, run `MCP: Reset Cached Tools`, then restart the server. Microsoft documents that command specifically for clearing a changed server's cached tool list.

Choose the next client setup step

Return to the client directory for another verified setup, review reload and cache behavior, or compare the separate Windsurf configuration before reusing this JSON elsewhere.

Editorial boundary

This page owns only the OfflineCreator setup path for VS Code and GitHub Copilot. It does not treat a documentation match as proof of successful OAuth, tool discovery, media generation, or compatibility with every VS Code build.