Project Desk by Atlier

Connect your AI

Project Desk works through the AI clients you already use. Connect once, sign in in your browser, and your clients can work in every desk your account can access.

Start by reflecting the work you already have

  1. Open a coding agent that can see your repositories, such as Claude Code or Codex, in your workspace.
  2. Paste this prompt: 
    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.

  3. Choose what lands on your desk. The agent only reads, then lists the projects worth tracking. Nothing is written until you pick them.

Project Desk never scans your computer. It cannot open repositories, source files, local environments, terminals, credential stores, or Git history; a host coding agent with its own access reads them and sends only the project facts you approve. More on what Project Desk can access.

A browser chat that holds only the Project Desk connector cannot see your repositories, and it should say so rather than guess. Use the prompt in Claude Code, Codex, or another coding agent inside your workspace instead.

Starting something new? Tell your agent what you want to build: it can create your first project and add it to your desk. From then on it is all conversation: "what needs me?", "add an issue," "close the login bug."

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

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

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.

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.