Mcp Public Feature Board Roadmap Monitor

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

A company's public feature board: top requests, votes, status, integration asks.

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Finds a company's public feature board or roadmap from its domain and returns its top feature requests, votes and statuses.

What you can do
  • Locate a company's public feedback board or roadmap from a domain, including boards on the company's own subdomain
  • Fall back to common board platforms such as Canny, Featurebase, Frill and UserVoice when no board is linked from the homepage
  • Return the top feature requests with votes, status and integration asks
When to use it
Useful when researching a vendor's public roadmap, comparing customer-requested features, or checking whether a specific integration has been requested and how much support it has.
Requirements
Runs as a local npm package over stdio on a desktop machine. Requires an Apify API token supplied in the APIFY_TOKEN environment variable, plus network access to fetch company homepages and board pages.
Before you install
The Apify token is a billable account credential; keep it private and be aware that Apify usage may incur costs. The server reads third-party public web pages, so results depend on what those sites expose.

Installation

In SourceWeft

  1. Open Mcp Public Feature Board Roadmap Monitor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Public Feature Board and Roadmap Monitor MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Public Feature Board Roadmap Monitor MCP server]

An MCP server for the Mamba Labs Public Feature Board and Roadmap Monitor actor on Apify. Give it a company domain. Each run finds the company's public feature board and returns the requests its customers vote on most.

What's Inside

What it does

  • Finds the board: a link on the homepage, a board on the company's own subdomain, or a Canny, Featurebase, Frill, or UserVoice board named after the company that links back to its domain.
  • One board row per company: platform, board URL, total posts, top request, status counts, and integration_targets, the products customers ask the company to integrate with.
  • One request row per request: title, votes, status, comments, board, link, and is_integration_request with integration_target.
  • Monitoring: with only_new and a state_key, only new requests, status changes, and vote jumps since the last run.

A company with no public board comes back free with a row_status saying so.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-public-feature-board-roadmap-monitor": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-public-feature-board-roadmap-monitor"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The get_feature_board_requests tool appears.

Prerequisites

Example prompts

  • "What are ClickUp's most requested features, and which integrations do its customers want?"
  • "Find the public roadmap boards for descript.com, instantly.ai, and ahrefs.com and list their planned items."
  • "Which new feature requests showed up on clickup.com's board since last week?"

Tool

get_feature_board_requests. One tool. Example arguments:

json
{  "company_domain": "clickup.com",  "max_requests": "20"}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and booleans are sent as strings.

InputTypeDescription
company_domainstringThe company website domain, for example clickup.com. The actor reads the homepage for a link to a feedback board or public roadmap, then checks the common board addresses
domainsarraySeveral company domains, one per line. Each gets its own board row. Up to 200 per run
board_urlsarrayBoard addresses you already know, for example https://feedback.canny.io. With one domain and one board URL, the board is read as that company's board. A board URL on its own is read as a company of its own
company_namestringWith one domain only: the company name as its board shows it. Used to confirm a board found by name
max_requestsstringRequest rows returned per company, most votes first, up to 100. 0 returns only the board row. Default 20
max_boardsstringBoards or forums read per company, largest first, up to 5. Canny shows its top 10 and newest 10 requests on each board page. Default 2
integration_requests_onlystringtrue to return only requests that ask for an integration. The board row still counts every request read. Default false
probe_platform_slugsstringtrue (default) checks .canny.io, .featurebase.app, .frill.co, and .uservoice.com when the site links no board. A board found this way is used only when it links back to the company domain
only_newstringtrue to return only requests that are new, changed status, or gained at least Min vote increase votes since the last run with the same state key. The board row is returned on every run. Default false
min_vote_increasestringWith only new on: the vote gain that makes a request count as changed. Default 5
state_keystringNames the saved request list, so separate schedules compare separately
max_charge_usdstringOptional. The run stops before it would charge more than this
proxy_modestringauto (default) sends requests directly and moves a host to the Apify proxy default pool only when that host refuses. A reliability setting: proxy use adds nothing to your price

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
board-found, one company whose public feature board was found and read, with its top requests$0.0038$0.00361$0.00342$0.00323
apify-actor-start, per run start$0.0005$0.0005$0.0005$0.0005

A company with no public board, a blocked board, a board with no readable request, and a Productboard portal returned as a link are free. Request rows carry no charge of their own.

Your keys

The actor needs no key. It reads public board pages and holds no key of any kind. Proxy traffic adds nothing to your price: Mamba Labs pays the platform costs of the run. proxy_mode is a reliability setting.

Full actor documentation

apify.com/mambalabs/public-feature-board-roadmap-monitor

License

MIT. See LICENSE.

Source: README.md at commit c263702

Tools

1

get_feature_board_requests

Get a company's public feature requests

Find a company's public feature board from its domain (for example clickup.com) and return its top requests. The homepage is read for a link to a feedback board or public roadmap, including one on the company's own subdomain; when none is linked, the common Canny, Featurebase, Frill, and UserVoice addresses are checked and a board is used only when it links back to the company domain. You get one company_board row (platform, board URL, total posts, top request, status counts, and the integrations customers ask for) and one request row per feature request, most votes first, with votes, status, comments, board, and an integration flag naming the product asked for. With only_new and a state_key, only new requests, status changes, and vote jumps since the last run. A Productboard portal comes back as a link. No board, a blocked board, and a board with no readable request are free. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges once per company whose board was found and read.

Parametersdomainsonly_newstate_keyboard_urlsmax_boardsproxy_modecompany_namemax_requestscompany_domainmax_charge_usdmin_vote_increaseprobe_platform_slugs+1 more

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Oct 26, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts