Gcore MCP Server enables AI assistants to manage Gcore services through natural language commands. The server implements the Model Context Protocol (MCP), exposing Gcore API operations as callable tools used to provision infrastructure, query resources, and chain multi-step workflows.Documentation Index
Fetch the complete documentation index at: https://gcore.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Supported products
| Product | Description |
|---|---|
| CDN | Content Delivery Network resources, origins, caching rules |
| Cloud | Virtual machines, bare metal, GPU clusters, networking |
| DNS | DNS zones and records |
| FastEdge | Edge computing applications |
| IAM | Users, roles, permissions |
| Security | SSL certificates, secrets management |
| Storage | S3-compatible object storage |
| Streaming | Live and VOD video streaming |
| WAAP | Web application and API protection |
Supported AI clients
| Client | Compatibility | Notes |
|---|---|---|
| Claude Code | Full | Recommended due to tool search capability |
| Cursor IDE | Limited | Maximum 40-50 tools before context issues |
| MCP Inspector | Full | Web-based interface for testing and exploration |
GCORE_TOOLS environment variable to reduce the number of exposed tools.
How it works
Requests are written in plain language—no fixed commands or syntax required. The AI client reads the available tool names and descriptions, matches them to the request, calls the appropriate tool, and returns the result in a readable format. Requests can be written in any language. For multi-step operations, the server chains tool calls automatically. A request like “Create a VM with a standard configuration” triggers the server to look up available regions, flavors, and images, present a summary for confirmation, and then provision the instance.
Get started
To set up Gcore MCP Server:- Install and configure Gcore MCP Server — set up the server with Claude Code or Cursor IDE
- Test tools with MCP Inspector — explore available tools in a browser interface
- Filter tools with GCORE_TOOLS — limit exposed tools for specific workflows
A Gcore API token with appropriate permissions is required. See API token permissions for guidance on required roles.
API token permissions
The API token must have permissions matching the tools being used. Gcore uses role-based access control:| Tool category | Required role |
|---|---|
cdn.* | CDN Viewer (read) or CDN Editor (read/write) |
cloud.* | Cloud Viewer or Cloud Editor |
dns.* | DNS Viewer or DNS Editor |
fastedge.* | FastEdge Viewer or FastEdge Editor |
storage.* | Storage Viewer or Storage Editor |
streaming.* | Streaming Viewer or Streaming Editor |
waap.* | WAAP Viewer or WAAP Editor |
iam.* | Account Administrator |