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