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