Koskamo

FeatureJet MCP MCP server

A hosted MCP server that proxies the FeatureJet public API, allowing AI agents to manage feedback boards. Agents can list planned requests, claim items from a queue, implement features, attach evidence, and update post statuses, effectively turning user feedback into an automated development workflow.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by FeatureJet
MCP endpoint (Streamable HTTP)
https://mcp.featurejet.com/mcp
Vendor documentation

What you can do with it

  • List top-voted planned posts from a feedback board
  • Claim and implement user requests via an atomic queue
  • Attach implementation evidence like commits or PRs
  • Update post status to shipped and notify voters
Tools advertised by the last live check:
  • list_boards
  • get_board
  • create_board
  • publish_board
  • unpublish_board
  • list_posts
  • get_post
  • create_post
  • update_post
  • delete_post
  • list_votes
  • list_comments
  • create_comment
  • get_queue
  • claim_post
  • release_post
  • add_evidence
  • propose_status
  • get_changelog
  • get_analytics
  • whoami
  • ping

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http featurejet-mcp https://mcp.featurejet.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add featurejet-mcp --url https://mcp.featurejet.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable featurejet-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "featurejet-mcp": {
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "featurejet-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.featurejet.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start featurejet-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "featurejet-mcp": {
      "type": "http",
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http featurejet-mcp https://mcp.featurejet.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "featurejet-mcp": {
      "url": "https://mcp.featurejet.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "featurejet-mcp": {
      "serverUrl": "https://mcp.featurejet.com/mcp"
    }
  }
}

Do you run FeatureJet MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing