Gcore Cloud Mcp Server

MCP其他

提供方 G-Core

其他 未标注 OAuth 授权 社区 / 第三方 CursorCodexZed

Gcore MCP Server makes your AI assistant:

一句话选型结论

按资料字段整理

Gcore Cloud Mcp Server 属于其他类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Cursor、Codex、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

cloud management vps vm gpu

支持客户端

适用场景

cloudmanagementvps

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gcore Cloud Mcp Server当前 未标注 未标注 未标注 无 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方G-Core上游标注的维护方 G-Core
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.1 KB
来自项目仓库与上游目录的原文,未做删改

Gcore MCP Server

MCP (Model Context Protocol) server for Gcore API. This server provides tools for interacting with Gcore Cloud API via LLM assistants.

Usage

Note: As we have multiple resources available, providing all of them at once to most LLM clients can overwhelm the model and lead to confusion among the tools. For most clients, it is recommended to specify only the necessary resources for your task to ensure optimal performance and clarity. Some clients, like Claude Code, handle this differently — see below.

Integration with Cursor IDE

Add the server to your Cursor IDE configuration file (~/.cursor/mcp.json):```json
{
"mcpServers": {
"gcore-mcp-server": {
"command": "uvx",
"args": ["--from", "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git", "gcore-mcp-server"],
"env": {
"GCORE_API_KEY": "4**1",
"GCORE_TOOLS": "instances,management,cloud.gpu_baremetal.clusters.
"
}
}
}
}


### Integration with Claude Code

Add the server to your Claude Code configuration file (`~/.claude.json`):```json
{
  "mcpServers": {
    "gcore-mcp-server": {
      "command": "uvx",
      "args": ["--from", "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git", "gcore-mcp-server"],
      "env": {
        "GCORE_API_KEY": "4***1",
        "GCORE_TOOLS": "*"
      }
    }
  }
}

Setting GCORE_TOOLS=* loads all available tools, which works well with Claude Code thanks to its Tool Search feature. Unlike other clients, Claude Code defers tool schema loading — tool schemas are only fetched on demand when they match a query. This means registering many tools doesn't bloat the context window.

Claude Code shows a warning when tools exceed 10% of the context window. With deferred loading, this isn't an issue even with all tools enabled.

The uvx command runs the server in a temporary environment without requiring a persistent installation. See Running in a Temporary Environment for more details.

Note: You can find instructions on how to obtain a Gcore API Key here.

Optional variables:
- GCORE_BASE_URL: "https://api.gcore.com",
- GCORE_CLOUD_PROJECT_ID: "1",
- GCORE_CLOUD_REGION_ID: "76",
- GCORE_CLIENT_ID: "2",
- GCORE_ALLOWED_HOSTS: "" (HTTP transport only; loopback names always allowed)
- GCORE_ALLOWED_ORIGINS: "" (HTTP transport only)

HTTP transport security

The HTTP transport (GCORE_TRANSPORT=http) validates the Host and Origin
headers of every request, as required by the MCP Streamable HTTP specification.
This prevents a web page the operator visits from reaching a listener bound to
loopback via DNS rebinding.

  • GCORE_ALLOWED_HOSTS is a comma-separated list of additional host names,
    matched as glob patterns. Ports are ignored on both sides, so list host
    names only (mcp.internal, not mcp.internal:8000). The built-in names
    127.0.0.1, localhost and ::1, plus the concrete address the listener
    is bound to, are always accepted. Any other Host is rejected with
    421 Misdirected Request.
  • GCORE_ALLOWED_ORIGINS is a comma-separated list of additional browser
    origins, also glob-matched. On top of it FastMCP always accepts an Origin
    equal to the request's own origin, and any loopback origin when the Host
    is loopback — so another web app running on your machine is trusted, a
    DNS-rebound page on an attacker's domain is not. Any other Origin is
    rejected with 403. Requests without an Origin header (typical for
    non-browser MCP clients) are unaffected. Known FastMCP limitation: an
    IPv6 literal origin such as http://[::1]:3000 cannot be allow-listed,
    because the brackets are read as glob syntax.

Validation is FastMCP's host/origin guard in strict mode, which this server
turns on for the HTTP transport regardless of the bind address. Only the
gcore-mcp-server entry point applies this policy; loading the module's mcp
object through another runner (such as fastmcp run …:mcp) does not.

The legacy SSE transport is not supported and GCORE_TRANSPORT=sse refuses to
start: FastMCP does not apply this validation to its SSE app, so an SSE listener
would run without it.

The HTTP transport does not authenticate clients: anyone who can reach the
listener can call every enabled tool using the server's GCORE_API_KEY. Bind it
to loopback and do not expose it to an untrusted network.

Configuration

Tool Selection

The server uses a unified configuration approach via the GCORE_TOOLS environment variable. This single variable can contain a mix of predefined toolset names and custom patterns:```bash

Mixed toolsets and patterns

export GCORE_TOOLS="instances,management,cloud.gpu_baremetal.clusters.*,dns.records.create"

Only toolsets

export GCORE_TOOLS="instances,management"

Only patterns

export GCORE_TOOLS="cloud.,waap."

Default behavior (if not set)

Uses "management,instances" toolsets for HTTP mode, "management" for stdio


#### Configuration Modes

1. **Default Mode** (no configuration)
   - HTTP transport: Uses `management,instances` toolsets
   - stdio transport: Uses `management` toolset

2. **Toolset Mode** (predefined tool collections)
   - Use predefined toolset names: `instances`, `management`, `ai_ml`, etc.
   - Example: `GCORE_TOOLS="instances,management"`

3. **Pattern Mode** (custom tool filtering)
   - Use wildcard patterns to match tool names from the Gcore SDK
   - Exact matches: `cloud.instances.create`, `dns.records.delete`
   - Wildcard matches: `cloud.*`, `waap.*`, `cloud.gpu_baremetal.clusters.*`
   - Example: `GCORE_TOOLS="cloud.instances.*,waap.*"`

4. **Combined Mode** (toolsets + patterns)
   - Mix predefined toolsets with custom patterns
   - Toolset definitions have priority over pattern matches
   - Example: `GCORE_TOOLS="instances,cloud.gpu_baremetal.clusters.*"`

#### Available Toolsets

The system includes several predefined toolsets for 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`**: Networks, 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 registries
- **`cdn`**: CDN resources, origin groups, certificates, and cache management
- **`cleanup`**: Deletion and cleanup operations
- **`list`**: List/read-only operations

#### Pattern Syntax

Patterns support wildcard matching using `*`:

- **Exact matches**: `cloud.instances.create` matches only that specific method
- **Wildcard matches**: `cloud.instances.*` matches all instance methods
- **Broad wildcards**: `cloud.*` matches all cloud service methods
- **Service-specific**: `waap.*` matches all WAAP methods

#### Priority System

When using combined mode:
1. **Toolset tools** are included first (highest priority)
2. **Pattern-matched tools** are added second
3. **Duplicates are removed** while preserving order
4. Toolset definitions take precedence over pattern matches

#### Examples```bash
# Development: Get specific tools for testing
export GCORE_TOOLS="cloud.instances.create,cloud.instances.delete,cloud.volumes.create"

# Full cloud management
export GCORE_TOOLS="management,instances,storage,networking"

# GPU cluster operations with custom additions
export GCORE_TOOLS="gpu_baremetal,cloud.instances.create,waap.*"

# All services with wildcard
export GCORE_TOOLS="cloud.*,waap.*"

# Minimal setup
export GCORE_TOOLS="instances"

Running in a Temporary Environment (One-off Execution)

If you want to run the server without installing it persistently (e.g., for a quick test or a single use), you can use uvx. This command fetches the package, runs the specified script in a temporary environment, and then discards the environment.

To run the latest version from the main branch:```bash
uvx --from "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git" gcore-mcp-server


To run a specific version (e.g., `v0.1.1`):```bash
uvx --from "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git@v0.1.1" gcore-mcp-server

Remember to set any required environment variables (like GCORE_API_KEY, GCORE_TOOLS, etc.) before running the command.

Persistent Installation (Installing as a Tool)

For detailed installation instructions for uv, please refer to the official uv installation guide.

You can install gcore-mcp-server as a command-line tool using uv. This makes the command available globally in your terminal without needing to specify the source each time.

To install the latest version from the main branch:```bash
uv tool install "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git"


To install a specific version (e.g., `v0.1.0`):```bash
uv tool install "gcore-mcp-server@git+https://github.com/G-Core/gcore-mcp-server.git@v0.1.0"

After installation, uv will make the gcore-mcp-server command available. If it's not immediately found, you might need to run uv tool update-shell or ensure uv's tool bin directory is in your PATH.

Once installed, you can run it like any other command:```bash
gcore-mcp-server


## Development

### Local Development Setup```bash
# Clone the repository
git clone https://github.com//G-Core/gcore-mcp-server.git
cd gcore-mcp-server

# Install development dependencies
uv venv
source .venv/bin/activate
uv sync --dev

Debugging and Testing

For debugging and development, it's recommended to use the MCP Inspector:bash npx @modelcontextprotocol/inspector

The MCP Inspector provides a web interface to test and debug your MCP server interactively, allowing you to:
- Explore available tools and their schemas
- Test tool calls with different parameters
- View real-time communication between client and server
- Debug authentication and connection issues

To use it with your local development server:
1. Start your MCP server locally
2. Run the inspector and connect to your server
3. Use the web interface to test your tools

License

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Gcore Cloud Mcp Server 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Gcore Cloud Mcp Server 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Gcore Cloud Mcp Server 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gcore Cloud Mcp Server 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Gcore Cloud Mcp Server 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Gcore Cloud Mcp Server 能提供哪些能力?

资料显示能力标签包括 cloud、management、vps、vm、gpu。具体工具清单以官方文档为准。

Gcore Cloud Mcp Server 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。