featurepulse-mcp
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@featurepulse-mcp What are the top feature requests by MRR?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FeaturePulse MCP Server
A Model Context Protocol (MCP) server for FeaturePulse feedback management. Connect FeaturePulse to any MCP-compatible AI client to query feature requests, analyze MRR impact, and manage your product roadmap through natural language.
Features
5 Tools — Feature requests, stats, search, grouping, and status updates
MRR Data — Every request includes revenue impact from paying customers
Search & Filter — By status, priority, votes, or free-text search
Write Access — Update feature request status and priority directly
Related MCP server: Coolify MCP Server
Prerequisites
Node.js v18+
MCP Client — Claude Code, Claude Desktop, Cursor, Windsurf, or any MCP-compatible client
FeaturePulse API Key — Get one from your FeaturePulse dashboard under Project Settings
Quick Start with Claude Code
The fastest way to start — run npx directly through Claude Code. No clone, no build.
Step 1: Get Your API Key
Go to your FeaturePulse dashboard
Open Project Settings
Copy your API Key
Step 2: Add the MCP Server
claude mcp add --transport stdio featurepulse \
--scope user \
--env FEATUREPULSE_API_KEY=<YOUR_API_KEY> \
-- npx -y featurepulse-mcpReplace <YOUR_API_KEY> with your API key.
Step 3: Restart Claude Code
Quit and reopen Claude Code for the new server to load.
Step 4: Verify
Ask Claude:
List the available FeaturePulse tools.You should see 5 tools including list_feature_requests and get_project_stats.
Setup with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"featurepulse": {
"command": "npx",
"args": ["-y", "featurepulse-mcp"],
"env": {
"FEATUREPULSE_API_KEY": "your-api-key-here"
}
}
}
}Setup with Cursor / Windsurf
Add the same configuration to your editor's MCP settings file. Both Cursor and Windsurf support the MCP standard.
Available Tools
Tool | Type | Description |
| Read | Browse and filter feature requests with MRR data. Filter by status, priority; sort by votes, MRR, or date. |
| Read | High-level overview — total requests, votes, MRR by status and priority. Top 10 by votes and MRR. |
| Read | Full-text search across feature request titles. |
| Read | Group requests by status or priority with aggregated counts and MRR. |
| Write | Change the status, priority, or status message of a feature request. |
Example Prompts
"What are the top feature requests by MRR?"
"Show me all pending high-priority requests"
"How much revenue is behind planned features?"
"Search for feedback about dark mode"
"Mark the dark mode request as in_progress"
"Give me a summary of feature requests grouped by status"
Configuration
Variable | Required | Description |
| Yes | Your project API key from the FeaturePulse dashboard |
| No | API base URL (defaults to |
How It Works
AI Assistant ←→ MCP Server (stdio/JSON-RPC) ←→ FeaturePulse API (HTTPS)The MCP server communicates over stdio using JSON-RPC. When your AI assistant calls a tool (e.g. list_feature_requests), the server makes authenticated requests to the FeaturePulse API and returns formatted results.
Development
cd mcp-server
npm install
npm run dev # Run with tsx (auto-reload)
npm run build # Compile TypeScript
npm start # Run compiled versionTesting with MCP Inspector
npx @modelcontextprotocol/inspector npx featurepulse-mcpLicense
MIT
Available Tools
6 toolsanalyze_feedback_by_groupA
Analyze and group all feature requests by a chosen dimension (status or priority), returning counts, total votes, and aggregated MRR for each group. Ideal for generating summaries like 'how much revenue is waiting on planned features?' or 'what's the MRR impact of unaddressed high-priority requests?'
Inputs: group_by (required), project_id.
get_project_statsA
Get a high-level statistical overview of your FeaturePulse project: total requests, votes, and MRR grouped by status and priority. Includes top-10 requests by votes and by revenue impact (MRR). Use this before diving into individual requests to understand the overall landscape.
Inputs: project_id.
list_feature_requestsA
List feature requests from FeaturePulse. Supports filtering by status and priority, full-text search, and sorting. Each result includes MRR data (revenue at risk) and vote breakdown so you can prioritize development by business impact.
Inputs: q, limit, offset, status, +3 more.
list_projectsA
List all projects accessible with your API key. Use this to find the project_id needed for other tools when you have multiple projects.
Inputs: no named parameters.
search_feedbackA
Search feature requests by a text query. Returns the most relevant matching requests with their vote counts and MRR. Useful for finding related feedback before opening a new request or exploring a specific feature area.
Inputs: q (required), limit, project_id.
update_feature_statusA
Update the status or priority of a feature request. Use this to move requests through the workflow (e.g., pending → approved → in_progress → completed) or to set/change priority.
Inputs: feature_request_id (required), status, priority, project_id, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
list_feature_requests and search_feedback both support text search, making it unclear which to use for finding requests. Similarly, get_project_stats and analyze_feedback_by_group both provide aggregated MRR and vote data by status/priority, overlapping in purpose.
All tool names follow a consistent verb_noun pattern with snake_case, but the resource is referred to as both 'feature_requests' and 'feedback' (e.g., list_feature_requests vs search_feedback), and 'feature_status' is not a clear noun. This is a minor inconsistency that could cause confusion.
Six tools is a well-scoped number for a feature request management server, covering listing, searching, analysis, and updates without redundancy.
The set lacks a create_feature_request or delete_feature_request tool, which is a notable gap in the lifecycle. However, it covers listing, searching, analysis, and status updates, so agents can work around the missing creation.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA versatile Model Context Protocol server that enables AI assistants to manage calendars, track tasks, handle emails, search the web, and control smart home devices.23MIT
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that enables AI assistants to interact with Coolify instances through natural language, allowing management of servers, applications, databases, and deployments.2,280 npm621MIT
- FlicenseDqualityDmaintenanceA Model Context Protocol server that enables querying feature suggestions from a Supabase database, allowing AI tools like Cursor and Claude to access and display feature request data.1-
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing AI assistants with comprehensive project, task, and subtask management capabilities with project-specific storage.2924 npm88MIT