Project memory and a control plane for AI coding agents, over MCP.
Déduit des transports déclarés par cette annonce (stdio). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu dans le code que npm livre réellement, au moment de l’analyse. Le paquet n’a jamais été exécuté. Les outils enregistrés dynamiquement à l’exécution, ou cachés dans du code empaqueté ou minifié, peuvent passer inaperçus — c’est donc un plancher de la surface d’outils, pas un recensement complet.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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…
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
search_notesFull-text search across notes for a project.Full-text search across notes for a project.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
get_contextGet context by key or list all context for a project.Get context by key or list all context for a project.
Aucun schéma d’entrée n’a été publié pour cet outil.
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…
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
get_blockersList all blocked tasks with what's blocking them.List all blocked tasks with what's blocking them.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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).
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
report_failureAucune description publiéeCet outil n’a publié aucune description. Forge n’en invente pas.
escalateAucune description publiéeCet outil n’a publié aucune description. Forge n’en invente pas.
release_taskAucune description publiéeCet outil n’a publié aucune description. Forge n’en invente pas.
review_taskAucune description publiéeCet outil n’a publié aucune description. Forge n’en invente pas.
resolve_needs_humanAucune description publiéeCet outil n’a publié aucune description. Forge n’en invente pas.
35 outils sur 40 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
Project memory and a control plane for AI coding agents, over MCP.
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
L'exploration s'est arrêtée à la limite de 60 paquets. Le reste de l'arbre n'a jamais été résolu.
36 autres paquets résolus ne sont pas dessinés ici (limite d'affichage : 24). Toute dépendance porteuse d'un avis de sécurité est dessinée quelle que soit la limite. Inventaire complet (SBOM CycloneDX)
76 dépendances déclarées ne sont jamais arrivées dans l'arbre. Elles manquent à la résolution de Forge, pas au paquet.
+64 de plus non listées. Les comptes par motif ci-dessus les couvrent toutes.
Non suivies : peerDependencies. Cet arbre ne couvre que les dépendances d'exécution ; ce qu'elles entraînent n'a jamais été résolu.