Back to Project Desk

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 read and update the same desk through live tools.

Your desk starts empty — that's by design. Open your coding agent and say "Connect my repositories to Project Desk. Find the work available to you, read its existing setup, and show me your recommended next step before changing anything." The agent uses read-only discovery in the workspace it can access, creates a truthful Desk mirror from what it actually finds, and explains any suggested workspace, documentation, or architecture change before it writes a file. If no repository is available, tell it what you want to build; 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."

Your connector URL

https://atlier.ai/mcp
OAuth 2.1 — sign in with GitHub, Google, or Microsoft Desk-scoped Standard MCP (streamable HTTP)

If your client lets you search a connector or app directory instead of pasting a URL, look for it by name: Project Desk.

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

Add the remote connector in the app or with one terminal command.

Set up Claude Code →

Codex

Add the remote MCP server from Codex settings or the CLI.

Set up Codex →

Claude

Add Project Desk as a custom connector in Claude Desktop or claude.ai.

Set up Claude →

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 projects, and let a desk owner invite or remove members. Removing a member revokes their desk access but preserves work and attribution; the connector does not expose hard-delete for projects or issues.

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:

  1. 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.
  2. Fully quit and relaunch the app — quit it completely, not just the window — then reconnect.
  3. 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.