メニュー
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.
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.
Use before filesync calls for project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files. Do not use for task-level sync; taskflow delegate_task and check_task handle task directory sync internally.
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).
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.
Use when you are invited to a Project Room or assigned a task within a multi-worker project. Covers project plan reading, task coordination with other Workers, and git author config.
Use when executing a task (progress logging, plan updates), when resuming a task after session reset, or when managing task history. Covers progress log format, task-history.json, and resume flow.
| 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