Skip to main content
Gcore MCP Server runs from uv and reads its settings from environment variables. Client configuration is in Connect Claude Code and Connect Cursor IDE. Install uv Gcore MCP Server runs via uvx, which is part of the uv package manager.
Verify the installation:
Create a Gcore API token Create an API token with permissions matching the products to be used. Required roles per product are in API token permissions.
The API token is displayed once and cannot be retrieved later. Store it securely and do not commit it to version control.

Install the server

uvx runs the server in a temporary environment without installing it permanently. The AI client handles this automatically using the uvx command in its configuration. No manual step is needed.To verify the server starts correctly, run it directly:
Pin a specific version by appending the tag:
If the AI client shows “Failed to connect to MCP server”, verify that uv is installed (uv --version) and test the uvx command directly from the terminal. A missing comma or bracket in the config file also prevents loading.

Environment variables

The server starts in dynamic mode when GCORE_TOOLS and GCORE_MCP_MODE are unset. Pattern syntax is in Tool filtering.
Requests that return “401 Unauthorized” indicate an invalid or expired API token. Verify the token in the Gcore Customer Portal and check that it has permissions for the requested product.

Project and region

cloud.instances.list with project_id and region_id omitted returns _scope.project for the account default project. The response note says every active region was searched, and each item includes region_id. The schema for project_id says the default project is used except for destructive operations. The schema for region_id says list operations search every region and other operations need a region. GCORE_CLOUD_PROJECT_ID and GCORE_CLOUD_REGION_ID are optional. Add them to the client env block only to pin calls:
Find the IDs by asking the client to list projects and regions, or from the URL at Cloud > Projects in the Gcore Customer Portal.

Read-only mode and approval

GCORE_READ_ONLY=true rejects writes. In direct mode the write and destructive tools are absent. In dynamic mode the client receives search_tools, get_tool_schema, call_read_tool, and execute_code. A write passed to call_read_tool returns an error that the server is in read-only mode. GCORE_TRANSPORT=http starts read-only and logs that GCORE_READ_ONLY=false is required to allow changes. The session URL is http://127.0.0.1:<port>/mcp. GET /sse returns 404. GCORE_CONFIRM=destructive is the default. dns.zones.delete returns CONFIRMATION REQUIRED and the text “This call was NOT executed.” Repeating the call is what sends it. cloud.instances.create and dns.zones.create do not set requires_confirmation. writes asks before every change. none does not ask.
Requests that return “429 Too Many Requests” are rate limited. Retry after the Retry-After interval when the response includes that header.