Atlantic's public MCP server gives AI assistants read-only access to Atlantic's public documentation and published knowledge. Results are quoted with a link to the source. No account is required. This page describes the server and how to configure supported assistants.
The server Coming
The server is in development for LightHouse™ 0.18.1 and is not yet deployed. Until then, the address below does not respond, and assistants can read the documentation site directly.
https://ask.atlanticagenticlabs.com/mcp
Transport
Streamable HTTP, as in the current MCP specification
Sign-in
Not required. No account, OAuth client or request headers are needed.
Access
Read-only access to Atlantic's published sources. The server has no access to client tenants.
Limits
Requests are rate-limited per caller and overall. A request over a limit receives HTTP 429 with a Retry-After header.
Recorded
Queries are retained for 12 months to improve the documentation. Email addresses, telephone numbers, keys and tokens are redacted before storage. IP addresses and other identifiers are not stored with queries. Do not include personal or confidential information in a query.
This server is separate from LightHouse's own MCP server, which reads a client's tenant and requires sign-in.
Tools
The server provides four read-only tools: two for search and two for reading pages. Each passage or page is returned verbatim, with a link to its source and the version or date of that source. The server does not call a language model. The assistant composes its reply from the returned content.
Tool
What it does
search_docs
Searches Atlantic's public documentation, including the LightHouse API's OpenAPI document and the MCP reference, and returns the best-matching passages
read_page
Returns one page of the public documentation in full, by its address
list_pages
Lists the pages of the public documentation, with their titles and addresses
search_published_knowledge
Searches the items Atlantic publishes on its knowledge pages and returns the best-matching passages
All four tools carry the MCP annotations readOnlyHint: true and openWorldHint: false. These annotations tell MCP clients that the tools do not write and do not access sources beyond Atlantic's published content.
Out of scope
No prices or commercial terms. Pricing, proposals and contracts are provided by the Atlantic team through Talk to us.
No commitments. Server responses do not constitute an offer, an undertaking or advice on Atlantic's behalf.
No contact on a person's behalf. The server does not send messages, make bookings or submit forms for Atlantic or for the person using the assistant.
No write access. The server has no write tools and no access to client data.
Setup Coming
Add the address to the assistant once the server is deployed. Each procedure follows the vendor's documentation as at 13 November 2026. Vendor menus change, and each procedure links the vendor's page.
Claude, on the web and in the desktop app
Go to Customize → Connectors, select Add, then Add custom connector.
Enter the name Atlantic and the server address, then select Continue.
Under Authentication, choose No sign-in, then select Add.
In a conversation, select +, then Connectors, and turn Atlantic on.
On a Team or Enterprise plan, an Owner adds it for the organisation under Organization settings → Connectors (Add, then Custom). The Free plan allows one custom connector.
Run MCP: Add Server from the Command Palette, choose HTTP (HTTP or Server-Sent Events), enter the server address and the name atlantic, then choose Global and Copilot Global. Or add it by file, to ~/.copilot/mcp-config.json for every workspace or .mcp.json at a workspace root:
Agent mode: the view switch at the top of every page shows that page as plain text, with this server's details first. Add ?mode=agent to a link to open a page that way.