Skip to main content
Glama
jeweis

jewei-mcp-nacos

by jeweis

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NACOS_HOSTNoNacos server address (Nacos 服务地址)localhost
NACOS_API_PORTNoAPI port used for login (API 端口,用于登录)8848
NACOS_PASSWORDNoPassword for authentication (密码)
NACOS_USERNAMENoUsername for authentication (用户名)
NACOS_NAMESPACENoDefault namespace ID (默认命名空间 ID)public
NACOS_READ_ONLYNoRead-only mode, disables publishing functions (只读模式,禁用发布功能)false
NACOS_CONSOLE_PORTNoConsole port used for configuration operations (Console 端口,用于配置操作)8080

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
nacos_get_configB

获取 Nacos 配置内容。

从 Nacos 配置中心获取指定的配置内容。

参数:
    params: 包含以下内容的验证输入参数:
        - data_id: 配置 ID
        - group_name: 配置分组,默认 DEFAULT_GROUP
        - namespace_id: 命名空间 ID,可选
        - response_format: 输出格式,markdown 或 json

返回:
    配置内容(Markdown 或 JSON 格式)
nacos_publish_configA

发布 Nacos 配置。

    创建新配置或更新已有配置。

    参数:
        params: 包含以下内容的验证输入参数:
            - data_id: 配置 ID
            - group_name: 配置分组,默认 DEFAULT_GROUP
            - namespace_id: 命名空间 ID,可选
            - content: 配置内容
            - config_type: 配置类型,默认 yaml
            - desc: 配置描述,可选

    返回:
        发布结果
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves configuration content from Nacos, while the other publishes/updates configuration. There is no overlap in functionality, and the descriptions clearly differentiate between read and write operations.

Naming Consistency5/5

Both tools follow a consistent naming pattern: 'nacos_' prefix followed by verb_noun (get_config, publish_config). This pattern is uniform across all tools, making them easily identifiable and predictable.

Tool Count2/5

With only two tools, this server feels severely under-scoped for managing a configuration system like Nacos. Essential operations like listing configurations, deleting configurations, or monitoring changes are missing, making the toolset incomplete for typical configuration management workflows.

Completeness2/5

The toolset covers basic get and publish operations but lacks critical CRUD/lifecycle coverage for a configuration management system. There are no tools for listing available configurations, deleting configurations, or handling configuration versioning, which are standard needs in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues