Install Deck's plugin so your coding agent can help decide what to build, prepare product work, and use the hosted Deck MCP server.

Deck Plugin for Claude Code, Codex, and Grok

The Deck plugin puts Deck — the AI Product Manager that Autonomously Improves your Product — in Claude Code, Codex, and Grok Build. Your coding agent can run the improvement loop: use customer and product context to find the highest-leverage problem, rank what to act on, draft initiative and Project briefs, and check NPS. The plugin also bundles Deck's hosted MCP server configuration, so the same assistant can authenticate with Deck and query your organization's evidence when a skill needs it.

Use the plugin when you want your coding agent to:

find the highest-leverage problem from Deck themes, insights, transcripts, segments, opportunities, and NPS
investigate a problem in depth before acting
rank roadmap options and recommend a next action
turn the chosen problem into initiative or Project briefs
connect to Deck through the hosted MCP server without manually writing MCP configuration

The plugin source is published at github.com/getdeck-io/plugins. The current plugin implementation includes six skills: discovery-partner, feedback-analyst, initiative-brief-generator, project-brief-generator, nps-breakdown, and prioritisation-advisor.

Before you start

You need:

a Deck account with access to at least one organization and product signal in that workspace
Deck MCP access turned on for your organization (on by default for new organizations; if it is off, an organization admin can turn it on in Settings -> MCP)
Claude Code, Codex, or Grok Build installed locally
browser access for the OAuth login flow

Deck MCP uses browser OAuth. You do not need to create or paste API keys for the plugin.

Install in Claude Code

Add the Deck plugin marketplace:

claude plugin marketplace add getdeck-io/plugins

Install the Deck plugin:

claude plugin install deck@deck-plugins

Start Claude Code, then open MCP management:

/mcp

Follow the browser prompts to sign in to Deck and approve the connection.

To confirm the MCP server is present from your shell, run:

claude mcp list

If your Claude Code install does not pick up the bundled MCP server, add it manually:

claude mcp add --transport http deck https://mcp.getdeck.io/mcp

Install in Codex

Add the Deck plugin marketplace:

codex plugin marketplace add getdeck-io/plugins

Install the Deck plugin:

codex plugin add deck@deck-plugins

Confirm the Deck MCP server is installed:

codex mcp list

Authenticate through the browser OAuth flow:

codex mcp login deck

If your Codex install does not pick up the bundled MCP server, add it manually:

codex mcp add deck --url https://mcp.getdeck.io/mcp

Install in Grok Build

Add the Deck plugin marketplace:

grok plugin marketplace add getdeck-io/plugins

Install the Deck plugin:

grok plugin install deck --trust

Enable it if Grok left the plugin off:

grok plugin enable deck

Confirm the Deck MCP server is installed:

grok mcp list

On first Deck tool use, Grok opens browser OAuth for https://mcp.getdeck.io/mcp. You can also start that flow from /mcps by selecting the deck server and pressing i.

If your Grok install does not pick up the bundled MCP server, add it manually:

grok mcp add --transport http deck https://mcp.getdeck.io/mcp

What the plugin installs

The plugin includes:

Claude Code, Codex, and Grok Build plugin manifests
marketplace entries for installing the plugin from this repository
Deck's hosted MCP server configuration at https://mcp.getdeck.io/mcp
Deck skills that guide agents through the improvement loop: discovery, investigation, ranking, initiative briefs, Project briefs, and NPS

After installation and OAuth, your agent can call Deck MCP tools when a skill needs feedback evidence. The plugin does not grant access by itself; Deck still checks your user identity, organization membership, and the organization's MCP access policy.

Agent-readable product context

When an agent needs to explain where the plugin fits in Deck, point it to these product surfaces:

Product surface	Use it for	Canonical page
Themes	Recurring patterns, source mix, sentiment, segments, and quote-backed evidence.	Themes
Opportunity Backlog	Ranked customer problems with impact, trend, affected customers, confidence, and supporting evidence.	Opportunity Backlog
Initiatives	Customer-backed product plans with goals, generated briefs, statuses, outcomes, and linked evidence.	Initiatives
Projects	Delivery-ready Build work linked to customer evidence, initiatives, and Jira or Linear execution artifacts.	Projects
MCP Server	Hosted OAuth MCP access for Deck data from AI clients and editors.	MCP Server

The shortest workflow model is:

Integrations + imports -> Themes -> Opportunity Backlog -> Initiatives -> Projects -> Deck Intelligence or MCP

For plain Markdown context, use:

Included skills

Skill	Use it for	Example prompt
`discovery-partner`	Find the highest-leverage problem to work on, using Deck themes, insights, segments, and customer evidence.	"What should we work on next for onboarding? Ground it in Deck evidence and recommend the next action."
`feedback-analyst`	Investigate a problem in depth before the AI PM acts — themes, transcripts, segments, churn reasons, and adoption blockers.	"Deep dive into why enterprise customers are churning. Read source evidence and summarize themes, segments, quotes, and what we should do next."
`initiative-brief-generator`	Turn the chosen problem into an initiative the team can run, with customer problem, target segment, scope, success metrics, risks, and evidence appendix.	"Generate an initiative brief for improving CSV import reliability using Deck evidence, including scope, non-goals, success metrics, and risks."
`project-brief-generator`	Turn the chosen problem into delivery-ready Project scope, with execution notes, success metrics, risks, and evidence appendix.	"Generate a Project brief for the Linear-linked onboarding cleanup work using Deck evidence, including scope, non-goals, execution notes, and risks."
`nps-breakdown`	Check whether the product is improving, and what to fix first — promoter/passive/detractor breakdowns, drivers, and related opportunities.	"Break down NPS for Enterprise accounts this quarter, including promoter, passive, and detractor counts, drivers, and what to improve first."
`prioritisation-advisor`	Rank what to act on next and say why, using volume, sentiment, segment concentration, feature requests, NPS impact, recency, and quotes.	"Compare billing flexibility, onboarding templates, and reporting exports for the next roadmap cycle. Rank them using Deck evidence and recommend the next action."

How the skills use Deck evidence

The skills are designed to fetch evidence before making recommendations. Depending on the request, they may ask the Deck MCP server for:

organization overview and available segments
themes, subthemes, sentiment, and category breakdowns
matching insights and original source transcripts
feedback source lists and processing status
opportunity backlog entries, initiatives, and Projects
NPS summaries, detractor drivers, promoter feedback, trends, and recommendations

This means prompts like "which problem is bigger?" can produce an evidence-backed ranking and a recommended next action instead of a generic answer. The agent should cite counts, segments, sentiment, source links, and uncertainty when the underlying data is thin.

Example prompts

Product discovery

What's the highest-leverage problem in Deck right now for onboarding, and what should we act on?

Feedback analysis

Deep dive into reporting exports. Read the strongest source evidence, summarize key themes, and recommend the next Deck action.

Prioritization

Compare improving Slack summaries, CSV import reliability, and NPS analysis. Rank them using Deck evidence and recommend the next action.

Project brief

Generate a Project brief for the Linear-linked onboarding cleanup work using Deck evidence. Include customer problem, parent initiative, execution scope, success metrics, risks, and evidence appendix.

Initiative brief

Generate an initiative brief for a new onboarding setup checklist using Deck feedback. Include customer problem, scope, non-goals, success metrics, risks, and evidence appendix.

NPS analysis

Break down NPS for enterprise customers this quarter. Include promoter, passive, and detractor counts, drivers, and what to improve first.

Access and security

Deck controls access in three places:

Organization setting: MCP access is on by default for new organizations. An admin can turn it off or on from Settings -> MCP.
Role policy: admins choose whether MCP is available to admins only or to admins and members.
User OAuth: each user authenticates through the browser and Deck scopes the connection to their account and organization access.

The plugin does not bypass Deck permissions. If MCP is disabled, your role is not allowed, or your account is not a member of the selected organization, the agent cannot read Deck data.

Troubleshooting

The plugin installs but Deck tools are unavailable

Check that the MCP server exists:

claude mcp list
codex mcp list
grok mcp list

If the server is missing, add it manually:

claude mcp add --transport http deck https://mcp.getdeck.io/mcp
codex mcp add deck --url https://mcp.getdeck.io/mcp
grok mcp add --transport http deck https://mcp.getdeck.io/mcp

MCP shows "not logged in"

That usually means the server is installed but OAuth has not completed yet.

For Claude Code, start Claude Code and run:

/mcp

For Codex, run:

codex mcp login deck

For Grok Build, open /mcps, select the deck server, and press i.

Then complete the browser login flow.

OAuth succeeds but the agent cannot access feedback

Ask a Deck organization admin to verify:

MCP is enabled in Settings -> MCP
your role is allowed to use MCP
you are signed in with the Deck account that belongs to the organization
the organization has the feedback data you expect the agent to analyze

A skill gives a generic answer

Ask the agent to use Deck explicitly and cite evidence:

Use Deck MCP data for this answer. Include insight counts, themes, relevant segments, source links, and any uncertainty.

If the agent still cannot access Deck data, check MCP authentication and organization access first.

Deck Plugin for Claude Code, Codex, and Grok

On this page