Claude Code

Preferred: connect through Claude

1. Open Claude's connector directory and find Project Desk.
2. Choose Connect, then authorize with the same GitHub, Google, or Microsoft account you use for the desk.
3. Open Claude Code and use the connector with the workspace permissions you prefer.

Can't find the published connector, or prefer manual setup? Use the account connector below.

Your connector URL

https://atlier.ai/mcp

Manual setup instead

1. Click your account name (bottom-left) and choose Settings.
2. In Settings, open Connectors (under Customize in the left rail).
3. Click Add → Add custom connector.
4. Name it ProjectDesk, paste the connector URL above into Remote MCP server URL, leave the OAuth fields blank, and click Add.
5. The new connector shows "not connected yet" — click Connect.
6. 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.
7. Approve the Authorize access to your desk screen — click Allow access.
8. Use the tool-permission settings you prefer in Claude Code.
9. 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.

Check the connection before resetting it

A browser sign-in, an authorization, and tools in the current AI chat are separate facts. This page cannot inspect your AI app or prove its account matches the browser.

1. Confirm the browser account and intended desk. In Project Desk, check the signed-in identity and desk selector. Correct an account or desk mismatch before changing the connection.
2. Inspect the Project Desk tools in this AI conversation. A last verified use in Settings → Connected agents proves a past MCP call, not that every chat has loaded the tools. If they are callable, run atlier_project_scan with no arguments and select the intended desk explicitly before any write.
3. If tools are missing, start a new chat or task and check the client's MCP status. The cause can be client configuration, a disabled connector, permissions, authentication, or a transient connection problem; Project Desk cannot identify it from this page.
4. If the client reports authentication is required or access was revoked, reauthenticate the affected connector with the same URL. Do not disconnect another client that is still working.
5. Use Disconnect only as a targeted last step. In Settings → Connected agents, disconnect the affected client, then re-add the same URL https://atlier.ai/mcp. Do not create a renamed duplicate or reset a working client.

If a write result was uncertain or reports a conflict, read the project and issue again before retrying. Keep the original freshness guard; a readback tells you whether the first attempt committed.