← Connect your AI

Codex

Add Project Desk as a remote MCP server. Project Desk supplies desk tools and OAuth; Codex keeps control of local workspace access and tool approvals.

Your connector URL

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

Fastest setup

Run this in a terminal:

codex mcp add projectdesk --url https://atlier.ai/mcp

Then authenticate projectdesk when Codex prompts you, using the same GitHub, Google, or Microsoft account you use for the desk.

Settings setup

  1. Click your account name and choose Settings.
  2. Open MCP servers, then choose Add server.
  3. Choose Streamable HTTP (not STDIO).
  4. Name it ProjectDesk, paste the connector URL into URL: https://atlier.ai/mcp — leave Bearer token env var and Headers empty (sign-in is OAuth, not a static token) — and save.
  5. Click Authenticate, sign in with the same GitHub, Google, or Microsoft account you use for the desk, and approve the Project Desk authorization screen.
  6. Use the permission settings you prefer in Codex.
  7. Your desk may be empty at first — that's expected. Say "Connect my repositories to Project Desk. Find the work available to you, read their existing setup, and show me your recommended next step before changing anything." If no repository is available, ask Codex to create and connect your first project.

Already added it once? Codex remembers your sign-in, so re-saving the same URL won't re-prompt — normally that's fine. But if the tools never appear afterward, that same "no re-prompt" is the tell that the sign-in went stale — see If your tools disappear below.

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. Run codex mcp login <your server name>, then start a new task. You need both. Codex saves the credential right away, but a task that is already running keeps the connection it started with — so the login alone will not bring your tools back, and neither will relaunching. This is a known Codex issue (openai/codex#32590), not a Project Desk problem: Codex reports the server as enabled: true and Auth: OAuth the whole time.
  3. Fully quit and relaunch the app — quit it completely, not just the window — then reconnect.
  4. 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.

Machine-readable setup

Connection facts are available at /setup/codex.json.