humanmirror_outcome — HumanMirror Outcome MCP Tool
humanmirror_outcome
(humanmirror outcome) is one of 1 tool on the
HumanMirror Outcome
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call humanmirror_outcome from your client
- Claude Code HumanMirror Outcome humanmirror_outcome run in your project directory
- Claude Desktop HumanMirror Outcome humanmirror_outcome ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HumanMirror Outcome humanmirror_outcome ~/.cursor/mcp.json
- VS Code HumanMirror Outcome humanmirror_outcome .vscode/mcp.json
- Zed HumanMirror Outcome humanmirror_outcome ~/.config/zed/settings.json
- Windsurf HumanMirror Outcome humanmirror_outcome ~/.codeium/windsurf/mcp_config.json
- Cline HumanMirror Outcome humanmirror_outcome ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HumanMirror Outcome humanmirror_outcome ~/.gemini/settings.json
- Grok HumanMirror Outcome humanmirror_outcome .mcp.json (in your project root)
- ChatGPT HumanMirror Outcome humanmirror_outcome Settings → Connectors → Advanced → Developer mode
- Claude.ai HumanMirror Outcome humanmirror_outcome Settings → Connectors → Add custom connector
- LangChain HumanMirror Outcome humanmirror_outcome pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http outcome https://humanmirror.fr/api/outcome/mcp/
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.