List your agent

Atlasly

MCP server · hosted · v0.3.0 · app.atlasly/atlasly
Online · tested 2h agoNEW · 4h agoSeen in the registry 3h ago

UK site research and worldwide CAD/GIS site context (DXF, GeoJSON, SVG) for architects

What it does

Atlasly is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.3.0
PriceNot in the registry
First seen29 Oct 2026
Last checked3h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

  • https://mcp.atlasly.app/mcp streamable-http

In Claude Code: claude mcp add --transport http atlasly https://mcp.atlasly.app/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "atlasly": {
      "url": "https://mcp.atlasly.app/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE Atlasly answered an MCP connection on 29 Oct 2026 and introduced itself as atlasly-mcp 0.3.0 (MCP protocol 2025-06-18).

35 tools offered to AI assistants

  • 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.
  • 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 sit
  • 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, conf
  • 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, docu
  • 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: do
  • present_site_research · Purpose: present cited site research. When to use: after conversation research, 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
  • 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, geometr
  • 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
  • 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. Chaining: every response returns site_ref; pass it unchanged into another Atlasly t
  • 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. Developme
  • 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
  • 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
Show 23 more
  • 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
  • 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 decisi
  • 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
  • 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
  • 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 metr
  • 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/applicabi
  • 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 r
  • 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-se
  • 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 prepara
  • 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 di
  • 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
  • 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
  • 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 hist
  • 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 BS
  • 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 c
  • 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 outcom
  • 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
  • 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
  • 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 categ
  • 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. Chaining: every response returns site_ref; pass it unchanged in
  • 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. Chainin
  • 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 poi
  • 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

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.atlasly.app/mcpDECLAREDSRC-001 Official MCP Registry3h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry3h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry3h ago
Websitehttps://atlasly.app/mcpDECLAREDSRC-001 Official MCP Registry3h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry3h ago
Version0.3.0DECLAREDSRC-001 Official MCP Registry3h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry3h ago

Change history

  • NEW29 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Atlasly? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor AtlaslyLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Atlasly?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedInListed on Electra Index
<a href="https://electraindex.com/mcp/atlasly?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/atlasly" alt="Listed on Electra Index"></a>

Questions about Atlasly

How do I connect Atlasly?

Use the hosted endpoint https://mcp.atlasly.app/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does Atlasly offer?

When Electra Index connected on 29 Oct 2026, it listed 35 tools: view_geojson_file, open_atlasly_workspace, get_location_coverage, inspect_research_source, prepare_site_research, present_site_research, export_site_boundary, export_site_context and more. The full list is in "Live check" above.

Is Atlasly online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.