Skip to main content

Connect Claude Desktop to Atlas

note

This is for the Claude Desktop app. For the CLI, see Claude Code →. Claude.ai in a browser is not supported — MCP requires a local app.


Step 1: Install Node.js

Node.js is required. Download the LTS installer at nodejs.org and run it.

Verify it worked — open Terminal (Mac) or Command Prompt (Windows) and run:

node --version

You should see a version number like v22.3.0. If you just installed Node, restart your computer before continuing.


Step 2: Get your Graphite Atlas access token

Generate your API key →

Keep your token private. Don't paste it into a chat or share it in a screenshot.


Step 3: Open the config file

In Claude Desktop:

Claude menu > Settings > Developer > Edit Config

This opens the config file and creates it if it doesn't exist yet.

Can't find it?
  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Step 4: Add the Graphite Atlas block

This is the step that trips people up

The config file must be one JSON object: exactly one { at the very top, one } at the very bottom, and nothing after it. The most common mistake is pasting a second { ... } block at the end of the file. If you do, Claude won't start and you'll see:

Could not load app settings: Unexpected non-whitespace character after JSON

If you get that error, you have two top-level blocks. Merge them into one using the examples below.

If the file is empty (or just {}), replace everything with:

{
"mcpServers": {
"graphite-atlas": {
"command": "npx",
"args": ["-y", "@graphite-atlas/mcp-server"],
"env": {
"GRAPHITE_ACCESS_TOKEN": "your-token-here",
"GRAPHITE_API_URL": "https://graphiteatlas.com"
}
}
}
}

If the file has other content but no mcpServers, add "mcpServers" as a sibling key inside the existing object. There must be exactly one { at the top and one } at the bottom — never paste a second block at the end.

Before:

{
"preferences": {
"theme": "dark"
}
}

After:

{
"preferences": {
"theme": "dark"
},
"mcpServers": {
"graphite-atlas": {
"command": "npx",
"args": ["-y", "@graphite-atlas/mcp-server"],
"env": {
"GRAPHITE_ACCESS_TOKEN": "your-token-here",
"GRAPHITE_API_URL": "https://graphiteatlas.com"
}
}
}
}

If the file already has an mcpServers block (you've set up other MCP servers before), do NOT add a second mcpServers. Add "graphite-atlas" as a new key inside the existing mcpServers, alongside whatever's already there.

Before:

{
"mcpServers": {
"some-other-server": {
"command": "npx",
"args": ["-y", "@someone/their-server"]
}
}
}

After:

{
"mcpServers": {
"some-other-server": {
"command": "npx",
"args": ["-y", "@someone/their-server"]
},
"graphite-atlas": {
"command": "npx",
"args": ["-y", "@graphite-atlas/mcp-server"],
"env": {
"GRAPHITE_ACCESS_TOKEN": "your-token-here",
"GRAPHITE_API_URL": "https://graphiteatlas.com"
}
}
}
}

Note the comma after the first server's closing } — each server inside mcpServers is separated by a comma, with no comma after the last one.

Save when done.


Step 5: Fully quit Claude and reopen

Closing the window is not enough — the config only loads on a full restart.

  • Mac: Claude menu > Quit Claude (or Cmd+Q)
  • Windows: system tray icon (bottom-right) > Quit

Then reopen Claude Desktop.


Step 6: Verify

In a new conversation, type:

List my atlases

Claude should respond with the atlases in your Graphite Atlas account.

Things to try
  • "What's in my atlas?"
  • "Show me all the processes"
  • "Who is responsible for the monthly close?"
  • "Create a new atlas called Test and add three people to it"

Troubleshooting

Full troubleshooting guide →