メニュー
Call MCP Server tools directly via the mcporter CLI. Use when you need to interact with external APIs (GitHub, weather, etc.) without delegating to a Worker — useful for quick lookups or when you need a result to make a decision.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/agentscope-ai/AgentTeams --skill mcporterコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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.
SOC 職業分類に基づく
SKILL.md を表示中
| name | mcporter |
| description | Call MCP Server tools directly via the mcporter CLI. Use when you need to interact with external APIs (GitHub, weather, etc.) without delegating to a Worker — useful for quick lookups or when you need a result to make a decision. |
You can call any configured MCP server's tools directly via mcporter. Your config is at ./config/mcporter.json (mcporter's default path — no --config flag needed, auto-generated by the setup-mcp-server.sh script).
# 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}'
When you're unsure what tools are available or what parameters a tool expects:
mcporter list to see all servers and tool countsmcporter list <server-name> --schema to see each tool's description, argument types, and which are required vs optionalsetup-mcp-server.shFor sustained or complex API interactions, delegate to a Worker instead — they have their own mcporter skill and can work autonomously.