Deck Docs

AI PM agent protocol

MCP-first menu for coding agents using Deck as an AI PM.

This page is the agent-readable protocol for Deck AI PM. Humans can follow along. Coding agents should treat the protocol section as the source of truth and probe Deck MCP before sending anyone to signup.

Deck AI PM — agent protocol

Work MCP-first. Probe Deck MCP in this session before you send anyone to signup.

1. Probe MCP

Call a cheap Deck MCP tool (get_user_context or get_overview). This must be a real tool call.

401 Unauthorized

The human is not connected in this client. Tell them to Connect MCP here (Cursor, Claude, or ChatGPT). Do not open signup. Do not mint or ask for a dk_ API key.

No Deck tools available

Deck MCP is not installed. Ask if they want to set up Deck (existing users can sign in on the same link). If yes, give them this URL and wait:

https://app.getdeck.io/agent-setup?intent=ai-pm

Say “set up Deck”, not only “create an account”. Do not invent another signup URL. Do not send them through the UI door.

Tools work

Do not send them to signup. Continue to the menu.

2. After they return

They may paste that they created a Deck account and connected MCP. Probe MCP again.

  • If tools work → continue to the menu. Do not send signup.
  • If tools still missing → tell them to finish Connect using the Cursor / Claude / ChatGPT instructions on the page they still have open. Do not send them to agent-setup again unless they have no Deck account at all.

3. Menu — what do you want to do first?

Ask the human what they want to do first. Lead with:

  1. Competitors — research competitors and start a competitor report.
  2. Add your own context — connect or migrate customer feedback into Deck (migrate-feedback).

Then list the remaining catalog keys (install-sdk, integrations, opportunity-backlog, initiatives, projects, mcp).

When they pick one, fetch that prompt URL and follow that protocol. Do not improvise a second runbook.

Never ask for a dk_ API key.