mcp-server-management

スター5,176

フォーク615

更新日2026年7月25日 05:54

Use when admin asks to configure an MCP tool server (e.g., GitHub, weather API), rotate credentials, grant/revoke worker access to MCP tools, or add a custom API integration via YAML.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

agentscope-ai

agentscope-ai/AgentTeams

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

MCP Server Management

MCP Servers expose REST APIs as tools on the Higress AI Gateway, or proxy existing MCP servers (SSE/StreamableHTTP). Use setup-mcp-server.sh to create/update from YAML templates, or setup-mcp-proxy.sh to proxy existing MCP servers. Built-in templates are at references/mcp-*.yaml.

Gotchas

Cloud mode (AGENTTEAMS_RUNTIME=aliyun) does not support script-based MCP management — direct admin to the Alibaba Cloud AI Gateway console instead
Auth plugin takes ~10s to activate after server creation/update — always wait and verify with mcporter before notifying Workers
Always verify end-to-end before notifying Workers — call at least one tool via mcporter to confirm connectivity. Do not push broken tools
Never echo credentials in chat messages — credentials are stored only in Higress config, Workers access via gateway proxy
Consumer authorization is a REPLACE operation — when calling the API manually, include ALL consumers (manager + all workers), not just the new one
All YAML configs must use accessToken: "" as the credential key — the setup script substitutes the real value
Only notify relevant Workers — do not broadcast to all Workers, only those whose role/task needs the new tool
MCP Server SSE endpoint always returns 200 — auth is checked on POST /mcp/<name>/message, not on SSE connect
mcp-proxy only supports http and sse transport — stdio servers cannot be proxied through the gateway

Operation Reference

Read the relevant doc before executing. Do not load all of them.

Situation	Read
Create/update an MCP server or rotate credentials	`references/create-update-server.md`
Generate YAML for a custom API integration	`references/custom-yaml-guide.md`
List, inspect, delete servers, or manage consumer access manually	`references/api-commands.md`
Proxy an existing MCP server (SSE/HTTP)	`references/setup-mcp-proxy.md`
Need the GitHub MCP tool definitions	`references/mcp-github.yaml`

このリポジトリの他の Skills

同じリポジトリ

coding-cli-management

agentscope-ai/AgentTeams

Execute AI coding CLI tools (Claude Code / Gemini CLI / qodercli) on behalf of Workers. Use when a Worker sends a coding-request: message, asking Manager to run coding operations in their workspace.

2026-07-255.2k

channel-management

agentscope-ai/AgentTeams

Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.

2026-07-255.2k

human-management

agentscope-ai/AgentTeams

Use when admin requests adding a human user to the system, changing human permissions, removing human access, or managing human accounts.

2026-07-255.2k

service-publishing

agentscope-ai/AgentTeams

Expose worker HTTP services via Higress gateway. Use when admin asks to publish a worker's web app or API to make it externally accessible.

2026-07-255.2k

task-management

agentscope-ai/AgentTeams

Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.

2026-07-255.2k

team-management

agentscope-ai/AgentTeams

Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.

2026-07-255.2k

MCP Server Management

Gotchas

Cloud mode (AGENTTEAMS_RUNTIME=aliyun) does not support script-based MCP management — direct admin to the Alibaba Cloud AI Gateway console instead

Auth plugin takes ~10s to activate after server creation/update — always wait and verify with mcporter before notifying Workers

Always verify end-to-end before notifying Workers — call at least one tool via mcporter to confirm connectivity. Do not push broken tools

Never echo credentials in chat messages — credentials are stored only in Higress config, Workers access via gateway proxy

Consumer authorization is a REPLACE operation — when calling the API manually, include ALL consumers (manager + all workers), not just the new one

All YAML configs must use accessToken: "" as the credential key — the setup script substitutes the real value

Only notify relevant Workers — do not broadcast to all Workers, only those whose role/task needs the new tool

MCP Server SSE endpoint always returns 200 — auth is checked on POST /mcp/<name>/message, not on SSE connect

mcp-proxy only supports http and sse transport — stdio servers cannot be proxied through the gateway

Operation Reference

Read the relevant doc before executing. Do not load all of them.

Situation

Read

Create/update an MCP server or rotate credentials

references/create-update-server.md

Generate YAML for a custom API integration

references/custom-yaml-guide.md

List, inspect, delete servers, or manage consumer access manually

references/api-commands.md

Proxy an existing MCP server (SSE/HTTP)

references/setup-mcp-proxy.md

Need the GitHub MCP tool definitions

references/mcp-github.yaml

name	mcp-server-management
description	Use when admin asks to configure an MCP tool server (e.g., GitHub, weather API), rotate credentials, grant/revoke worker access to MCP tools, or add a custom API integration via YAML.