Skip to main content
Cursor IDE connects to Gcore MCP Server in dynamic mode. Leave GCORE_TOOLS unset. The client receives six tools and can reach every operation. Pattern rules for a narrower set are in Tool filtering.

Step 1. Add Gcore MCP Server to Cursor

Open the Cursor MCP configuration file:
Add the gcore-mcp-server entry to the mcpServers object. If the file is empty, create it with the full structure shown below.
Replace API_TOKEN with the Gcore API token. Setting GCORE_TOOLS without GCORE_MCP_MODE selects direct mode. A value that matches nothing exits with status 2. If the file already contains other MCP servers, add the gcore-mcp-server block inside the existing mcpServers object without removing other entries.

Step 2. Verify the connection

Restart Cursor to load the new configuration. Open Settings and navigate to Features → MCP. The gcore-mcp-server entry appears with a green indicator and lists the loaded tools.
If the server does not appear in MCP settings, verify that the mcp.json file has valid JSON syntax. A missing comma or bracket prevents loading. Check that uv is installed (uv --version). Quit Cursor and open it again. Reloading the window does not load the server.

Step 3. Test with a query

Open a Cursor chat and ask:
A successful response lists DNS zones with the zone name, record count, and status:
If tools are not available in chat, confirm the GCORE_API_KEY value has no extra spaces or quotes, and verify the token is active in the Gcore Customer Portal. Requests returning “401 Unauthorized” indicate an invalid or expired token. Required roles are in API token permissions.