bots.st/atlasly
Atlasly
UK planning evidence and site context research; export bound
2772 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 43
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.atlasly.app/mcp
What it can do
| Tool | What it says it does |
|---|---|
analyze_site | Purpose: prepare a limited first site read. When to use: use for an initial resolved England address before selecting further evidence tools. Returns: reported flood point evidence, a bounded national application sample with explicit decision text, conditional point elevation and source gaps… |
assess_planning_readiness | Purpose: check planning evidence readiness for a proposal at a resolved England location. When to use: prepare proposal evidence and identify decision references to verify before policy and design appraisal. Returns: bounded national-source sample, explicit source state, dated point-checked… |
boundary_doctor | Purpose: check a user-supplied red-line boundary before treating it as the site geometry. When to use: run after receiving a GeoJSON Polygon or MultiPolygon, especially before Site Verdict or focused constraint checks. Returns: closure, CRS, coordinate-range, topology, vertex-limit, and area… |
check_permitted_development | Purpose: prepare an England permitted-development evidence checklist, tentative class hint and restriction samples, without confirming a legal route. When to use: use for architect questions like "is this rear extension PD?", "can I convert this Class E shop to flats?", or "does Article 4 affect… |
check_planning_constraints | Check first-pass UK planning constraints at a site: flood zone, listed buildings, World Heritage Sites, registered parks and gardens, scheduled monuments, registered battlefields, archaeological priority areas, conservation areas, Article 4 Directions, Tree Preservation Orders, environmental… |
compare_design_options | Read the connected user's active saved Canvas options for one owned development. Use project_id from list_developments. Omit option_ids to choose available options; supply exactly two different IDs to compare immutable captured versions. Recomputes early design quantities from saved geometry and… |
compare_sites | Purpose: compare exactly two UK sites for the same intended use and stage using the existing Site Verdict evidence. When to use: use after appraising one or two candidate sites, or when an architect/developer needs a shortlist decision that colleagues can review. Returns: both canonical site_ref… |
create_project_from_site | Create an Atlasly project for the resolved site so work can continue inside the full product. Preserves the country and location provenance for plugin reopen. User-supplied coordinates remain unverified with unknown planning jurisdiction; saving does not verify the site, save export files or an… |
draft_site_description | Purpose: draft grounded site description, constraints, accessibility, planning history, and policy-context sections for a Design & Access Statement or feasibility note using Atlasly source-backed tool outputs. When to use: use when the user asks for D&A site context, planning statement background… |
enable_site_watch | Purpose: save enabled Site Watch settings for an owned Atlasly development after the user explicitly requests monitoring. Requires a connected account with atlasly.site_watch.write permission. Inputs: project_id from list_developments, optional checks, weekly/monthly frequency and radius in… |
estimate_planning_costs | Purpose: estimate England planning application fees, CIL coverage/liability status, and likely S106 heads for early feasibility and viability checks. When to use: use when a user asks for planning fees, CIL, S106, planning obligations, or rough pre-application cost exposure; use… |
export_site_boundary | Purpose: validate and export a supplied WGS84 boundary as GeoJSON or SVG. When to use: when the user provides a Polygon, MultiPolygon or Feature and wants a portable boundary file. Returns: actual file contents, filename, MIME type, geometry checks and limitations; the workspace supports… |
export_site_context | Purpose: retrieve source geometry and prepare a portable site-context file. When to use: when the user wants OpenStreetMap buildings, roads, water, green space and land use worldwide or available UK flood/heritage geometry around a location for QGIS, Rhino or CAD. Returns: actual GeoJSON, SVG or… |
find_development_sites | Purpose: find and rank official English brownfield-register development-site candidates for an area, then enrich the shortlist with Atlasly flood, heritage, conservation-area, and transit checks where requested. When to use: use for site-selection briefs like "find brownfield residential sites in… |
find_precedents | Purpose: retrieve explicitly decided records from a bounded national planning-application sample for a resolved England site. When to use: to locate application references for manual decision and policy verification. Returns: known approved/refused/withdrawn sample records, source state, nullable… |
generate_site_brief | Generate a structured site brief from Atlasly project memory and conversation context. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context. |
generate_site_map | Purpose: compose multiple Atlasly source-backed site layers into one shareable map URL for feasibility reports, client decks, and planning context review. When to use: use when the user wants a single map with flood, heritage, planning history, transport, constraints, or precedent layers; use… |
get_flood_risk | Purpose: retrieve reported flood point evidence with source-state and coverage limits. When to use: first-pass flood evidence before authority/site-specific review. Returns: UK reported zone/native SEPA likelihood and gaps; US native FEMA context if configured. Limitations: no whole-site/access… |
get_job_status | Poll the status of an async Atlasly job (e.g. site package run). Returns current status, progress, and result summary when complete. Poll every 10–30 seconds until status is complete or failed. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the… |
get_local_plan_policies | Purpose: review stored England local policy extract leads for a resolved authority. When to use: early planning statement research, with source links where available. Returns: a bounded extract sample, unknown adoption/currentness/applicability and a current national framework link. Missing… |
get_location_coverage | Check registered context/place routes and selected official research references for a supplied global WGS84 point and country before choosing a task. No geocoding, dataset retrieval or source health probe. Separates community geometry, configuration and document references from unassessed local… |
get_lpa_adapter_status | Purpose: inspect Atlasly top-LPA planning source adapter coverage, operational status, cache state, record counts, and geometry coverage. When to use: use when inspecting local-adapter registrations and reported operational state. Development-site application cells and planning evidence readiness… |
get_map_layer_plan | Return structured map actions, source-backed evidence layers, missing layers, citations, coverage status, and warnings for Atlasly site-intelligence map customization requests. This plans layers and draws nothing: use generate_site_map for a rendered map image and open_atlasly_workspace for the… |
get_nearby_mapped_places | Purpose: find mapped nearby schools, shops and services worldwide. When to use: compare local place context around a known site, or prepare mapped points for QGIS. Returns: selected OpenStreetMap point categories from fixed regional sources, straight-line distances in metres, per-layer coverage… |
get_official_source_adapters | List Atlasly registered official-source adapters for USA/EU/global site intelligence. Use to inspect source endpoint readiness, token requirements, and health-check queue instructions before relying on unsupported-location research. Omit every filter to list all registered adapters. For UK local… |
get_planning_history | Purpose: retrieve a bounded national planning-application sample for a resolved England site. When to use: for first-pass record research with direct local-portal verification. Returns: references, source decision text, known/unknown outcomes, nullable dates, source-point proximity, source state… |
get_point_elevation | Purpose: read one contextual elevation worldwide from Copernicus GLO-30 surface data, or an operator-configured Open Topo Data-compatible service. When to use: when a user asks about elevation at a known worldwide point. Returns: finite point elevation in metres, provider-declared dataset, nominal… |
inspect_research_source | Purpose: independently retrieve a supported official publishing page and compare an optional literal quotation. When to use: check a cited source passage after conversation research. Returns: bounded plain-text excerpt, retrieval time, document hash, publisher and quotation match state. Parameter… |
list_developments | Purpose: list the connected user's saved Atlasly developments. When to use: only when the user asks to reopen or choose their saved work. Returns: up to 20 owned project names, addresses, coordinates and portable site_ref handles. Limitations: not a complete project history, options/revisions or… |
open_atlasly_workspace | Purpose: open Atlasly's interactive maps and site workspace. When to use: when the user wants to explore Atlasly tasks or open its workspace; call the specific evidence tool directly for a specific question. Returns: a task chooser with site checks, maps, comparisons, supplied-boundary export, 2D… |
plan_site_intelligence | Resolve a site into a structured data-source route: which Atlas warehouse datasets apply, which official sources are verified for this jurisdiction, which categories have coverage gaps, and what research fallback applies for uncovered categories. Use before making planning analysis claims to… |
prepare_biodiversity_review | Purpose: prepare an England biodiversity evidence checklist from supplied site area and habitat labels. When to use: identify missing surveys and metric inputs before a BNG review. Returns: supplied inputs, missing information and null metric values. Limitations: does not calculate statutory… |
prepare_building_regulations_review | Purpose: prepare an England building-control review checklist without determining applicable requirements or compliance. When to use: use during feasibility/RIBA Stage 1-2 for fire, structure, ventilation, energy, access, overheating and BSR review questions. Returns: unassessed review_topics… |
prepare_heritage_review | Purpose: review a bounded source inventory of listed buildings and conservation areas. When to use: prepare heritage evidence and identify gaps before a proposal-specific assessment. Returns: named source records, published grades, point distances where available, source states and unresolved… |
prepare_sequential_review | Purpose: prepare an England sequential-test evidence checklist and bounded candidate-register sample without determining a requirement, exemption or outcome. When to use: for flood sequential/exception questions and authority-review preparation. Returns: subject point evidence, source… |
prepare_site_research | Purpose: prepare a site-bound research request for the current conversation. When to use: when a user asks to research a global site question. Returns: a reviewable request and reusable site_ref, with no researched findings. Limitations: does not search the web or access account history; search… |
present_site_research | Purpose: present cited site research. When to use: after prepare_site_research and the host's own search, or to show unavailable search and gaps. Returns: Atlas AI UI, a JSON evidence register and a self-contained printable HTML pack. The HTML can be printed to PDF by the receiving browser; no… |
run_site_package | Purpose: request a background Atlasly site package for a resolved site. When to use: only after the user explicitly asks to start a package and connects an account with atlasly.site_package.run permission. Inputs: address, optional search radius in metres and an optional existing project_id… |
search_aec_knowledge | Search the Atlasly AEC knowledge graph: official data source registry, jurisdiction planning frameworks, technical standards, calculation tools, and domain records. kind=sources returns official datasets by jurisdiction. kind=jurisdictions returns policy frameworks (NPPF, NPF4, PPW, etc.)… |
search_development_mentions | Search up to 20 owned development names for explicit composer selection. Requires the existing projects permission; not complete history or document search. |
search_tools | Discover available Atlasly tools by keyword. Call this first when unsure which tool to use. Returns tool names, one-line summaries, and required parameters. To search standards, policy frameworks or official datasets, use search_aec_knowledge instead. Chaining: every response returns site_ref… |
site_verdict | Purpose: produce the one-call Atlasly hero appraisal for a known UK site. When to use: use first for acquisition, feasibility, concept, or planning-stage questions that need a clear Proceed, Investigate, or Stop screen rather than separate lookups. Returns: potential dealbreakers, design-changing… |
view_geojson_file | Open a user-selected .geojson file read-only in Atlas AI. Host resource access required; bounded WGS84 geometry, no source fetch, legal parcel verification or file edits. |
In its maker's words
UK site research and worldwide CAD/GIS site context (DXF, GeoJSON, SVG) for architects
- Website
- atlasly.app/mcp
- Publisher
- atlasly.app
- Listed from
- the official MCP Registry as
app.atlasly/atlasly - Version
- 0.3.0, updated 29 Oct 2026
- Kinds of work
- Law, tax and government, Search and research, Domains and websites
The domain it lives on
- atlasly.app
- registered 28 Oct 2025 (1 year ago), at GoDaddy.com, LLC, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2772 ms | |
| Answered | 2636 ms | |
| Answered | 1666 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.