Skip to main content
Gcore MCP Server exposes six tools by default and can reach every operation through them. GCORE_TOOLS limits that set. GCORE_MCP_MODE=direct with the same variable registers one tool per matched operation instead. Patterns are SDK paths, comma-separated. A value that matches nothing stops the server before it accepts connections. Check a pattern with no API key:
The command prints the matching operations and a count out of 818.

Dynamic mode

With GCORE_TOOLS and GCORE_MCP_MODE both unset, the client receives search_tools, get_tool_schema, call_read_tool, call_write_tool, call_destructive_tool, and execute_code. The server log reports dynamic mode, 818 operations, and six MCP tools. GCORE_CODE_EXECUTION=false removes execute_code and leaves the other five. GCORE_TOOLS in dynamic mode limits which operations search and calls can reach. GCORE_TOOLS=dns.zones,not-a-real-toolset logs a warning for the unknown pattern and starts with the operations under dns.zones (23 operations in that run). GCORE_MCP_MODE=direct without GCORE_TOOLS logs a warning and starts in dynamic mode.

Direct mode

Set both variables:
The client receives one tool per matched operation. The tool name replaces dots with underscores, so cloud.instances.list is cloud_instances_list. Project and region tools are included even when the pattern does not name them: cloud_projects_get, cloud_projects_list, cloud_regions_get, and cloud_regions_list. The cloud.instances pattern registered 40 tools. GCORE_TOOLS=* in direct mode registers all 818 operations. GCORE_TOOLS set without GCORE_MCP_MODE selects direct mode. The startup log says so. A value that matches nothing then stops the process and serves no tools. These names exit that way: instances, management, and management,instances.

Patterns

A name with no wildcard matches that operation and the operations under it. dns.zones matches 19 operations, including dns.zones.list and dns.zones.rrsets.delete. * matches any characters, dots included. cloud.*.delete* matches 74 operations, including cloud.instances.delete and cloud.instances.delete_and_poll. Several patterns go in one value, separated by commas: GCORE_TOOLS=cdn.*,dns.*.

Deny list

GCORE_DENY_TOOLS uses the same patterns. A denied operation disappears from search_tools and is not registered in direct mode. GCORE_DENY_TOOLS=dns.zones.delete removed dns.zones.delete from a search for “delete dns zone”. GCORE_DENY_TOOLS=cloud.instances.delete removed both cloud_instances_delete and cloud_instances_delete_and_poll from the direct-mode list (40 tools down to 38). A deny pattern that matches nothing logs a warning and blocks nothing. The server still starts.
A GCORE_TOOLS value that matches nothing exits with status 2. Run gcore-mcp-server --list on the pattern before adding it to a client configuration.