Connect Claude Code to Gcore MCP Server

Claude Code is the recommended client for Gcore MCP Server due to its deferred schema loading. It fetches tool schemas on demand when they match a query, allowing it to work with all Gcore tools without context window limits.

Prerequisites

• Gcore API token with permissions for the operations to perform
• uv package manager installed
• Git for Windows (Windows only) — download from git-scm.com

Step 1. Install Claude Code

Windows PowerShell

irm https://claude.ai/install.ps1 | iex

After installation, restart PowerShell to update the PATH.

macOS/Linux

curl -fsSL https://claude.ai/install.sh | bash

Verify the installation:

claude --version

Step 2. Authenticate Claude Code

1. Start Claude Code in any directory:

claude

2. On first launch, select a color theme and press Enter.

3. Enter the login command:

/login

4. A browser window opens for authentication. Sign in with a Claude Pro, Max, Team, or Enterprise account.

5. If the browser displays an authentication code instead of redirecting automatically, copy the code and paste it into the terminal prompt.

Claude Code requires a paid subscription (Pro, Max, Team, or Enterprise). Free accounts cannot use Claude Code.

Step 3. Configure Gcore MCP Server

The configuration file defines MCP server connections. Add Gcore MCP Server to enable Gcore API access.

Windows

Open the configuration file:

notepad $env:USERPROFILE\.claude.json

macOS/Linux

Open the configuration file:

nano ~/.claude.json

Add the Gcore MCP Server entry to the mcpServers section:

{
  "mcpServers": {
    "gcore-mcp-server": {
      "command": "uvx",
      "args": [
        "--from",
        "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git",
        "gcore-mcp-server"
      ],
      "env": {
        "GCORE_API_KEY": "your-api-key",
        "GCORE_TOOLS": "*"
      }
    }
  }
}

Replace your-api-key with the Gcore API token. Save the file.

If the configuration file already contains other settings, merge the mcpServers section without overwriting existing content. JSON syntax errors cause Claude Code to fail silently.

Step 4. Verify the connection

Restart Claude Code to load the new configuration:

claude

Check that Gcore MCP Server is connected:

claude mcp list

The output shows gcore-mcp-server with status Connected:

gcore-mcp-server: uvx --from gcore-mcp-server@... - ✓ Connected

Test with a resource query:

List my CDN resources

A successful response displays CDN resource details, including resource ID, CNAME, status, and configuration.

If the server shows Failed to connect, verify that uv is installed and the API key is valid. Test the API key independently:

curl -H "Authorization: Bearer your-api-key" https://api.gcore.com/cdn/resources

A 200 response confirms valid credentials. A 401 response indicates an invalid or expired key.

Tool search behavior

When a query mentions a product or operation, Claude Code searches tool names and descriptions for matches, loads schemas for matched tools, and executes the appropriate tool. The query “create a CDN resource” triggers a search for cdn and create patterns, returning only the relevant tool schema rather than loading all tools.

Setting GCORE_TOOLS=* enables all available tools. This configuration is appropriate for Claude Code because schemas load only when needed. Other clients require tool filtering to avoid context window limits.