How To Use Atlasly Inside Claude, ChatGPT, and Other AI Assistants

Use Atlasly’s connection page and the client’s current official instructions. The hosted URL is https://mcp.atlasly.app/mcp. This remote connection differs from installing a local desktop server.

The repository’s public server card currently lists 27 public tools and five account-linked operations. Those counts are a dated description, not a promise that your client exposes every tool or that every request succeeds. Inspect the discovered list, input requirements and access information.

Follow Claude’s custom remote connector guide. Add a custom connector from the supported connector settings, name it Atlasly and enter the hosted URL. Workspace permissions and the current client control availability.

After connecting, start a conversation with the connector enabled and ask a bounded question such as “Using Atlasly, review available flood evidence for this site and identify missing sources.” Check that an actual tool result and source links are returned. Do not assume a slash command is supported in every interface.

Use OpenAI’s developer-mode and MCP app guidance. The documented full MCP workflow is on ChatGPT web for eligible Business and Enterprise/Edu accounts with the appropriate permissions; the page distinguishes Pro read/fetch access. Do not equate this with a Custom GPT action or promise availability on every Plus account.

An authorised user creates the custom app, supplies the Atlasly endpoint and authentication configuration, scans the tools and tests the draft. Workspace publication and access follow the administrator’s controls. Follow the current official flow when labels change.

Public tools are intended to support an initial review without an Atlasly account, subject to request limits and service availability. Creating a project, running a site package, checking its job, generating a saved brief and enabling Site Watch are the account-linked operations listed in the server card.

Follow the offered authorisation flow when needed and inspect the requested permissions. Do not assume consent is permanent or that credentials can never expire. Client-plan eligibility, Atlasly account access and export entitlement are separate questions.

Ask for the source, date, boundary used and missing layers. Verify material planning and environmental conclusions against the underlying record. A successful connection does not establish nationwide completeness.

The public tool list does not establish direct CAD-file delivery in every chat. Where a response provides a link into Atlasly, check the available export format and entitlement in the app. Do not promise that a signed file appears in every answer or that AutoCAD opens automatically. Read the methodology and limits before relying on the evidence.