release_review_task — co.build MCP Tool
release_review_task
(release review task) is one of 23 tools on the
co.build
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call release_review_task from your client
- Claude Code co.build release_review_task run in your project directory
- Claude Desktop co.build release_review_task ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor co.build release_review_task ~/.cursor/mcp.json
- VS Code co.build release_review_task .vscode/mcp.json
- Zed co.build release_review_task ~/.config/zed/settings.json
- Windsurf co.build release_review_task ~/.codeium/windsurf/mcp_config.json
- Cline co.build release_review_task ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI co.build release_review_task ~/.gemini/settings.json
- Grok co.build release_review_task .mcp.json (in your project root)
- ChatGPT co.build release_review_task Settings → Connectors → Advanced → Developer mode
- Claude.ai co.build release_review_task Settings → Connectors → Add custom connector
- LangChain co.build release_review_task pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cobuild https://co.build/mcp
Other tools on this server
- prepare_installation_report
- publish_installation_report
- prepare_feedback
- publish_feedback
- get_review_task
- submit_review
- report_review_usage
- submit_install_check
- get_my_devices
- get_my_installations
- withdraw_installation_report
- schedule_installation_followup
- cancel_installation_followup
- get_installation_stats
- search
- get_top_mods
- fetch
- get_device
- get_mod
- get_feedback
- prepare_report_link
- compare_mods
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.