AI Integrations

Connect Your Agent

Give Claude Code, Codex, Cursor, Claude Desktop, ChatGPT, Gemini CLI or another MCP client access to your Stardeck organization.

Your apps' data stores, tasks, memory and settings live on Stardeck, not in the repo. The Stardeck MCP server gives your agent tools to reach them. Use the same server for a coding agent building an app on your machine and for a chat client such as Claude Desktop or ChatGPT.

Before you begin

  • Membership in the org you want to connect.
  • A role to bind the connection to. Pick the least permissive one that covers your needs. See Members & Roles.
  • To build an app locally: a checkout of it (GitHub Access), with npm install run.

The server URL is the same for every client and every app:

https://www.stardeck.ai/api/mcp

On the Agents page, Connect an agent shows each client's command or config with the URL filled in.

One-command setup

In your app's checkout:

npm run setup

It signs you in, picks the app's project, asks which agents get the Stardeck MCP server (installed ones are ticked), adds it to each, and pulls your environment into apps/web/.env.local. The server is named after the app's organization, such as stardeck-harbor-cafe. Then authorize in your agent: /mcp in Claude Code, codex mcp login stardeck-harbor-cafe in Codex. Setup prints the step for each one.

AgentWhere the server is added
Claude Code.mcp.json in your checkout
VS Code (GitHub Copilot).vscode/mcp.json in your checkout
Cursor~/.cursor/mcp.json
Codex~/.codex/config.toml
Gemini CLI~/.gemini/settings.json
Windsurf~/.codeium/windsurf/mcp_config.json
  • --agents claude-code,codex skips the picker.
  • No setup script in your app? Run npx @stardeckai/cli setup.
  • Running it again leaves agents that are already set up alone.
  • With --api-key, setup can't look up the organization, so the server is named stardeck.

Not working in an app checkout, or using a chat client? Add the server by hand below.

Each connection is authorized once in the browser:

  1. Your client opens a Stardeck page.
  2. Sign in, then pick the organization, the role the connection acts as, and Read only or Read & write.
  3. Your client receives a token.

Client setup

Add the server once per organization. Naming it after the organization, such as stardeck-harbor-cafe, keeps two organizations apart in the same client.

claude mcp add --transport http --scope user stardeck-harbor-cafe https://www.stardeck.ai/api/mcp

Run /mcp, pick stardeck-harbor-cafe and authenticate.

To verify any client, ask: "What's in my Stardeck knowledge store?"

How the connection works

  • One connection per organization. Tools that act on an app take its slug, so name the app in your request. To skip that in a coding agent, add "This repo is the Stardeck app storefront." to CLAUDE.md.
  • Tools follow the role you picked, not your own role. See Tools & Permissions.
  • Another organization gets its own server. Run setup in one of its apps, and its stardeck-<organization> server is added next to the first one. Sign in to it as above.
  • Working for clients as a partner? Connect each client organization separately. See Agents on Client Organizations.

Let your agent open your apps in a browser

A Read & write connection can sign your agent's browser tool in to one of your apps, on a staging by default, as you or (for an org admin) as another person or role. It needs:

  • Allow agents to access turned on by an org admin under Settings → Team Members.
  • A role with Open Apps in a Browser, plus Open Apps as Another Person or Role to open the app as someone else. Both start on Admin only.
  • A browser tool in your client, such as the Playwright MCP server, Claude in Chrome or Cursor's browser.

Your agent gets a one-time link that works for 60 seconds and keeps the browser signed in to that app for up to 30 minutes. Treat the link like a password. What the browser does in the app is real, production included. See Opening an app in your browser.

Managing connections

All connections are on the Agents page. Changes apply on the next tool call, with no re-authorization.

  • Change the role the connection acts as.
  • Change the access level (Read only or Read & write).
  • Revoke access.

Each of these also signs out any app browser sign-in the connection opened.

You can always manage your own connections. Managing another member's needs the Manage AI Connectors permission.

If tools don't show up or a call is refused, see Troubleshooting.

Next steps