Coreshub MCP Server

mcp server for coreshub: https://coreshub.cn/. Exposed over MCP by the coreshub mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

class MyTool(BaseTool): tool_name = "my_tool" tool_description = "我的自定义工具"

Its toolset

Everything the assistant can do here goes through one of these:

• zone — type: string
• description — 区域标识，从上下文获取，选项：xb3,xb2,hb2
• default — xb3
• required — True
• owner — type: string
• user_id — type: string
• resource_id — type: string
• limit — type: integer
• offset — type: integer
• name — type: string
• namespace — type: string
• uuid — type: string

Configuration

You will need 3 environment variables: QY_ACCESS_KEY_ID, QY_SECRET_ACCESS_KEY, CORESHUB_USER_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Coreshub's toolset — zone, description, default and 11 more — is a fair guide to whether it matches your workflow. It is maintained by coreshub; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Coreshub's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Coreshub.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the coreshub mcp server does with a few real requests.