MCP Server

Connect FeatureDeck to Cursor, Claude, ChatGPT, and other MCP-compatible AI tools. Query feature requests and manage your roadmap from your editor.

Overview

The FeatureDeck MCP server lets AI assistants read your project's feature requests and roadmap, and update roadmap items when you have editor or admin access. It proxies requests to the FeatureDeck API using your project API key — it never connects directly to the database.

MCP Client (Cursor, Claude, …)
    ↓
FeatureDeck MCP Server
    ↓
FeatureDeck API
    ↓
Supabase

Getting Your API Key

Every MCP client authenticates with a FeatureDeck project API key. Generate one from your dashboard:

Sign in to the FeatureDeck dashboard
Select your project and open Settings
Generate or copy your API key (starts with fd_live_)
Paste it into your MCP client configuration

Cursor Setup

The fastest way to get started is the hosted MCP server. Add this to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "featuredeck": {
      "url": "https://mcp.featuredeck.in/mcp",
      "headers": {
        "Authorization": "Bearer fd_live_xxxxxxxxx"
      }
    }
  }
}

Replace fd_live_xxxxxxxxx with your project API key. Restart Cursor after saving.

Available Tools

Tools are scoped to the project attached to your API key. Write tools require editor or admin role.

Read

• featuredeck_whoami
• featuredeck_list_feature_requests
• featuredeck_get_feature_request
• featuredeck_list_roadmap
• featuredeck_get_roadmap_item

Write (editor/admin)

• featuredeck_create_roadmap_item
• featuredeck_update_roadmap_item
• featuredeck_delete_roadmap_item

Example Prompts

Once connected, ask your AI assistant things like:

• “What are the top-voted feature requests right now?”
• “Show me everything on the roadmap that's in progress.”
• “Create a roadmap item for dark mode support.”
• “Which project and role is this API key scoped to?”

Local / Self-Hosted

Run the MCP server locally with stdio transport for Claude Desktop or offline development. Clone the featuredeck-mcp repo, or use npx:

Environment variables

FEATUREDECK_API_URL=https://featuredeck.in
FEATUREDECK_API_KEY=fd_live_xxxxxxxxx
MCP_TRANSPORT=stdio

Cursor (local stdio)

{
  "mcpServers": {
    "featuredeck": {
      "command": "npx",
      "args": ["-y", "featuredeck-mcp"],
      "env": {
        "FEATUREDECK_API_URL": "https://featuredeck.in",
        "FEATUREDECK_API_KEY": "fd_live_xxxxxxxxx",
        "MCP_TRANSPORT": "stdio"
      }
    }
  }
}

Run from source

git clone https://github.com/Mak-3/featuredeck-mcp.git
cd featuredeck-mcp
npm install
npm run build
npm start

Hosted Deployment

The hosted server at https://mcp.featuredeck.in accepts HTTP transport. Each client sends its own API key via the Authorization header:

Authorization: Bearer fd_live_xxxxxxxxx

POST /mcp — MCP protocol endpoint

GET /healthz — health check

Need Help?

Questions about MCP setup or tool behaviour:

📧 Email: featuredeck.support@gmail.com
💻 Source: https://github.com/Mak-3/featuredeck-mcp
📱 SDK docs: React Native integration