outcome_run — HumanMirror Nexus MCP Tool
outcome_run
(outcome run) is one of 6 tools on the
HumanMirror Nexus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call outcome_run from your client
- Claude Code HumanMirror Nexus outcome_run run in your project directory
- Claude Desktop HumanMirror Nexus outcome_run ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HumanMirror Nexus outcome_run ~/.cursor/mcp.json
- VS Code HumanMirror Nexus outcome_run .vscode/mcp.json
- Zed HumanMirror Nexus outcome_run ~/.config/zed/settings.json
- Windsurf HumanMirror Nexus outcome_run ~/.codeium/windsurf/mcp_config.json
- Cline HumanMirror Nexus outcome_run ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HumanMirror Nexus outcome_run ~/.gemini/settings.json
- Grok HumanMirror Nexus outcome_run .mcp.json (in your project root)
- ChatGPT HumanMirror Nexus outcome_run Settings → Connectors → Advanced → Developer mode
- Claude.ai HumanMirror Nexus outcome_run Settings → Connectors → Add custom connector
- LangChain HumanMirror Nexus outcome_run pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nexus https://humanmirror.fr/api/nexus/mcp/Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.