log_outcome — Audifact MCP Tool
log_outcome
(log outcome) is one of 5 tools on the
Audifact
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call log_outcome from your client
- Claude Code Audifact log_outcome run in your project directory
- Claude Desktop Audifact log_outcome ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Audifact log_outcome ~/.cursor/mcp.json
- VS Code Audifact log_outcome .vscode/mcp.json
- Zed Audifact log_outcome ~/.config/zed/settings.json
- Windsurf Audifact log_outcome ~/.codeium/windsurf/mcp_config.json
- Cline Audifact log_outcome ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Audifact log_outcome ~/.gemini/settings.json
- Grok Audifact log_outcome .mcp.json (in your project root)
- ChatGPT Audifact log_outcome Settings → Connectors → Advanced → Developer mode
- Claude.ai Audifact log_outcome Settings → Connectors → Add custom connector
- LangChain Audifact log_outcome pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http audifact https://api.audifact.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 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.