Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
QodFlow 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.
99/100
trust score
25
downloads a day
local
runs on your machine
828
downloads in 30d
What it does
Shared kanban board with SLA tracking: AI agents claim jobs, report progress, ask humans to decide.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'QODFLOW_API_TOKEN=${QODFLOW_API_TOKEN}' --transport stdio qodflow-mcp '--' npx -y qodflow-mcp
# 2 — ask your agent for something these tools do
# list_jobs, list_stages, create_job and 16 more
It needs QODFLOW_API_TOKEN: this reads it from your environment, so export it first.
QodFlow costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
QOAll 1 server
qodflow1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 QodFlow 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.
Claude Codedeclared by this listing
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. Claude Code reads QODFLOW_API_TOKEN (Personal Access Token from QodFlow Settings > API Keys (starts with qf_live_). Scoped and revocable) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx QODFLOW_API_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'QODFLOW_API_TOKEN=${QODFLOW_API_TOKEN}' --transport stdio qodflow-mcp '--' npx -y qodflow-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: QODFLOW_API_TOKEN — Personal Access Token from QodFlow Settings > API Keys (starts with qf_live_). Scoped and revocable.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
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.
What you approve
19 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 jobs in the QodFlow workspace bound to this token. Returns the most recent first. Cursor-paginated.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| cursor | string | no | Pagination cursor from a previous response. |
List pipeline stages for the workspace. Each stage has an order, name, color, and SLA in days. Use stage IDs when referencing positions.
No parameter schema on file.
Create a new job in the workspace. Placed in the first stage unless stageId is provided. Requires the jobs:write scope on the token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | — |
| description | string | no | — |
| stageId | string | no | — |
| priority | string | no | — |
Update a job's title, description, priority, or PO number. To move a job between stages use move_job; to assign it use assign_job. Completed jobs are read-only: move_job it to an earlier stage first (the server returns 409 JOB_COMPLETED otherwise). Requires jobs:write.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| title | string | no | — |
| description | string | no | — |
| priority | string | no | — |
| poNumber | string | no | — |
Move a job to a different stage. Use list_stages to get stage IDs. Requires jobs:write.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| stageId | string | yes | — |
| reason | string | no | Optional short note on why the job moved; kept on the team's activity record. |
Assign a job to a team member, or pass assignedToId:null to unassign. Use list_members to get member IDs. Completed jobs are read-only: move_job it to an earlier stage first (the server returns 409 JOB_COMPLETED otherwise). Requires the mcp:assign scope. Available on every plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| assignedToId | string/null | yes | Member user id, or null to unassign. |
List all tags defined on the workspace. Requires tags:read.
No parameter schema on file.
List team members with their roles. Requires members:read.
No parameter schema on file.
Create a new tag for the workspace. Requires tags:write.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| color | string | no | — |
Rename a stage, change its SLA, or change its color. Requires stages:write.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| name | string | no | — |
| slaDays | integer | no | — |
| color | string | no | — |
Atomically claim a job for this agent so other agents won't pick it up. Includes a lease (default 30 min, max 240) so a crashed agent does not lock the job forever. Requires mcp:claim scope. Returns CONFLICT if already claimed by someone else with a fresh lease.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| leaseMinutes | integer | no | — |
| note | string | no | — |
Release a job this agent currently holds. Lets another actor pick it up. Requires mcp:claim.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| note | string | no | — |
Append a 280-character narration entry to the job's timeline so the human can see what this agent has been doing. Call this at every meaningful step — humans skim, agents forget. Requires mcp:claim.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| note | string | yes | — |
Ask the human team to pick one of 2-6 structured options. Creates a DecisionRequest that appears in their /my-tasks inbox. PREMIUM-plan only — FREE will receive PLAN_UPGRADE_REQUIRED with a structured upgrade prompt. Requires mcp:decide.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| question | string | yes | — |
| options | array | yes | — |
| ttlDays | integer | no | — |
Attach a 280-character note and optional external URL as evidence that work was completed. URLs must be http(s) and never target internal/private hosts — they are display-only, never fetched server-side. PREMIUM-plan only. Requires mcp:evidence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| note | string | yes | — |
| url | string | no | — |
Read the most recent timeline entries for a job (claim/release/progress/decision/evidence). Helpful when the agent restarts a conversation and needs to know what happened. Requires jobs:read.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
| limit | integer | no | — |
| cursor | string | no | — |
List open + recently resolved decision requests for a job. Use to poll for human response. Requires jobs:read.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
List evidence attached to a job. PREMIUM-plan only. Requires jobs:read.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jobId | string | yes | — |
Resolve a DecisionRequest you previously opened with request_human_decision. Use this when the human gave you the answer in your chat (not in the QodFlow board) — propagating it here keeps the board in sync. You MUST include humanResponseExcerpt with the human's actual reply (first 280 chars).…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| decisionId | string | yes | — |
| chosenOption | string | yes | — |
| humanResponseExcerpt | string | yes | — |
Free
$0 forever
- 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 QodFlow or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.2.0 · scanned 29 Oct 2026
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.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest0dfeb420fc1366277cdb1b0ae73dd9afefbe1b088a40699a7fe267c400381c84
Score vectorthreat 100 → client 99
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
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. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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
Integrityfirst-seen
Surface digest0dfeb420fc136627
Scanned2026-10-29
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.2.0. Pin a release below and the command asks for exactly that one.
0.2.0
29 Oct 2026
latestNo release note was published with this version.
0.1.3
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish QodFlow can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.