mcpbeat

FeatureJet MCP Server

com.featurejet/feedback-board
answering

FeatureJet is answering right now. Last checked 10 min ago. It exposes 22 tools.

The feedback board your AI agents work from: users vote, agents build over MCP. 22 tools.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
22
Tools
read from the server
449 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add feedback-board --transport http https://mcp.featurejet.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "feedback-board": {
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.feedback-board]
url = "https://mcp.featurejet.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "feedback-board": {
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "feedback-board": {
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

post
create_post
Create a post on a board.
delete_post
Delete a post by hiding it through the developer API.
get_post
Get one post by board slug and post id.
update_post
Update mutable post fields; null queue_rank explicitly un-ranks.
board
create_board
Create a new feedback board, as a DRAFT. `slug` is the board's URL path segment (lowercase, hyphenated, unique); `name` is the display name. The new board's public URL 404s until a human publishes it from the dashboard -- `publish_board` is off by default (403 `publish_disabled`).
get_board
Get one board by slug.
analytics
get_analytics
Get read-only analytics for a board.
boards
list_boards
List boards available to the caller's FeatureJet API key.
changelog
get_changelog
List shipped posts for a board.
claim
claim_post
Atomically claim a post before working on it (double-work guard). ttl_seconds defaults to 3600 (max 86400); re-claiming with the same key extends the lease. Returns 409 if another key holds a live claim.
comment
create_comment
Comment on a post as the board team, optionally replying to a comment.
comments
list_comments
List comments for a post.
evidence
add_evidence
Attach implementation evidence to a post (shown publicly). kind is one of branch|commit|pr|transcript|url; ref is the branch name, commit sha, or URL. Voters see these in the post page's "Implementation" section.
ping
ping
Check MCP and FeatureJet API reachability for the caller's key.
posts
list_posts
List posts for a board, optionally filtered by status, search, or tag.
propose
propose_status
Propose a status change for the board owner to confirm. The agent-honest way to mark work done: nothing changes on the public board and no voter is notified until a human confirms the proposal from the dashboard. status is one of open|planned|in_progress|shipped|declined; a new proposal replaces any pending one. Prefer this over update_post's direct status flip.
publish
publish_board
Publish a board so it is live at its public URL. OFF BY DEFAULT. Putting a board on the public internet is a human decision: unless the FeatureJet deployment has opted in, this returns 403 `publish_disabled` and the owner publishes from the dashboard. Where it is enabled it needs a `write` (or `admin`) scoped key and an active subscription -- an org without one gets 403 `subscription_required`.
queue
get_queue
Top UNCLAIMED posts in the owner's curated build order. Owner-ranked posts (queue_rank, lower = sooner) come first, then unranked planned posts by votes. Call this to find the next thing to build, then claim_post before starting work.
release
release_post
Release a post's claim so other agents can pick it up.
unpublish
unpublish_board
Return a board to draft so its public URL stops serving it. Nothing is deleted; publish it again to bring it back.
votes
list_votes
List vote metadata for a post.
whoami
whoami
Confirm the caller's API key by listing accessible boards.

Endpoints

URLTransportStateLatencyChecked
https://mcp.featurejet.com/mcp streamable-http answering 448 ms 10 min ago

FeatureJet — questions

Answers built from our own checks of this server.

What can FeatureJet do?
It exposes 22 tools, read directly from the server on our last check. Among them: add_evidence, claim_post, create_board, create_comment, create_post, delete_post and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is FeatureJet mostly used for?
Its tools cluster around post and board. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is FeatureJet working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 449 ms. The bar chart above shows every period we have measured.
How do I connect FeatureJet?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FeatureJet need an API key?
No. FeatureJet completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 22 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FeatureJet?
It answers our handshake in 449 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.