Project memory and a control plane for AI coding agents, over MCP.
Inferido de los transportes que declara este listado (stdio). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.
La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.
Leído del código que npm publica realmente, en el momento del análisis. El paquete nunca se ejecutó. Las herramientas registradas dinámicamente en tiempo de ejecución, o escondidas en código empaquetado o minificado, pueden pasarse por alto — así que esto es un mínimo de la superficie de herramientas, no un censo 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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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…
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
search_notesFull-text search across notes for a project.Full-text search across notes for a project.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
get_contextGet context by key or list all context for a project.Get context by key or list all context for a project.
No se publicó ningún esquema de entrada para esta herramienta.
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…
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
get_blockersList all blocked tasks with what's blocking them.List all blocked tasks with what's blocking them.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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).
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
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.
No se publicó ningún esquema de entrada para esta herramienta.
report_failureSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
escalateSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
release_taskSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
review_taskSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
resolve_needs_humanSin descripción publicadaEsta herramienta no publicó ninguna descripción. Forge no se la inventa.
35 de 40 herramientas publicaron una descripción.
Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.
Project memory and a control plane for AI coding agents, over MCP.
Los nombres enlazados abren el índice de Forge con todas las entradas que se observó que exponen esa herramienta. Ver todas las herramientas indexadas.
El rastreo se detuvo en el límite de 60 paquetes. El resto del árbol nunca se resolvió.
Hay 36 paquetes resueltos más que no se dibujan aquí (límite de visualización: 24). Toda dependencia con avisos de seguridad se dibuja aunque se supere el límite. Inventario completo (SBOM CycloneDX)
76 dependencias declaradas nunca llegaron al árbol. Faltan en la resolución de Forge, no en el paquete.
+64 más sin listar. Los recuentos por motivo de arriba las incluyen todas.
No se siguen: peerDependencies. Este árbol cubre solo dependencias en tiempo de ejecución, así que lo que estas arrastren nunca se resolvió.