compare_design_options — Atlasly MCP Tool
compare_design_options
(compare design options) is one of 43 tools on the
Atlasly
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compare_design_options from your client
- Claude Code Atlasly compare_design_options run in your project directory
- Claude Desktop Atlasly compare_design_options ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Atlasly compare_design_options ~/.cursor/mcp.json
- VS Code Atlasly compare_design_options .vscode/mcp.json
- Zed Atlasly compare_design_options ~/.config/zed/settings.json
- Windsurf Atlasly compare_design_options ~/.codeium/windsurf/mcp_config.json
- Cline Atlasly compare_design_options ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Atlasly compare_design_options ~/.gemini/settings.json
- Grok Atlasly compare_design_options .mcp.json (in your project root)
- ChatGPT Atlasly compare_design_options Settings → Connectors → Advanced → Developer mode
- Claude.ai Atlasly compare_design_options Settings → Connectors → Add custom connector
- LangChain Atlasly compare_design_options pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http atlasly https://mcp.atlasly.app/mcpOther tools on this server
- view_geojson_file
- search_development_mentions
- open_atlasly_workspace
- get_location_coverage
- inspect_research_source
- prepare_site_research
- present_site_research
- export_site_boundary
- export_site_context
- search_tools
- get_lpa_adapter_status
- site_verdict
- compare_sites
- boundary_doctor
- analyze_site
- check_planning_constraints
- check_permitted_development
- prepare_biodiversity_review
- get_local_plan_policies
- estimate_planning_costs
- find_development_sites
- prepare_sequential_review
- prepare_heritage_review
- assess_planning_readiness
- draft_site_description
- generate_site_map
- prepare_building_regulations_review
- get_flood_risk
- get_planning_history
- find_precedents
- search_aec_knowledge
- plan_site_intelligence
- get_map_layer_plan
- get_official_source_adapters
- get_point_elevation
- get_nearby_mapped_places
- list_developments
- create_project_from_site
- run_site_package
- get_job_status
- generate_site_brief
- enable_site_watch
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.