code_review_architecture — Moretes Architect MCP MCP Tool
code_review_architecture
(code review architecture) is one of 48 tools on the
Moretes Architect MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call code_review_architecture from your client
- Claude Code Moretes Architect MCP code_review_architecture run in your project directory
- Claude Desktop Moretes Architect MCP code_review_architecture ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Moretes Architect MCP code_review_architecture ~/.cursor/mcp.json
- VS Code Moretes Architect MCP code_review_architecture .vscode/mcp.json
- Zed Moretes Architect MCP code_review_architecture ~/.config/zed/settings.json
- Windsurf Moretes Architect MCP code_review_architecture ~/.codeium/windsurf/mcp_config.json
- Cline Moretes Architect MCP code_review_architecture ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Moretes Architect MCP code_review_architecture ~/.gemini/settings.json
- Grok Moretes Architect MCP code_review_architecture .mcp.json (in your project root)
- ChatGPT Moretes Architect MCP code_review_architecture Settings → Connectors → Advanced → Developer mode
- Claude.ai Moretes Architect MCP code_review_architecture Settings → Connectors → Add custom connector
- LangChain Moretes Architect MCP code_review_architecture pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http moretes-aws-architect-mcp https://m9od37vm41.execute-api.us-east-1.amazonaws.com/mcpOther tools on this server
- architect_panel
- dependency_manifest_review
- requirements_check
- architecture_pattern
- service_compare
- decision_record
- well_architected_review
- threat_model
- failure_rehearsal
- capacity_plan
- cost_model
- slo_budget
- migration_plan
- architecture_diagram
- implementation_plan
- agent_tool_contract
- c4_model
- sequence_diagram
- service_equivalents
- data_classification
- openapi_review
- event_contract
- latency_budget
- queue_sizing
- dr_strategy
- retry_policy
- storage_growth
- finops_unit_economics
- postmortem
- runbook
- agent_eval_plan
- prompt_injection_checklist
- rag_pipeline_plan
- mcp_server_review
- mcp_config_review
- iam_policy_review
- cloudformation_review
- terraform_plan_review
- kubernetes_manifest_review
- aws_knowledge_search
- aws_knowledge_read
- aws_regions
- aws_regional_availability
- aws_skill
- integration_catalog
- integration_config
- github_public_repository
This list was read from the server itself, by connecting to it and calling tools/list on 25 October 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.