FeatureJet
The feedback board your AI agents work from: users vote, agents build over MCP.
What it can do
What data it sees
Do you need an account
An API key from the service settings is required
The feedback board your AI agents work from: users vote, agents build over MCP. 22 tools.
How to connect
How to connect FeatureJet to Claude
The server address to paste into Claude settings:
https://mcp.featurejet.com/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect FeatureJet to ChatGPT
The server address to paste into ChatGPT settings:
https://mcp.featurejet.com/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect FeatureJet to Cursor
The server address to paste into Cursor settings:
https://mcp.featurejet.com/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (22)
Raw names from tools/list. Only developers need these.
| list_boards | List boards available to the caller's FeatureJet API key. |
| get_board | Get one board by slug. |
| 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`). |
| 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`. |
| unpublish_board | Return a board to draft so its public URL stops serving it. Nothing is deleted; publish it again to bring it back. |
| list_posts | List posts for a board, optionally filtered by status, search, or tag. |
| get_post | Get one post by board slug and post id. |
| create_post | Create a post on a board. |
| update_post | Update mutable post fields; null queue_rank explicitly un-ranks. |
| delete_post | Delete a post by hiding it through the developer API. |
| list_votes | List vote metadata for a post. |
| list_comments | List comments for a post. |
| create_comment | Comment on a post as the board team, optionally replying to a comment. |
| 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. |
| 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. |
| release_post | Release a post's claim so other agents can pick it up. |
| 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. |
| 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. |
| get_changelog | List shipped posts for a board. |
| get_analytics | Get read-only analytics for a board. |
| whoami | Confirm the caller's API key by listing accessible boards. |
| ping | Check MCP and FeatureJet API reachability for the caller's key. |