# MCP Server Management

Use when admin asks to configure an MCP tool server (e.g., GitHub, weather API), rotate...

- Repository: https://github.com/agentscope-ai/AgentTeams (5913 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add agentscope-ai/AgentTeams --skill mcp-server-management -g -a claude-code -y`
Codex: `npx skills add agentscope-ai/AgentTeams --skill mcp-server-management -g -a codex -y`
Cursor: `npx skills add agentscope-ai/AgentTeams --skill mcp-server-management -g -a cursor -y`
Gemini CLI: `npx skills add agentscope-ai/AgentTeams --skill mcp-server-management -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

- **Self-hosted Console in another container:** set `HIGRESS_CONSOLE_URL` (or `AGENTTEAMS_HIGRESS_CONSOLE_URL`) to its reachable address. You can reuse `HIGRESS_COOKIE_FILE` or let the scripts log in with `AGENTTEAMS_ADMIN_USER` / `AGENTTEAMS_ADMIN_PASSWORD`. If Controller-local Worker credentials are unavailable, the scripts save your Worker MCP assignments through `agt apply`; wait for reconciliation and file-sync before verifying tools.
- **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

The rest: https://github.com/agentscope-ai/AgentTeams/blob/HEAD/manager/agent/skills/mcp-server-management/SKILL.md