report_review_usage — co.build MCP Tool
report_review_usage
(report review usage) 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 report_review_usage from your client
- Claude Code co.build report_review_usage run in your project directory
- Claude Desktop co.build report_review_usage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor co.build report_review_usage ~/.cursor/mcp.json
- VS Code co.build report_review_usage .vscode/mcp.json
- Zed co.build report_review_usage ~/.config/zed/settings.json
- Windsurf co.build report_review_usage ~/.codeium/windsurf/mcp_config.json
- Cline co.build report_review_usage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI co.build report_review_usage ~/.gemini/settings.json
- Grok co.build report_review_usage .mcp.json (in your project root)
- ChatGPT co.build report_review_usage Settings → Connectors → Advanced → Developer mode
- Claude.ai co.build report_review_usage Settings → Connectors → Add custom connector
- LangChain co.build report_review_usage 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
- release_review_task
- 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.