Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Queueboard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Feedback boards for product teams: posts, votes, comments, agent work queue, changelog.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user queueboard-mcp '--' npx -y @reneturcios/queueboard mcp
# 2 — ask your agent for something these tools do
# list_boards, get_board, create_board and 19 more
Queueboard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Queueboard as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user queueboard-mcp '--' npx -y @reneturcios/queueboard mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
22 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List boards available to the caller's FeatureJet API key.
No parameter schema on file.
Get one board by slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Display name for the new board. |
| slug | string | yes | URL path segment for the new board (lowercase, hyphenated, unique). |
| description | no | Text description of the new 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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
Return a board to draft so its public URL stops serving it. Nothing is deleted; publish it again to bring it back.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
List posts for a board, optionally filtered by status, search, or tag.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| status | no | Filter posts by status. | |
| q | no | Free-text search query matched against posts. | |
| tag | no | Filter posts by this tag. | |
| limit | no | Maximum number of posts to return. | |
| offset | no | Number of posts to skip before returning results (paging). |
Get one post by board slug and post id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
Create a post on a board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| title | string | yes | Title of the new post. |
| body | no | Body text of the post. | |
| status | no | Initial status of the post. | |
| tags | no | Tags to attach to the post. |
Update mutable post fields; null queue_rank explicitly un-ranks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
| title | no | New title for the post. | |
| body | no | New body text for the post. | |
| status | no | New status for the post. | |
| tags | no | Replacement tags for the post. | |
| pinned | no | Whether the post is pinned. | |
| queue_rank | no | Owner-curated queue position (lower = sooner); null explicitly un-ranks the post. |
Delete a post by hiding it through the developer API.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
List vote metadata for a post.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
List comments for a post.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
Comment on a post as the board team, optionally replying to a comment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
| body | string | yes | Text of the comment. |
| parent_comment_id | no | Id of the comment being replied to, when this comment is a reply. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| limit | no | Maximum number of queued posts to return. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
| ttl_seconds | no | Claim lifetime in seconds (defaults to 3600, max 86400). | |
| agent_label | no | Label identifying the claiming agent. |
Release a post's claim so other agents can pick it up.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
| kind | string | yes | Kind of evidence: one of branch, commit, pr, transcript or url. |
| ref | string | yes | The evidence reference itself: branch name, commit hash, PR reference, transcript id or URL, according to kind. |
| label | no | Short label shown with the evidence. | |
| action_key | no | Optional key identifying the agent action this evidence belongs to. |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| post_id | integer | yes | Numeric id of the post. |
| status | string | yes | The status being proposed for the post. |
| note | no | Note explaining the proposed status change. | |
| action_key | no | Optional key identifying the agent action behind this proposal. |
List shipped posts for a board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
Get read-only analytics for a board.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
| period | no | Analytics period to report over. |
Confirm the caller's API key by listing accessible boards.
No parameter schema on file.
Check MCP and FeatureJet API reachability for the caller's key.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Queueboard or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Queueboard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.