菜单
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/agentscope-ai/AgentTeams --skill mcporter命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when a Leader maintains durable TeamHarness project state for Quick Task or Project Work: create_quick_project, create_project, plan_dag, plan_loop, ready_nodes, resolve_project, accept_task_result, project completion, and requester report state. Do not use to create Matrix task rooms or send messages.
Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use agentteams-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.
Use for standalone Matrix admin requests (register users, create rooms, manage membership, upload files). Also use when you need to send a file to the admin via Matrix media upload. Do NOT use for Worker/project creation — those handle Matrix operations internally.
正在显示 SKILL.md
基于 SOC 职业分类
| name | mcporter |
| description | Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers. |
You call MCP Server tools via mcporter. Your config is at /home/openhuman/.openhuman/config/mcporter.json (mcporter's default path — no --config flag needed).
# List all configured MCP servers and their tool counts
mcporter list
# View a specific server's tools with full parameter schemas
mcporter list <server-name> --schema
# Call a tool — key=value syntax for simple args
mcporter call <server-name>.<tool-name> key=value key2=value2
# Call a tool — JSON syntax for complex args (arrays, objects, numbers)
mcporter call <server-name>.<tool-name> --args '{"key":"value","count":5}'
Output is JSON — parse with jq when needed.
When your coordinator @mentions you saying a new MCP server has been configured, follow this workflow:
Run your file-sync skill to pull the latest files from MinIO.
# Verify the new server appears
mcporter list
# Get full tool schemas — read carefully to understand each tool
mcporter list <server-name> --schema
After understanding the tools, create a skill directory and SKILL.md so you have a permanent reference:
mkdir -p /home/openhuman/.openhuman/skills/<server-short-name>-operations
Then write /home/openhuman/.openhuman/skills/<server-short-name>-operations/SKILL.md with:
name, description, assign_whenmcporter call command, and parameter notesAfter generating the skill, reply to your coordinator confirming:
mcporter command is not found, install it: npm install -g mcporter/home/openhuman/.openhuman/config/mcporter.json doesn't exist yet, use your file-sync skill first — your coordinator pushes the config to MinIO after setting up MCP servers