gcore-mcp-server

Gcore MCP Server is the official MCP (Model Context Protocol) server provided by Gcore, used to allow LLM assistants to interact with the Gcore Cloud API through tool calls.

Purpose

This server wraps the Gcore Cloud API as MCP tools, enabling MCP-compatible LLM clients (such as Cursor IDE and Claude Code) to directly operate Gcore cloud resources, such as managing virtual machines, networks, storage, AI clusters, and more.

Main Capabilities

The server provides multiple predefined tool sets covering common workflows:

• management: core account and project management
• instances: virtual machine operations
• baremetal: bare metal server operations
• gpu_baremetal: GPU bare metal cluster management
• gpu_virtual: GPU virtual cluster management
• networking: networking, floating IPs, load balancers
• security: security groups, SSH keys, secrets
• storage: volumes, file shares
• ai: AI clusters
• ai_ml: AI/ML inference services
• billing: cost reports and billing information
• containers: container registry
• cdn: CDN resources, origin groups, certificates, and cache management
• cleanup: delete and cleanup operations
• list: list/read-only operations

Tool selection is uniformly configured through the GCORE_TOOLS environment variable and supports three modes:

1. Tool set mode: use predefined tool set names, such as GCORE_TOOLS="instances,management".
2. Pattern matching mode: use wildcards to match tool names in the Gcore SDK, supporting exact matching (such as cloud.instances.create) and wildcard matching (such as cloud., waap.).
3. Combined mode: mix tool sets and patterns, with tool set definitions taking precedence over pattern matching.

By default, HTTP transport uses the management,instances tool sets, and stdio transport uses the management tool set.

Usage

Integration with Cursor IDE

Add the server to the Cursor IDE configuration file (~/.cursor/mcp.json).

Integration with Claude Code

Add the server to the Claude Code configuration file (~/.claude.json). Setting GCORE_TOOLS=* loads all tools, and Claude Code's Tool Search feature will delay loading tool schemas to avoid context bloat.

Temporary Run

Use the uvx command to run the server in a temporary environment without a persistent installation. For example, run the latest version of the main branch or a specified version (such as v0.1.1). Before running, set the necessary environment variables (such as GCORE_API_KEY, GCORE_TOOLS, etc.).

Persistent Installation

Use uv to install gcore-mcp-server as a command-line tool. After installation, the command is available globally. If the command is not found, run uv tool update-shell or ensure that uv's tool bin directory is in PATH.

Local Development and Debugging

MCP Inspector is recommended for debugging and testing. It provides a web interface to explore available tools and their schemas, test tool calls, view real-time communication, and debug authentication and connection issues.

Configuration Variables

Required: GCORE_API_KEY (see the official instructions for how to obtain it). Optional:

• GCORE_BASE_URL: default "https://api.gcore.com"
• GCORE_CLOUD_PROJECT_ID: default "1"
• GCORE_CLOUD_REGION_ID: default "76"
• GCORE_CLIENT_ID: default "2"
• GCORE_ALLOWED_HOSTS: HTTP transport only, comma-separated list of hostnames, supports glob patterns
• GCORE_ALLOWED_ORIGINS: HTTP transport only, comma-separated list of browser origins, supports glob patterns

Use cases

Suitable for developers and operations personnel who need to manage Gcore cloud resources through an LLM assistant, especially in scenarios where cloud operation workflows are integrated in Cursor IDE or Claude Code.

Limitations

• Providing all resources may overload some LLM clients; it is recommended to specify only the necessary resources.
• The HTTP transport does not authenticate clients. Anyone who can access the listener can use the server's GCORE_API_KEY to call all enabled tools. It should be bound to the loopback address and not exposed to untrusted networks.
• The HTTP transport validates the Host and Origin headers to prevent DNS rebinding attacks.
• The legacy SSE transport is not supported; GCORE_TRANSPORT=sse will refuse to start.
• Known FastMCP limitation: IPv6 literal origins (such as http://[::1]:3000）无法加入允许列表。
• The HTTP transport security policy is applied only at the gcore-mcp-server entry point; the mcp object loaded through other runners does not apply it.