developer.code-change-review — API Acre MCP Tool
developer.code-change-review
(developer code change review) is one of 73 tools on the
API Acre
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call developer.code-change-review from your client
- Claude Code API Acre developer.code-change-review run in your project directory
- Claude Desktop API Acre developer.code-change-review ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor API Acre developer.code-change-review ~/.cursor/mcp.json
- VS Code API Acre developer.code-change-review .vscode/mcp.json
- Zed API Acre developer.code-change-review ~/.config/zed/settings.json
- Windsurf API Acre developer.code-change-review ~/.codeium/windsurf/mcp_config.json
- Cline API Acre developer.code-change-review ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI API Acre developer.code-change-review ~/.gemini/settings.json
- Grok API Acre developer.code-change-review .mcp.json (in your project root)
- ChatGPT API Acre developer.code-change-review Settings → Connectors → Advanced → Developer mode
- Claude.ai API Acre developer.code-change-review Settings → Connectors → Add custom connector
- LangChain API Acre developer.code-change-review pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api-acre https://apiacre.com/mcp
Other tools on this server
- web.extract
- web.metadata
- web.seo-audit
- web.security-audit
- web.accessibility-audit
- web.performance-profile
- web.links
- web.robots-sitemap
- web.tech-fingerprint
- web.email-auth
- web.domain-intelligence
- web.full-audit
- web.business-due-diligence
- commerce.product-price
- research.lei-entity-search
- document.extract
- document.tables
- document.redact
- document.diff
- data.profile
- data.clean
- data.convert
- data.json-repair
- data.schema
- data.schema-validate
- data.contract
- data.schemaorg-normalize
- data.deduplicate
- developer.x402-preflight
- developer.openapi-audit
- developer.dependency-audit
- developer.license-audit
- developer.secret-scan
- developer.code-metrics
- developer.sql-change-review
- developer.structured-diff
- research.feed-normalize
- research.news-aggregate
- developer.openapi-test-generate
- research.us-contract-search
- research.federal-register-search
- research.ofac-entity-search
- research.organization-evidence
- data.vin-decode
- data.worldbank-snapshot
- research.sec-filing-signals
- research.sec-insider-transactions
- research.sec-financial-facts
- research.sec-company-evidence
- research.crossref-work-search
- research.crossref-doi-metadata
- research.wikidata-organization-search
- data.ecb-fx-reference
- data.place-geocode
- data.reverse-geocode
- data.us-address-geocode
- data.current-weather
- data.us-weather-forecast
- data.timezone-convert
- crypto.address-inspect
- crypto.base-account-snapshot
- crypto.base-account-status
- crypto.base-usdc-transfers
- crypto.base-event-logs
- crypto.base-gas-estimate
- crypto.base-network-status
- crypto.base-block-inspect
- crypto.base-contract-inspect
- crypto.base-contract-read
- crypto.base-transaction-inspect
- crypto.calldata-decode
- crypto.typed-data-hash
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.