featurepulse-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEATUREPULSE_URL | No | API base URL | https://featurepul.se |
| FEATUREPULSE_API_KEY | Yes | Your project API key from the FeaturePulse dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| 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. |
| analyze_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?' |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.