Skip to main content
Glama
Houlong66

MNS MCP Manager

by Houlong66
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MNS_ENDPOINTYesYour Alibaba Cloud MNS endpoint
MNS_ACCESS_KEY_IDYesYour Alibaba Cloud MNS access key ID
MNS_ACCESS_KEY_SECRETYesYour Alibaba Cloud MNS access key secret

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
create_mns_queueC
创建一个 MNS 队列。

Args:
    queue_name (str): 队列名称。

Returns:
    str: 创建结果信息。
delete_queueB
删除 MNS 队列。

Args:
    queue_name (str): 队列名称。

Returns:
    str: 删除结果信息。
send_messageB
发送消息到指定队列。

Args:
    queue_name (str): 队列名称。
    message_body (str): 消息内容。

Returns:
    str: 发送结果信息。
receive_and_delete_messagesA
接收并删除队列中的消息。

Args:
    queue_name (str): 队列名称。
    wait_seconds (int): 长轮询等待时间（秒）。

Returns:
    List[str]: 收到的消息列表。
list_queuesA
获取给定前缀的所有队列。如果未提供前缀，则列出所有队列。

Args:
    prefix (str): 队列名称的前缀，默认为空字符串。

Returns:
    List[str]: 包含队列信息的列表，每条信息格式为 "QueueName: <name>, QueueURL: <url>"。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool clearly targets a distinct operation: create, delete, list, send, and receive/delete. There is no overlapping functionality or ambiguity in purpose.

Naming Consistency3/5

Names generally follow a verb_noun pattern, but there are inconsistencies: 'create_mns_queue' includes 'mns' while 'delete_queue' and 'list_queues' do not, and 'receive_and_delete_messages' is a compound verb phrase. Still, the overall style is readable and predictable.

Tool Count5/5

With 5 tools, the set is well-scoped for core MNS queue management. Each tool serves a necessary function without redundancy or bloat.

Completeness4/5

The set covers the essential lifecycle: create, list, delete, send, and receive/delete messages. Missing operations like queue attribute management or purging are minor gaps that agents can typically work around.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources