English Français العربية

Atlas

Official registry Marketing and sales

Atlas is a YAML-defined semantic layer for analytics — authored by humans, consumed by AI agents.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @useatlas/mcp
Claude Code 
claude mcp add atlas -e 'ATLAS_DATASOURCE_URL=<your atlas_datasource_url>' -e 'ATLAS_PROVIDER=<ATLAS_PROVIDER>' -e 'ATLAS_API_URL=<ATLAS_API_URL>' -- npx -y @useatlas/mcp@0.0.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "atlas": {
            "command": "npx",
            "args": [
                "-y",
                "@useatlas/mcp@0.0.2"
            ],
            "env": {
                "ATLAS_DATASOURCE_URL": "<your atlas_datasource_url>",
                "ATLAS_PROVIDER": "<ATLAS_PROVIDER>",
                "ATLAS_API_URL": "<ATLAS_API_URL>"
            }
        }
    }
}

Environment variables

  • ATLAS_DATASOURCE_URL secret Analytics datasource URL (postgres, mysql, clickhouse, snowflake, duckdb, bigquery, salesforce). Optional — falls back to a bundled NovaMart SQLite demo when unset.
  • ATLAS_PROVIDER LLM provider: anthropic, openai, bedrock, ollama, openai-compatible, gateway. Optional — the MCP server does not call an LLM directly (the client does); set this only if you also run Atlas's chat or scheduler.
  • ATLAS_API_URL URL of a running Atlas API. Optional — defaults to http://localhost:3001. When set, the MCP server inherits the API's connections, semantic layer, and governance.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Atlas
  2. How it works
  3. Run it
  4. Where everything else went
  5. Acknowledgments
  6. License

Atlas

Atlas is the company facts your AI agents can trust: every one carries its source, its date, and the name of the person who approved it. Open source, runs in your VPC.

The hosted service is shut down. I ran Atlas as a hosted service at useatlas.dev until September 2026 and have now turned it off, along with the hosted demo and docs.useatlas.dev. Atlas continues as open source: everything below runs on your own machine or in your own VPC. The docs live in apps/docs/content.

Point Claude Desktop, Cursor or Continue at a local Atlas with one command. With no datasource configured it uses the bundled NovaMart demo data:

bunx @useatlas/mcp init --local --write

Restart the client and ask it a question about NovaMart's orders. (Claude Code, VS Code and other clients: the same command with --client generic prints a block to paste. On WSL2, write bun x instead of bunx.)

How it works

Three kinds of thing live in the Atlas, and every answer says which it is drawing on:

  1. Surveyed — read straight from your company's own data through a semantic layer you author. True by construction: the query re-reads live rows, nobody interpreted anything, and it cannot go stale between readings. SELECT-only, single statement, table-whitelisted, validated seven ways before it runs.
  2. Attested — extracted from something someone wrote, then approved by a named person in your company. That person is on the record, and the fact carries its source and its date.
  3. On the record — the raw source material itself, unedited. Trustworthy as testimony, not as fact.

Surveyed outranks Attested wherever they overlap, so a recollection never overwrites the data. Nothing becomes Attested without a person approving it, and there is no setting that turns that off. Contradictions are shown with both claims and both sources; Atlas does not pick a winner. Where nobody has surveyed, the coverage page says so instead of guessing.

Run it

  • Self-hosted — the complete Atlas under AGPL, in your VPC, free; Docker, Railway or Vercel. Self-host quick start.
  • From your AI agent — bunx @useatlas/mcp init --local against a local Atlas, or bunx @useatlas/mcp init --hosted --api-url <your Atlas> against a self-hosted one with managed auth. MCP guide.

Where everything else went

This README used to inventory the whole product. Each section now lives on one docs page, in the docs source:

Acknowledgments

Atlas was inspired by Abhi Sivasailam's work on Vercel's internal data agent d0 and the open-source vercel-labs/oss-data-analyst template. The core insight — invest in a rich semantic layer, trust the model, and keep the tool surface minimal — came from that work.

License

The server and core packages are AGPL-3.0: if you modify the server and serve it to users, you share those modifications. The client libraries (@useatlas/sdk, @useatlas/react, @useatlas/types, @useatlas/plugin-sdk, @useatlas/mcp) and all plugins are MIT. The ee/ directory is source-available under a commercial license; nothing that makes the Atlas work is behind it — only governance, convenience and scale. Full inventory: Enterprise boundary.

Frequently asked questions

What is Atlas?

Atlas is a YAML-defined semantic layer for analytics — authored by humans, consumed by AI agents.

How do I install Atlas?

It runs on your machine. In Claude Code: claude mcp add atlas -e 'ATLAS_DATASOURCE_URL=<your atlas_datasource_url>' -e 'ATLAS_PROVIDER=<ATLAS_PROVIDER>' -e 'ATLAS_API_URL=<ATLAS_API_URL>' -- npx -y @useatlas/mcp@0.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Atlas need an API key?

Yes. It expects ATLAS_DATASOURCE_URL, which you set in its configuration.

Is Atlas open source?

Yes. Its code is on GitHub under the AGPL-3.0 license.

Who maintains Atlas?

It is published by AtlasDevHQ. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.