Volcengine MCP Servers
The official collection of Volcengine cloud MCP servers: each service gets its own server for the agent, from ECS to billing
- 333 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Access keys open control of real cloud resources, including servers and databases
- The billing, IAM and certificate servers work with credentials and rights of the whole account
- Some tools start, renew or change paid resources
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/volcengine-mcp-serversDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Access keys open control of real cloud resources, including servers and databases
- The billing, IAM and certificate servers work with credentials and rights of the whole account
- Some tools start, renew or change paid resources
This is third-party code. Review the repository files before installing.
What it does
The Volcengine repository holds dozens of separate MCP servers for the Volcengine cloud, each in its own server/mcp_server_<name> folder. The core is compute, storage and databases: ECS, TOS object storage, RDS MySQL, Redis, MongoDB. There are servers for containers and monitoring (VKE, VMP, APMPlus), the TLS log service, networking and CDN. Separate servers handle access, billing and certificates. ECS shows how the servers are built. Its tools mostly read: lists of instances and images, system events, console data. The actions available are starting and renewing an instance. The server's author deliberately kept only frequent queries so that extra output does not weigh on the model's context, and the other servers are built the same way. A server runs through uv or uvx, in stdio mode by default, and the `-t streamable-http` flag turns on HTTP. Cloud access comes from environment variables with keys and a region. Next to them sits a simple client in app/general_client that shows how to connect to one server.
Who it is for. For developers and administrators whose resources live in the Volcengine cloud and who manage them from Cursor, Trae, Claude Desktop or Cline.
Good fit when
- You want the state of cloud servers, images and system events without opening the Volcengine console
- You want to dig into logs and metrics via TLS, VMP or APMPlus by asking in words
- You want to manage Volcengine Redis, MongoDB or MySQL databases through requests to an agent
- You want to check spending or access rights in IAM and billing
- You want a ready Python server skeleton: each server's code is open and shows how to wrap a cloud API as MCP
Not a fit when
- Your infrastructure is not in the Volcengine cloud: the servers talk only to its API with its keys
- You want a single server without sorting through dozens of folders: you have to pick one and run it separately
- You need Russian or English documentation for every server
- You cannot hand the agent keys with write rights in the cloud
Example request
List my ECS instances in the cn-beijing region and tell me which ones have unacknowledged system events.MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
VOLCENGINE_ACCESS_KEYrequired, secret- Volcengine account access key
VOLCENGINE_SECRET_KEYrequired, secret- Volcengine account secret key
VOLCENGINE_REGIONrequired- Volcengine resource region
VOLCENGINE_ENDPOINT- Volcengine endpoint
MCP_SERVER_PORT- HTTP mode port, 8000 by default
Limitations
A Volcengine account with the services enabled and access keys is required. Each server has its own requirements, usually Python 3.12 and the uv manager, and its own environment variables: ECS settings do not carry over to other servers unchecked.
Many servers act on paid resources: they start, renew and change settings. The agent's rights equal those of the keys you give it, so start with a separate read-only user. The overall list includes third-party servers with other authors and licenses.
The availability of the Volcengine cloud and its documentation from Russia was not checked. The repository license is MIT.
How to disable. Remove the server's entry from the MCP client settings and stop the process. Revoke the access key you issued for the agent in the Volcengine console so it does not stay active.
FAQ
How do I run the ECS server from Volcengine MCP Servers?
Install uv and add a block to the client settings with the command uvx, the arguments `--from mcp-server-ecs>=0.2.0` and mcp-server-ecs, and three variables: key, secret and region. For a local run from a clone, execute `uv run mcp-server-ecs` in server/mcp_server_ecs.
Which clients do the servers work with?
The support list in the repository names Volcengine Ark, Trae, Cursor and Python. The servers suit other MCP clients too, such as Claude Desktop and Cline, if they can launch stdio servers or connect over HTTP.
How do I turn on HTTP instead of stdio?
Add the `-t streamable-http` flag to the launch command. The port comes from MCP_SERVER_PORT, 8000 by default.
Which environment variables does cloud access need?
VOLCENGINE_ACCESS_KEY and VOLCENGINE_SECRET_KEY for the keys, VOLCENGINE_REGION for the region and, when needed, VOLCENGINE_ENDPOINT for the address. Other servers may add their own variables, listed in each one's documentation.
Are all the servers from the list in this repository?
No. Some entries in the list point to third-party projects such as Sequential Thinking, Puppeteer, Browserbase, Docker and Spotify. Volcengine's own servers are in the server folder of this repository.
Discussion
No questions or reviews yet.
Related
MCP serversOfficial Cloudflare MCP server: the agent drives the whole Cloudflare API by searching the spec and running code
The remote MCP server of Devopness, a platform that builds infrastructure and deploys apps in your own cloud accounts
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
VK Cloud MCP server
VK Cloud MCP Server
An unofficial VK Cloud MCP server: virtual machines, networks, disks and SSH keys via the OpenStack-compatible API
A self-hosted gateway that merges several MCP servers into one endpoint with auth and tool selection
A Node.js manager for MCP servers: it starts local servers, connects remote ones and gives a client one address, with a REST API for control
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Volcengine MCP Servers (this entry) | yes | API key | 333 | |
| VK Cloud MCP server | no | API key | 1 | an unofficial server for one Russian cloud, while Volcengine publishes a collection of official servers for its Chinese cloud |
| selectel-mcp | no | API key | 1 | an unofficial server for the Selectel cloud, while here are dozens of official servers for separate Volcengine services |
README in short
The main page describes the Volcengine MCP marketplace, where getting from picking a server to installing it in a client takes five steps. The server list by category and links to the MCP protocol follow.