Skip to main content
Glama
goofun

volcengine-mcp-server

by goofun

Volcengine MCP Server

中文文档

MCP Server for the Volcengine services.

Tools

Supply OpenAPI from Volcengine as MCP Tools.

Related MCP server: VoIPbin MCP Server

Setup

  1. Get your AccessKey from Volcengine

Integrate Volcengine Services with Claude or other Agents using NodeJS

Add the following to your config.json:

{
  "mcpServers": {
    "volcengine": {
      "command": "npx",
      "args": ["-y", "volcengine-mcp-server"],
      "env": {
        "VOLC_SERVICE": "<use which service>",
        "VOLC_VERSION": "<use which version of service>",
        "VOLC_ACTION": "<use which action of version>",
        "VOLC_ACCESSKEY": "<your access key>",
        "VOLC_SECRETKEY": "<your secret key>"
      }
    }
  }
}

Example for IAM service

{
  "mcpServers": {
    "volcengine-iam": {
      "command": "npx",
      "args": ["-y", "volcengine-mcp-server"],
      "env": {
        "VOLC_SERVICE": "iam",
        "VOLC_VERSION": "2018-01-01",
        "VOLC_ACTION": "GetUser,ListUsers",
        "VOLC_ACCESSKEY": "<your access key>",
        "VOLC_SECRETKEY": "<your secret key>"
      }
    }
  }
}

Available Tools

1 tool
iam/2018-01-01/ListUsersC

获取IAM用户列表。

ParametersJSON Schema
NameRequiredDescriptionDefault
QueryNo模糊查询。可按用户名、显示名或备注查询。
OffsetNo分页起始索引,默认为0。
LimitNo分页条数,默认为10。

TDQS

C2.4/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states the basic purpose. It does not disclose any behavioral traits such as read-only nature, pagination behavior, or response characteristics. No value is added beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise but lacks necessary detail. It is under-specified for a tool with three parameters and no output schema, failing to front-load critical usage information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is incomplete. No output schema exists, and the description does not explain list behavior, pagination, or any limitations. It fails to provide sufficient context for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage for three parameters, so the baseline is 3. The description does not add any additional meaning beyond what the schema provides, so a score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states '获取IAM用户列表' which clearly indicates the tool retrieves a list of IAM users. It is a specific verb and resource. However, there are no sibling tools to differentiate, so it does not achieve the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool or how it compares to alternatives. The description lacks any context for selection, and no sibling tools are mentioned to indicate differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observediam/2018-01-01/ListUsers

TDQS

C2.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap with other tools.

Naming Consistency5/5

A single tool inherently follows a consistent pattern; the name format is unique but not inconsistent.

Tool Count2/5

The server provides only one tool, which is insufficient for the apparent scope of IAM user management, falling into the too-few category.

Completeness2/5

The tool set is severely incomplete, offering only a list operation with no create, update, or delete capabilities, which will cause agent failures for most IAM tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • F
    license
    A
    quality
    F
    maintenance
    MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
    5
    3
    -
  • A
    license
    B
    quality
    C
    maintenance
    An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
    52
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/goofun/volcengine-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server