Model Context Protocol (MCP) Integration

The Model Context Protocol (MCP) integration allows you to connect AI assistants and code editors to your Deck organization's customer feedback data. This enables your AI tools to access insights, themes, and feedback directly during conversations or while coding.

Supported clients: Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code, Windsurf, Zed, Codex, and v0 by Vercel.

What is MCP?

Model Context Protocol is an open standard introduced by Anthropic that enables AI assistants to securely connect to external data sources. MCP provides a universal interface for AI systems to read data, execute functions, and handle contextual prompts. The protocol has been adopted by major AI providers including OpenAI and is now managed by the Agentic AI Foundation under the Linux Foundation.

Deck's MCP server provides a secure, read-only interface for AI assistants to query your customer feedback data using OAuth 2.0 authentication.

Features

The Deck MCP server provides the following capabilities to AI assistants:

Insights Tools

list_insights - Browse all customer insights with filtering by theme, category, or sentiment
get_insight - View detailed information about a specific insight
search_insights - Search insights by keywords across names and quotes

Themes Tools

list_themes - View all organizational themes with insight counts
get_theme - Get detailed theme information and associated insights

Feedback Tools

list_feedback - Browse feedback sources (interviews, calls, surveys)
get_feedback - Access full transcripts and details of specific feedback items

Setup

Prerequisites

A Deck account with feedback data
Organization admin access (to configure MCP settings)
One of the following AI assistants:
- Claude Desktop (macOS or Windows)
- Claude Code (CLI)
- ChatGPT Plus, Pro, Business, Enterprise, or Education (with Developer Mode)
- Cursor
- Visual Studio Code
- Windsurf
- Zed
- Codex (OpenAI)
- v0 by Vercel

Step 1: Enable MCP Access for Your Organization

Organization admins must first enable MCP access:

Navigate to Settings → MCP in your Deck organization
Toggle Enable MCP Access to on
Select which roles can connect via MCP:
- Admins - Organization administrators
- Members - Regular organization members
Click Save Changes

Step 2: Configure Your AI Assistant

Choose the setup instructions for your preferred AI assistant below.

Claude Desktop

Add the following to your MCP configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "deck": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.getdeck.io/mcp"]
    }
  }
}

After saving the configuration:

Restart Claude Desktop completely
Claude will automatically detect the OAuth configuration from Deck's MCP server
Follow the Clerk OAuth flow to sign in to your Deck account
Grant access to the MCP integration
The connection will automatically use your default organization

Verify Connection: Look for the MCP server indicator (hammer icon) in the bottom-right corner of the input box. Click it to view available Deck tools.

Claude Code

Claude Code supports MCP servers via CLI commands. Use the following to connect to Deck:

Add the Deck MCP Server

# Add Deck MCP server (stored locally by default)
claude mcp add --transport http deck https://mcp.getdeck.io/mcp

Authenticate

Once added, authenticate within Claude Code:

# Start Claude Code
claude

# Open MCP management
> /mcp

# Follow the browser prompts to login with your Deck account

Installation Scopes

You can configure the scope of your MCP installation:

# Local scope (default) - private to you, stored in ~/.claude.json
claude mcp add --transport http deck https://mcp.getdeck.io/mcp

# Project scope - shared with team via .mcp.json file
claude mcp add --transport http deck --scope project https://mcp.getdeck.io/mcp

# User scope - cross-project, personal configuration
claude mcp add --transport http deck --scope user https://mcp.getdeck.io/mcp

Management Commands

# List all configured MCP servers
claude mcp list

# Get details for Deck server
claude mcp get deck

# Remove the Deck server
claude mcp remove deck

# Check server status (within Claude Code)
> /mcp

ChatGPT

ChatGPT supports MCP servers through the Connectors feature in Developer Mode.

Prerequisites

ChatGPT Plus, Pro, Business, Enterprise, or Education subscription
Developer Mode enabled

Enable Developer Mode

Open ChatGPT settings
Navigate to Apps & Connectors → Advanced settings
Enable Developer mode

Note: For Business/Enterprise workspaces, an admin must first enable Developer Mode in Workspace Settings → Permissions & Roles.

Add Deck Connector

Go to Settings → Apps & Connectors
Click Create under Connectors
Enter the following details:
- Name: Deck Customer Feedback
- Description: Access customer insights, themes, and feedback from Deck
- MCP Server URL: https://mcp.getdeck.io/mcp
- Authentication mode: OAuth
Select "I trust this application" to confirm
Click Create
Complete the Clerk OAuth login flow when prompted

How ChatGPT Connects

ChatGPT uses OAuth 2.1 with PKCE (Proof Key for Code Exchange) and Dynamic Client Registration:

ChatGPT queries Deck's OAuth discovery endpoint
Registers dynamically as an OAuth client
Initiates Authorization Code + PKCE flow
You authenticate with your Deck credentials
Access tokens are attached to all subsequent MCP requests

Limitations

OAuth only - API key authentication is not supported
No machine-to-machine grants - Client credentials and service accounts are not supported
HTTPS required - ChatGPT only connects to secure endpoints

Cursor

Cursor has built-in MCP support. You can add Deck using either the quick install or manual configuration.

Quick Install

Click here to install Deck in Cursor

This will automatically configure Cursor with the Deck MCP server.

Manual Configuration

Open Cursor Settings (Cmd/Ctrl + ,)
Navigate to Features → MCP
Click Add new MCP server
Enter the following:
- Name: Deck
- URL: https://mcp.getdeck.io/mcp
Save and authenticate when prompted

Alternatively, you can edit your Cursor MCP configuration file directly:

macOS: ~/.cursor/mcp.json

Windows: %APPDATA%\Cursor\mcp.json

{
  "mcpServers": {
    "deck": {
      "url": "https://mcp.getdeck.io/mcp"
    }
  }
}

Visual Studio Code

VS Code supports MCP servers through the built-in MCP extension.

Setup

Open the Command Palette (Ctrl/Cmd + Shift + P)
Search for "MCP: Add Server"
Select Command (stdio)

Enter the following command:

npx -y mcp-remote@latest https://mcp.getdeck.io/mcp

When prompted for a name, enter Deck
Follow the OAuth prompts to authenticate with your Deck account

Verify Connection

Open the Command Palette and run "MCP: List Servers" to verify Deck is connected.

Windsurf

Windsurf supports MCP servers through its Cascade settings.

Setup

Open Windsurf Settings
Navigate to Cascade → MCP servers
Click Add custom server
Add the following configuration:

{
  "deck": {
    "command": "npx",
    "args": ["-y", "mcp-remote@latest", "https://mcp.getdeck.io/mcp"]
  }
}

Save the configuration
Restart Windsurf if prompted
Follow the OAuth prompts to authenticate with your Deck account

Zed

Zed supports MCP through context servers in its settings.

Setup

Open Zed Settings (Cmd + ,)
Add the Deck context server to your configuration:

{
  "context_servers": {
    "deck": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote@latest", "https://mcp.getdeck.io/mcp"]
      }
    }
  }
}

Save the settings file
Follow the OAuth prompts to authenticate with your Deck account

Codex (OpenAI)

OpenAI's Codex CLI supports MCP servers with the experimental remote MCP feature.

Enable Remote MCP (First Time Only)

If this is your first time using remote MCP in Codex, enable it in your config:

Edit ~/.codex/config.toml:

[experimental]
rmcp = true

Add Deck Server

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

Authenticate

After adding, run Codex and follow the OAuth prompts to authenticate with your Deck account.

v0 by Vercel

v0 supports MCP servers through its connections settings.

Setup

Open v0 Settings
Navigate to Connections
Click Add Connection or look for MCP integrations
Enter the Deck MCP URL: https://mcp.getdeck.io/mcp
Follow the OAuth prompts to authenticate with your Deck account

Once connected, v0 can access your Deck customer feedback data when generating UI designs and code.

Generic MCP Clients

For any MCP-compatible tool not listed above, use these connection details:

HTTP Transport (Recommended)

URL: https://mcp.getdeck.io/mcp

stdio Transport (via mcp-remote)

Command: npx

Arguments: ["-y", "mcp-remote@latest", "https://mcp.getdeck.io/mcp"]

Most MCP clients support one of these transport methods. Refer to your client's documentation for specific configuration instructions.

Usage Examples

Once connected, you can ask your AI assistant questions about your customer feedback. Here are example prompts organized by use case:

Discovery & Overview

"Give me a summary of all customer feedback themes"
"What are the top 5 most mentioned issues this quarter?"
"How many insights do we have in each category?"

Sentiment Analysis

"Show me all negative sentiment insights from last month"
"Compare positive vs negative feedback trends"
"Which themes have the most negative sentiment?"
"What's the overall sentiment distribution across our feedback?"

Deep Dive Research

"Search for insights related to pricing concerns"
"What did customers say about the onboarding experience?"
"Show me the full transcript from the most recent user interview"
"Find all feedback mentioning competitor products"

Cross-Reference Analysis

"Which feedback sources mention both 'pricing' and 'value'?"
"List all insights in the 'Feature Requests' category"
"Show me themes that appear across multiple feedback types"

Product Planning

"What features are customers requesting most?"
"Summarize pain points mentioned in user interviews this month"
"What do customers love most about our product?"
"Identify the top 3 issues we should prioritize fixing"

The AI assistant will use the MCP tools to query your Deck data and provide informed responses based on your actual customer feedback.

Managing Access & Connections

Access Control (Admin Only)

Organization admins can control MCP access from Settings → MCP:

Enable/Disable MCP: Toggle MCP access on or off for the entire organization
Role-Based Access: Choose which roles can connect:
- Enable for admins only for restricted access
- Enable for both admins and members for broader team access
Changes take effect immediately - users with unauthorized roles will be denied access

Connection Analytics

Admins can monitor MCP usage:

View the Active Connections list to see who is currently connected via MCP
Each connection shows:
- User name and avatar
- Last connection time
- Client name (e.g., "Claude Desktop", "ChatGPT", "Cursor", "VS Code")
Use this to audit access and ensure only authorized users are connecting

Disabling Access

If MCP is disabled:

All connection attempts will be denied immediately
Existing active connections will lose access on their next request
Users will see an authorization error in their AI assistant
Re-enabling MCP restores access for authorized roles

Security

Deck's MCP server implements robust security measures:

Authentication

OAuth 2.0 / 2.1: All connections use Clerk OAuth for secure authentication
PKCE Support: Proof Key for Code Exchange prevents authorization code interception attacks
Dynamic Client Registration: Supports RFC 7591 for clients like ChatGPT that register dynamically
Token Management: OAuth tokens are managed securely by Clerk with automatic refresh

Data Protection

Read-Only Access: All data access through MCP is read-only
Organization Scoping: Connections are automatically scoped to your organization
Role-Based Access: Admins control which roles can connect via MCP

Access Control

Sign out or revoke access at any time from the MCP server interface
Organization admins can disable MCP access instantly for all users
View active connections and audit access patterns

Troubleshooting

Connection Issues

Server not appearing in Claude Desktop:

Verify the MCP server URL is correct: https://mcp.getdeck.io/mcp
Check JSON syntax in your configuration file
Restart Claude Desktop completely (quit and reopen)
Check logs:
- macOS: ~/Library/Logs/Claude/mcp*.log
- Windows: %APPDATA%\Claude\logs

Claude Code connection issues:

Verify the server was added: claude mcp list
Try removing and re-adding: claude mcp remove deck then add again
Re-authenticate via /mcp command

ChatGPT connector issues:

Ensure Developer Mode is enabled in settings
Verify you have a Plus or Pro subscription
Check that the MCP Server URL is exactly: https://mcp.getdeck.io/mcp
Try removing and recreating the connector

Cursor connection issues:

Verify the server appears in Settings → Features → MCP
Check that the URL is exactly: https://mcp.getdeck.io/mcp
Try using the quick install link
Restart Cursor and re-authenticate

VS Code connection issues:

Ensure you have an MCP extension installed and enabled
Run "MCP: List Servers" from Command Palette to verify Deck is configured
Check that npx is available in your system PATH
Try removing and re-adding the server

Windsurf connection issues:

Verify the configuration in Cascade → MCP servers
Ensure the JSON syntax is correct
Restart Windsurf after making configuration changes
Check that npx is available in your system PATH

Zed connection issues:

Verify the context_servers configuration in Zed settings
Ensure the JSON syntax is valid
Check that npx is available in your system PATH
Try restarting Zed

Codex connection issues:

Verify experimental rmcp is enabled in ~/.codex/config.toml
Run codex mcp list to verify Deck is configured
Try removing and re-adding: codex mcp remove deck then add again
Ensure you're running a recent version of Codex

Authorization Errors

"Access Denied" error:

Check that MCP is enabled for your organization
Verify your role is allowed (admin or member, depending on settings)
Contact your organization admin to verify MCP settings

OAuth flow not completing:

Ensure you're signed in to your Deck account
Try signing out of Deck and re-authorizing
Clear browser cookies and try again
Verify you belong to a Deck organization

"OAuth discovery failed" (ChatGPT):

This may indicate a temporary server issue
Wait a few minutes and try again
Ensure your network allows connections to mcp.getdeck.io

Access Control Issues

If you suddenly lose access, your organization admin may have:

Disabled MCP entirely
Changed the allowed roles and your role is no longer permitted

Contact your organization admin to request access restoration.

Support

For additional help with the MCP integration, contact the Deck support team or visit our documentation at docs.getdeck.io.

Model Context Protocol (MCP)

On this page