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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/featurepulse/featurepulse-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server