MCP planning server for AI agents — plan management, full-text search, and task lifecycle
Local Intelligent MCP Planning Server — A document and planning layer for AI assistants. No subscriptions, no cloud. Point limps at any folder (local, synced, or in git). One shared source of truth across Claude, Cursor, Codex, and any MCP-compatible tool. Environment Variables Obsidian Compatibility Creating a feature plan That's it. Your AI assistant now has access to your documents via HTTP…
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.
create_planNo description publishedThis tool published no description. Forge does not invent one.
update_task_statusNo description publishedThis tool published no description. Forge does not invent one.
get_next_taskNo description publishedThis tool published no description. Forge does not invent one.
configure_scoringNo description publishedThis tool published no description. Forge does not invent one.
search_docsNo description publishedThis tool published no description. Forge does not invent one.
list_docsNo description publishedThis tool published no description. Forge does not invent one.
reindex_docsNo description publishedThis tool published no description. Forge does not invent one.
create_docNo description publishedThis tool published no description. Forge does not invent one.
update_docNo description publishedThis tool published no description. Forge does not invent one.
delete_docprivilegedNo description publishedThis tool published no description. Forge does not invent one.
process_docNo description publishedThis tool published no description. Forge does not invent one.
process_docsNo description publishedThis tool published no description. Forge does not invent one.
list_plansNo description publishedThis tool published no description. Forge does not invent one.
list_agentsNo description publishedThis tool published no description. Forge does not invent one.
get_plan_statusNo description publishedThis tool published no description. Forge does not invent one.
check_stalenessNo description publishedThis tool published no description. Forge does not invent one.
check_driftNo description publishedThis tool published no description. Forge does not invent one.
infer_statusNo description publishedThis tool published no description. Forge does not invent one.
get_proposalsNo description publishedThis tool published no description. Forge does not invent one.
apply_proposalNo description publishedThis tool published no description. Forge does not invent one.
graphNo description publishedThis tool published no description. Forge does not invent one.
analyzeNo description publishedThis tool published no description. Forge does not invent one.
0 of 22 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.
Local Intelligent MCP Planning Server — A document and planning layer for AI assistants. No subscriptions, no cloud. Point limps at any folder (local, synced, or in git). One shared source of truth across Claude, Cursor, Codex, and any MCP-compatible tool. Environment Variables Obsidian Compatibility Creating a feature plan That's it. Your AI assistant now has access to your documents via HTTP transport. The folder can be anywhere—local, synced, or in a repo; limps does not require a git…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.