← Connect your AI

Claude Code

Add Project Desk to Claude Code so the same agent can read and update your desk while it works. Project Desk does not change Claude Code's filesystem, command, or approval settings.

Your connector URL

https://atlier.ai/mcp

OAuth 2.1 — sign in with GitHub, Google, or Microsoft Desk-scoped Standard MCP (streamable HTTP)

Steps (Claude Code app)

Click your account name (bottom-left) and choose Settings.
In Settings, open Connectors (under Customize in the left rail).
Click Add → Add custom connector.
Name it ProjectDesk, paste the connector URL above into Remote MCP server URL, leave the OAuth fields blank, and click Add.
The new connector shows "not connected yet" — click Connect.
Sign in to claude.ai if asked, then choose your Project Desk sign-in — GitHub, Google, or Microsoft, the same account you use for the desk.
Approve the Authorize access to your desk screen — click Allow access.
Use the tool-permission settings you prefer in Claude Code.
Done. Ask Claude Code to connect the repositories available in its workspace, read their existing setup, and recommend the next step before changing anything.

Menu not where you expect it, or on an older build? Skip straight to the terminal command below — it does the same thing.

Prefer the terminal?

The same connector, added from any shell:

claude mcp add --transport http projectdesk https://atlier.ai/mcp

Add --scope user to make it available in every project. Then inside Claude Code run /mcp, select projectdesk, and choose Authenticate.

Good to know

Project Desk honors the authenticated desk and membership boundaries; Claude Code continues to honor the local settings you chose.
The same account signs in everywhere — Claude Code, claude.ai, and the desk in your browser all see one desk.
Also use Claude Desktop or claude.ai? See Claude setup.

If your tools disappear

Sometimes an AI app loses its connection to Project Desk mid-session and the desk tools stop showing up. Your desk and your data are safe — this is the app's local connection, not your account. Recover in order, easiest first:

Start a new chat or thread in your AI app. The lost connection is usually scoped to one conversation, so a fresh one often brings the tools right back — no restart needed.
Fully quit and relaunch the app — quit it completely, not just the window — then reconnect.
If reconnecting never asks you to sign in again (the app acts connected but the tools never appear), it is likely holding a stale sign-in. Do not add a second connector under a different name — that makes it worse. Instead: open Project Desk → Settings → Sessions & connected agents, click Disconnect next to that agent, then remove and re-add the connector in your app using the same name and the exact URL https://atlier.ai/mcp. That triggers a fresh sign-in attempt; if it still doesn't prompt, fully quit and relaunch the app.

Always reconnect the exact same endpoint — https://atlier.ai/mcp — never a renamed duplicate. A new name creates a separate connection identity, which is what causes the "acts connected but no tools" state above.