ワンクリックでManusで任意のスキルを実行

mcp-server-management

スター1

フォーク0

更新日2026年7月14日 02:09

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 ページを確認してインストールできます。

Manusで実行

ソース

Stars1233

Stars1233/hiclaw

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

ダウンロード

Manusで実行

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

同じリポジトリ

hiclaw-migrate

Stars1233/hiclaw

Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into HiClaw as a managed Worker

2026-07-171

file-sharing

Stars1233/hiclaw

Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.

2026-07-141

find-skills

Stars1233/hiclaw

Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.

2026-07-141

organization

Stars1233/hiclaw

Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.

2026-07-141

file-sync

Stars1233/hiclaw

Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).

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.