Connect your AI
Project Desk is operated through the AI clients you already use. Connect once, sign in in your browser, then let those clients work in the desks your account can access through live tools.
Start by reflecting the work you already have. Open a coding agent that can already see your repositories — Claude Code, Codex, or another agent running in your workspace — and paste "Run atlier_project_scan first to get up to speed on Project Desk's capabilities and workflow, so you can help me use it. Then inspect the repositories in this workspace, including their setup and agent instructions, and show me a list of the projects worth tracking. Change nothing until I choose the projects I want to promote to Project Desk." The agent uses read-only discovery in the workspace it can access and comes back with what it found and what it would track - the named projects themselves. You choose what lands on the desk; it explains any suggested workspace, documentation, or architecture change before it writes a file.
Project Desk never scans your computer. Your coding agent reads only the repositories already available to it, then writes the project state you approve into your desk. Project Desk itself cannot open repositories, source files, local environments, terminals, credential stores, or Git history — a host coding agent with its own access does that, and passes in the project facts you approve.
If the AI you are talking to cannot reach your repositories — a browser chat holding only the Project Desk connector, for example — it should say so rather than guess. Open Claude Code, Codex, or another coding agent inside your workspace and use the prompt there instead.
Starting something new rather than connecting existing work? Tell your agent what you want to build and it can create your first project, get it running, and connect it to Project Desk. From then on it's all conversational: "what needs me?", "add an issue," "close ate-12."
Pick your client
Choose the client you already work in. Project Desk adds desk tools only; the files, commands, and other capabilities available to that client still come from the client and the workspace permissions you configured there.
Claude Code
Find Project Desk in Claude's connector directory, or use manual MCP setup.
Set up Claude Code →Codex
Add the remote MCP server from Codex settings or the CLI.
Set up Codex →Claude
Find Project Desk in Claude's connector directory, or use manual MCP setup.
Set up Claude →Manual MCP setup
For Codex, another MCP client, or any time you prefer to paste the exact URL, use this setup instead.
Your connector URL
https://atlier.ai/mcp
Any other MCP client
The connector is a standard MCP server — streamable HTTP transport, OAuth 2.1 with dynamic client registration (RFC 7591), discovery at https://atlier.ai/.well-known/oauth-protected-resource/mcp. Any client that supports remote MCP servers over HTTP with a browser OAuth flow can connect — for example Cursor, VS Code (Copilot agent mode), Gemini CLI, Windsurf, or Cline. (Clients that only speak local stdio MCP can't reach a hosted connector.)
What the tools can do: scan and update projects, create and move issues, record handoffs, archive or restore projects, and let a desk owner permanently remove a project through a protected preview-and-confirm flow. Permanent removal deletes Project Desk records only; it never touches repositories, files, Git history, deployments, or other external systems. The connector exposes no raw project or issue hard-delete.
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.