VS Code

VS Code’s GitHub Copilot Chat reads MCP servers from `mcp.json`, add Creatorland once and it’s available across your sessions.

Add to VS Code

One click installs the server; the manual config below does the same thing.

Setup

VS Code

VS Code (GitHub Copilot Chat, Agent mode), create .vscode/mcp.json in your workspace or edit your user-scoped mcp.json:

{
  "servers": {
    "creatorland": {
      "url": "https://mcp.creatorland.com/mcp"
    }
  }
}

Reload the VS Code window (Cmd+Shift+P → “Developer: Reload Window”) so Copilot Chat picks up the new server. Then in Copilot Chat, switch to Agent mode → open the tool picker → enable “creatorland.” The OAuth flow runs in your default browser the first time you invoke a tool.

Loading setup…

Who it’s for: Developers running GitHub Copilot Chat in Agent mode inside VS Code.
Compatibility: GitHub Copilot Chat in VS Code supports MCP servers via `.vscode/mcp.json` (workspace) or your user-scoped `mcp.json` (settings file location varies by OS). Agent mode must be enabled in Copilot Chat’s settings for MCP tools to appear.
Verify the connection: After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.

Troubleshooting

After editing `mcp.json`, reload VS Code’s window (Cmd+Shift+P → “Developer: Reload Window”) so Copilot Chat picks up the new server.
In Copilot Chat, switch to Agent mode and open the tool picker to confirm “creatorland” is listed and toggled on.
If the OAuth flow opens but doesn’t return cleanly, check VS Code’s output panel under “GitHub Copilot Chat” for the redirect URL and complete the flow manually if needed.

Other clients

Windsurf

Zed

OpenClaw