pi-durabletask-mcp

MCPcommunity

v0.7.12NyarlathotepppppMITUpdated 2d agonpm GitHub

Multi-provider Pi agent teams over MCP with parallel delegates, coordination, steering, and optional crash recovery

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

13GitHub stars

2d agoLast update

Package

AuthorNyarlathoteppppp

LicenseMIT

Version0.7.12

Sourcenpm+mcp-registry

npmpi-durabletask-mcp

GitHubNyarlathoteppppp/pi-durabletask-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface18 tools · 2 privileged

Security scan✓ Cleanv0.7.12 · todayHow well does this scan work?

EvalsNone

IndexedOct 10, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

18 tools · 2 privileged

Statically extracted from the published packagev0.7.12 · 23h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

statusCheck a background pi session. Returns state, turn count, tools used, latest text, and any

Check a background pi session. Returns state, turn count, tools used, latest text, and any

No input schema was published for this tool.

steerRedirect a running pi agent mid-task. The message lands after its current tool call finishes,

Redirect a running pi agent mid-task. The message lands after its current tool call finishes,

No input schema was published for this tool.

waitWait for delegates without polling in a loop. until: "progress" (default) returns after a new

Wait for delegates without polling in a loop. until: "progress" (default) returns after a new

No input schema was published for this tool.

answerAnswer a pending Pi extension UI question. Get requestId from questions[].id in status or wait.

Answer a pending Pi extension UI question. Get requestId from questions[].id in status or wait.

No input schema was published for this tool.

follow_upSend another prompt to a delegate that has already finished, keeping everything it read

Send another prompt to a delegate that has already finished, keeping everything it read

No input schema was published for this tool.

abortStop a running pi session. Partial output stays readable via `status`.

Stop a running pi session. Partial output stays readable via `status`.

No input schema was published for this tool.

sessionsList pi sessions held by this server, running and finished, plus finished durable sessions

List pi sessions held by this server, running and finished, plus finished durable sessions

No input schema was published for this tool.

forgetDrop a finished session from the review history, freeing its id for reuse.

Drop a finished session from the review history, freeing its id for reuse.

No input schema was published for this tool.

delegate_start_batchLaunch caller-approved tasks by zero-based taskIndexes (omit for all unlaunched). Started tasks run once; startup failures can be retried.

Launch caller-approved tasks by zero-based taskIndexes (omit for all unlaunched). Started tasks run once; startup failures can be retried.

No input schema was published for this tool.

delegate_waitNo description published

This tool published no description. Forge does not invent one.

delegate_getGet one launched child's full report, state and follow-up readiness (without renewing quotas), including questions, failures and save diagnostics. store() reports within the SDK's storage limits; print only the conclusions/references the caller needs. Original savedTo files remain independent of su…

Get one launched child's full report, state and follow-up readiness (without renewing quotas), including questions, failures and save diagnostics. store() reports within the SDK's storage limits; print only the conclusions/references the caller needs. Original savedTo files remain independent of su…

No input schema was published for this tool.

delegate_follow_upAsk a finished child launched by this coordinator a targeted question, preserving its history/model/tools.

Ask a finished child launched by this coordinator a targeted question, preserving its history/model/tools.

No input schema was published for this tool.

handoffHand a Pi session over between Claude/Codex windows. save (when the user asks to hand over): record

Hand a Pi session over between Claude/Codex windows. save (when the user asks to hand over): record

No input schema was published for this tool.

initOptional setup diagnostics: reports model availability, provider authentication, permissions and budgets.

Optional setup diagnostics: reports model availability, provider authentication, permissions and budgets.

No input schema was published for this tool.

modelsList models this delegate may use from pi's available providers after model filters.

List models this delegate may use from pi's available providers after model filters.

No input schema was published for this tool.

spawnprivilegedDelegate a task to a pi agent running in the background. Returns a sessionId immediately, so

Delegate a task to a pi agent running in the background. Returns a sessionId immediately, so

No input schema was published for this tool.

spawn_batchprivilegedFan out several delegates in one call. Each task inherits the batch-level model, cwd, tools

Fan out several delegates in one call. Each task inherits the batch-level model, cwd, tools

No input schema was published for this tool.

runDelegate a task to a pi agent and wait for the final answer. Blocks until done.

Delegate a task to a pi agent and wait for the final answer. Blocks until done.

No input schema was published for this tool.

17 of 18 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Multi-provider Pi agent teams over MCP with parallel delegates, coordination, steering, and optional crash recovery

Keywords

mcpmcp-servermodel-context-protocolpipi-coding-agentcoding-agentsubagentdelegateclaude-codellmopenrouterdeepseekgrokcodex

Alternatives

Comparing tool surfaces…

Tools exposed

18 tools · 2 privileged · observed 2026-10-21 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

status
steer
wait
answer
follow_up
abort
sessions
forget
delegate_start_batch
delegate_wait
delegate_get
delegate_follow_up
handoff
init
models
spawnpriv
spawn_batchpriv
run

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-21 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.6.7
@earendil-works/chord1.0.01 dependency
- esbuild0.28.2
@modelcontextprotocol/sdk1.32.117 dependencies
- ajv8.20.0+4 not drawn
- zod4.6.7shown above
- cors2.8.6+2 not drawn
- hono4.13.13
- jose6.2.13
- express5.3.0incomplete+18 not drawn
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete
- eventsource3.0.7incomplete
- content-type1.0.5
- pkce-challenge5.0.1
- @hono/node-server2.1.5
- json-schema-typed8.0.2
- eventsource-parser3.1.1
- express-rate-limit8.7.1incomplete
- zod-to-json-schema3.25.2
@earendil-works/pi-durable1.0.0+2 not drawn2 dependencies
- diff8.0.4
- typebox1.3.27
@earendil-works/pi-coding-agent1.0.0+19 not drawn3 dependencies
- diff8.0.4shown above
- typebox1.3.27shown above
- cross-spawn7.0.6incompleteshown above

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

74 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 74

parseurl ^1.3.3 — required by express@5.3.0package cap reached
statuses ^2.0.1 — required by express@5.3.0package cap reached
encodeurl ^2.0.0 — required by express@5.3.0package cap reached
mime-types ^3.0.0 — required by express@5.3.0package cap reached
proxy-addr ^2.0.8 — required by express@5.3.0package cap reached
body-parser ^2.3.0 — required by express@5.3.0package cap reached
escape-html ^1.0.3 — required by express@5.3.0package cap reached
http-errors ^2.0.0 — required by express@5.3.0package cap reached
on-finished ^2.4.1 — required by express@5.3.0package cap reached
content-type ^2.0.0 — required by express@5.3.0package cap reached
finalhandler ^2.1.0 — required by express@5.3.0package cap reached
range-parser ^1.2.1 — required by express@5.3.0package cap reached

+62 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.