Install Deck's AI agent plugin for Claude Code or Codex to use customer feedback skills and the hosted Deck MCP server.

Deck Plugin for Claude Code and Codex

The Deck plugin adds Deck-specific skills to Claude Code and Codex so your AI coding agent can use customer feedback while you plan, prioritize, research, and write product artifacts. The plugin also bundles Deck's hosted MCP server configuration, so the same assistant can authenticate with Deck and query your organization's feedback data when a skill needs evidence.

Use the plugin when you want your coding agent to:

ground product discovery in real Deck themes, insights, transcripts, segments, opportunities, and NPS feedback
prepare feedback analysis, weekly digests, initiative briefs, and roadmap opportunity reviews
compare roadmap options with evidence instead of generic prioritization advice
connect to Deck through the hosted MCP server without manually writing MCP configuration

The plugin source is published at github.com/getdeck-io/plugins.

Before you start

You need:

a Deck account with access to at least one organization
Deck MCP access enabled by an organization admin in Settings -> MCP
Claude Code or Codex 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

What the plugin installs

The plugin includes:

Claude Code and Codex plugin manifests
marketplace entries for installing deck@deck-plugins
Deck's hosted MCP server configuration at https://mcp.getdeck.io/mcp
Deck skills that guide agents through product discovery, feedback analysis, prioritization, roadmap review, initiative briefs, weekly digests, and NPS analysis

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
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 -> Deck Intelligence or MCP

For plain Markdown context, use:

Included skills

Skill	Use it for	Example prompt
`discovery-partner`	Early product discovery, idea validation, problem exploration, and "what should we build next?" conversations grounded in Deck feedback.	"What should we work on next for onboarding? Ground it in Deck feedback and include the strongest customer evidence."
`feedback-analyst`	Deep investigations into customer problems, themes, churn reasons, adoption blockers, source feedback, and segment differences.	"Deep dive into why enterprise customers are churning. Read source feedback and summarize themes, segments, quotes, and open questions."
`deck-weekly-feedback-digest`	Recurring or ad hoc PM and design digests covering recent feedback, changing themes, opportunities, initiatives, and NPS movement.	"Create a weekly feedback digest for self-serve teams over the last 7 days, with emerging pain points, NPS movement, and recommended actions."
`deck-initiative-brief-generator`	Initiative briefs with customer problem, target segment, proposed scope, non-goals, 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."
`nps-breakdown`	NPS score explanation, promoter/passive/detractor breakdowns, score drivers, segment-level views, related opportunities, and representative feedback.	"Break down NPS for Enterprise accounts this quarter, including promoter, passive, and detractor counts, drivers, related opportunities, and representative feedback."
`prioritisation-advisor`	Roadmap comparisons using feedback 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 call out missing data."
`deck-roadmap-opportunity-review`	Interviews about planning context, then surfaces 3 to 7 roadmap opportunity candidates with evidence strength and next steps.	"Interview me about the growth team's activation goals, then surface 3 to 5 roadmap opportunities from Deck feedback for SMB users."

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 and initiatives
NPS summaries, detractor drivers, promoter feedback, trends, and recommendations

This means prompts like "which problem is bigger?" can produce an evidence-backed comparison 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

Use Deck to investigate onboarding friction. What are customers struggling with, which segments mention it most, and what should we validate next?

Feedback analysis

Deep dive into feedback about reporting exports. Read the strongest source evidence, summarize key themes, and call out gaps in the data.

Prioritization

Compare improving Slack summaries, CSV import reliability, and NPS analysis. Rank them using Deck evidence and explain the tradeoffs.

Weekly digest

Create a weekly feedback digest for the product team covering the last 7 days. Include emerging pain points, opportunity backlog movement, and NPS changes.

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, related opportunities, and representative feedback.

Access and security

Deck controls access in three places:

Organization setting: an admin must enable MCP access 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

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

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

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 and Codex

On this page