Project memory and a control plane for AI coding agents, over MCP.
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
search_notesFull-text search across notes for a project.Full-text search across notes for a project.
No input schema was published for this tool.
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 input schema was published for this tool.
get_contextGet context by key or list all context for a project.Get context by key or list all context for a project.
No input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
get_blockersList all blocked tasks with what's blocking them.List all blocked tasks with what's blocking them.
No input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
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 input schema was published for this tool.
report_failureNo description publishedThis tool published no description. Forge does not invent one.
escalateNo description publishedThis tool published no description. Forge does not invent one.
release_taskNo description publishedThis tool published no description. Forge does not invent one.
review_taskNo description publishedThis tool published no description. Forge does not invent one.
resolve_needs_humanNo description publishedThis tool published no description. Forge does not invent one.
35 of 40 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.
Project memory and a control plane for AI coding agents, over MCP.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
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)
76 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+64 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.