Project memory and a control plane for AI coding agents, over MCP.
Dedotto dai trasporti dichiarati da questo annuncio (stdio). Un client che non compare qui non è escluso — semplicemente Forge non è in grado di confermarlo.
La verifica conferma l’identità del publisher (la proprietà del repo), non la sicurezza del codice. L’analisi di sicurezza copre i CVE noti e gli script di installazione sospetti.
Letto dal codice che npm distribuisce davvero, al momento dell’analisi. Il pacchetto non è mai stato eseguito. Gli strumenti registrati dinamicamente a runtime, o nascosti in codice impacchettato o minificato, possono sfuggire — quindi questo è un limite inferiore della superficie di strumenti, non un censimento completo.
get_agent_instructionsReturns the recommended instructions for using mindpm effectively. Call this once if you are unsure how to use mindpm, or share it with the user to paste into other LLM clients.Returns the recommended instructions for using mindpm effectively. Call this once if you are unsure how to use mindpm, or share it with the user to paste into other LLM clients.
Per questo strumento non è stato pubblicato alcuno schema di input.
create_projectCreate a new project to track. Use this when starting a new project or when a user mentions a project that doesn't exist yet.Create a new project to track. Use this when starting a new project or when a user mentions a project that doesn't exist yet.
Per questo strumento non è stato pubblicato alcuno schema di input.
list_projectsList all tracked projects. Filter by status to see active, paused, completed, or archived projects.List all tracked projects. Filter by status to see active, paused, completed, or archived projects.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_project_statusGet a full overview of a project: active tasks, recent decisions, blockers, and last session summary. Great for getting up to speed.Get a full overview of a project: active tasks, recent decisions, blockers, and last session summary. Great for getting up to speed.
Per questo strumento non è stato pubblicato alcuno schema di input.
set_project_repo_pathSet or update the local git repository path for a project. Required for the session brief to include git activity (commits, branch, working-tree state) since the last session.Set or update the local git repository path for a project. Required for the session brief to include git activity (commits, branch, working-tree state) since the last session.
Per questo strumento non è stato pubblicato alcuno schema di input.
set_execution_defaultsSet the coding conventions and verification commands (build, unit, integration, lint) that go into every task brief for this project. Tasks can override individual commands with their own verification. These are hints for the executor: the verifier never runs them. It runs only the checks a human c…Set the coding conventions and verification commands (build, unit, integration, lint) that go into every task brief for this project. Tasks can override individual commands with their own verification. These are hints for the executor: the verifier never runs them. It runs only the checks a human c…
Per questo strumento non è stato pubblicato alcuno schema di input.
create_taskCreate a new task in a project. Proactively use this when the user mentions something that needs to be done, a bug to fix, or a feature to build. Link it to a spec (spec_id) to make it executable by an agent: it then starts in backlog until the spec is approved.Create a new task in a project. Proactively use this when the user mentions something that needs to be done, a bug to fix, or a feature to build. Link it to a spec (spec_id) to make it executable by an agent: it then starts in backlog until the spec is approved.
Per questo strumento non è stato pubblicato alcuno schema di input.
update_taskUpdate fields of a task. Proactively use this when priorities shift or new information comes in. Changing status directly is reserved for humans (actor human:*); agents move tasks with claim_task, submit_task, report_failure, escalate and release_task.Update fields of a task. Proactively use this when priorities shift or new information comes in. Changing status directly is reserved for humans (actor human:*); agents move tasks with claim_task, submit_task, report_failure, escalate and release_task.
Per questo strumento non è stato pubblicato alcuno schema di input.
list_tasksList tasks with filters. Defaults to showing non-completed tasks for the most recent active project.List tasks with filters. Defaults to showing non-completed tasks for the most recent active project.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_taskGet full detail for a specific task including sub-tasks, related notes, its spec criteria and its attempts.Get full detail for a specific task including sub-tasks, related notes, its spec criteria and its attempts.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_next_tasksPlanning view: what should be worked on next? Returns the highest priority ready or claimed tasks for a project. Executor agents use pick_task instead.Planning view: what should be worked on next? Returns the highest priority ready or claimed tasks for a project. Executor agents use pick_task instead.
Per questo strumento non è stato pubblicato alcuno schema di input.
log_decisionRecord a decision with reasoning and alternatives considered. Proactively use this when the user makes a technical decision, chooses between options, or settles a debate.Record a decision with reasoning and alternatives considered. Proactively use this when the user makes a technical decision, chooses between options, or settles a debate.
Per questo strumento non è stato pubblicato alcuno schema di input.
list_decisionsList decisions for a project. Filter by tags to find specific decisions.List decisions for a project. Filter by tags to find specific decisions.
Per questo strumento non è stato pubblicato alcuno schema di input.
add_noteAdd a note to a project or task. Proactively use this when the user shares context about architecture, bugs, ideas, research findings, or any important information worth remembering. Always specify the project parameter when you know which project is active.Add a note to a project or task. Proactively use this when the user shares context about architecture, bugs, ideas, research findings, or any important information worth remembering. Always specify the project parameter when you know which project is active.
Per questo strumento non è stato pubblicato alcuno schema di input.
search_notesFull-text search across notes for a project.Full-text search across notes for a project.
Per questo strumento non è stato pubblicato alcuno schema di input.
set_contextSet a key-value context pair for a project (upsert). Proactively use this when the user shares important project context like architecture decisions, config values, conventions, or constraints.Set a key-value context pair for a project (upsert). Proactively use this when the user shares important project context like architecture decisions, config values, conventions, or constraints.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_contextGet context by key or list all context for a project.Get context by key or list all context for a project.
Per questo strumento non è stato pubblicato alcuno schema di input.
start_sessionBegin a work session for a project. Returns the full project overview including last session's next_steps, active tasks, blockers, and recent decisions. Call this at the start of every conversation. For multi-project conversations, call once per project — after that, pass `project` explicitly on ev…Begin a work session for a project. Returns the full project overview including last session's next_steps, active tasks, blockers, and recent decisions. Call this at the start of every conversation. For multi-project conversations, call once per project — after that, pass `project` explicitly on ev…
Per questo strumento non è stato pubblicato alcuno schema di input.
end_sessionEnd a work session with a summary of what was accomplished and what to do next. Call this when the user is done working.End a work session with a summary of what was accomplished and what to do next. Call this when the user is done working.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_session_briefRead-only: what changed since the last session ended — commits, branch and working-tree state, task status changes, new blockers, decisions, and notes. Unlike start_session, this does not open a session or mark one as started.Read-only: what changed since the last session ended — commits, branch and working-tree state, task status changes, new blockers, decisions, and notes. Unlike start_session, this does not open a session or mark one as started.
Per questo strumento non è stato pubblicato alcuno schema di input.
queryExecute a read-only SQL query against the database. Only SELECT statements are allowed. Use this for custom queries not covered by other tools.Execute a read-only SQL query against the database. Only SELECT statements are allowed. Use this for custom queries not covered by other tools.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_project_summaryHigh-level summary of a project: total tasks by status, recent activity, open blockers, and upcoming priorities.High-level summary of a project: total tasks by status, recent activity, open blockers, and upcoming priorities.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_blockersList all blocked tasks with what's blocking them.List all blocked tasks with what's blocking them.
Per questo strumento non è stato pubblicato alcuno schema di input.
searchFull-text search (FTS5, ranked by relevance) across tasks, notes, decisions, specs and attempt root causes for a project.Full-text search (FTS5, ranked by relevance) across tasks, notes, decisions, specs and attempt root causes for a project.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_delivery_metricsDORA-inspired delivery metrics for a project: throughput, lead time, flow efficiency, and performance tier. Use to understand delivery health and trends.DORA-inspired delivery metrics for a project: throughput, lead time, flow efficiency, and performance tier. Use to understand delivery health and trends.
Per questo strumento non è stato pubblicato alcuno schema di input.
create_specDefine a spec: the objective, why it matters, the chosen approach, constraints and acceptance criteria an executor agent works against. Created as a draft; approve_spec makes its tasks workable. Architect or human only.Define a spec: the objective, why it matters, the chosen approach, constraints and acceptance criteria an executor agent works against. Created as a draft; approve_spec makes its tasks workable. Architect or human only.
Per questo strumento non è stato pubblicato alcuno schema di input.
update_specEdit a spec. Pass the version you read as expected_version; a stale version fails with version_conflict. Editing an approved spec republishes it: the version bumps and agents working on its tasks see spec_changed on their next heartbeat.Edit a spec. Pass the version you read as expected_version; a stale version fails with version_conflict. Editing an approved spec republishes it: the version bumps and agents working on its tasks see spec_changed on their next heartbeat.
Per questo strumento non è stato pubblicato alcuno schema di input.
approve_specApprove a draft spec so agents can work on its tasks. Medium and high risk need human:*; low risk also allows agent:architect. Moves linked backlog tasks with no open blockers to ready and writes specs/SPEC-<n>.md into the repo (a human commits it).Approve a draft spec so agents can work on its tasks. Medium and high risk need human:*; low risk also allows agent:architect. Moves linked backlog tasks with no open blockers to ready and writes specs/SPEC-<n>.md into the repo (a human commits it).
Per questo strumento non è stato pubblicato alcuno schema di input.
supersede_specReplace a spec with another one. Cancels the old spec's unfinished tasks; any live claim on them ends.Replace a spec with another one. Cancels the old spec's unfinished tasks; any live claim on them ends.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_specA spec with its acceptance criteria, linked tasks (status and attempts) and the active decisions that shaped it.A spec with its acceptance criteria, linked tasks (status and attempts) and the active decisions that shaped it.
Per questo strumento non è stato pubblicato alcuno schema di input.
pick_taskExecutor: return the next task to work on: ready, spec approved (or no spec), all blockers done, no live lease. Ordered by priority, then oldest. Does not claim; call claim_task next.Executor: return the next task to work on: ready, spec approved (or no spec), all blockers done, no live lease. Ordered by priority, then oldest. Does not claim; call claim_task next.
Per questo strumento non è stato pubblicato alcuno schema di input.
claim_taskExecutor: take exclusive ownership of a ready task. Returns a claim_token that authorizes every later write, the lease expiry, and the task brief. Heartbeat before the lease runs out or the claim expires and counts as a used attempt.Executor: take exclusive ownership of a ready task. Returns a claim_token that authorizes every later write, the lease expiry, and the task brief. Heartbeat before the lease runs out or the claim expires and counts as a used attempt.
Per questo strumento non è stato pubblicato alcuno schema di input.
get_task_briefEverything needed to execute a task in one read: task, spec and acceptance criteria, project conventions, verification commands, relevant decisions, dependencies and what previous attempts learned.Everything needed to execute a task in one read: task, spec and acceptance criteria, project conventions, verification commands, relevant decisions, dependencies and what previous attempts learned.
Per questo strumento non è stato pubblicato alcuno schema di input.
heartbeatExecutor: extend your lease by its original length and log the phase you are in. If spec_changed comes back true, the spec was revised since you claimed: re-read it with get_task_brief before continuing.Executor: extend your lease by its original length and log the phase you are in. If spec_changed comes back true, the spec was revised since you claimed: re-read it with get_task_brief before continuing.
Per questo strumento non è stato pubblicato alcuno schema di input.
submit_taskExecutor: hand finished work over for verification. Requires the branch, head commit SHA, files touched, a summary, and a result for every acceptance criterion on the task. Moves the task to needs_verification.Executor: hand finished work over for verification. Requires the branch, head commit SHA, files touched, a summary, and a result for every acceptance criterion on the task. Moves the task to needs_verification.
Per questo strumento non è stato pubblicato alcuno schema di input.
report_failureNessuna descrizione pubblicataQuesto strumento non ha pubblicato alcuna descrizione. Forge non se la inventa.
escalateNessuna descrizione pubblicataQuesto strumento non ha pubblicato alcuna descrizione. Forge non se la inventa.
release_taskNessuna descrizione pubblicataQuesto strumento non ha pubblicato alcuna descrizione. Forge non se la inventa.
review_taskNessuna descrizione pubblicataQuesto strumento non ha pubblicato alcuna descrizione. Forge non se la inventa.
resolve_needs_humanNessuna descrizione pubblicataQuesto strumento non ha pubblicato alcuna descrizione. Forge non se la inventa.
35 strumenti su 40 hanno pubblicato una descrizione.
I nomi e le descrizioni degli strumenti sono scritti dal publisher e mostrati alla lettera come testo inerte. Sono le stringhe che un client MCP passa a un modello, quindi Forge vi cerca schemi di prompt injection — ogni rilievo compare insieme all’analisi di sicurezza qui sopra. «Privilegiato» è una corrispondenza di parola chiave sul nome dello strumento, non una verifica di ciò che fa: un nome innocuo può comunque fare qualsiasi cosa.
Project memory and a control plane for AI coding agents, over MCP.
I nomi collegati aprono l’indice Forge di tutte le voci osservate esporre quello strumento. Sfoglia tutti gli strumenti indicizzati.
La scansione si è fermata al limite di 60 pacchetti. Il resto dell'albero non è mai stato risolto.
Altri 36 pacchetti risolti non vengono disegnati qui (limite di visualizzazione: 24). Ogni dipendenza con un avviso di sicurezza viene disegnata comunque. Inventario completo (SBOM CycloneDX)
76 dipendenze dichiarate non sono mai arrivate nell'albero. Mancano dalla risoluzione di Forge, non dal pacchetto.
+64 altre non elencate. I conteggi per motivo qui sopra le comprendono tutte.
Non seguite: peerDependencies. Questo albero copre solo le dipendenze di runtime, quindi ciò che queste comportano non è mai stato risolto.