Developer-tools MCP server
Docmancer
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 12
- 5
- 3
- 0
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- docmancer@0.9.17
- Registry
- pypi
- Published
- Aug 13, 2026
- Integrity
sha256-/FaHDDcA8y3J1ISHIvYze6XEjS4u6tezMN0JOdbkM1w=- Analyzer
- modelara v0.1.8 · policy not recorded
- Repository
- https://github.com/docmancer/docmancer
20 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
ask_memorydocmancer:tool:ask_memoryObserved interface and hashesREAD-ONLY: recall one bounded bundle of everything local memory knows about a task, combining mandatory policy, curated memory, and supporting harvested agent evidence in priority order. This is the default recall tool and the right first call when you do not already know which store holds the answer; search_memory and search_evidence each cover only one store. Local and free by default. Returns an empty bundle rather than an error when nothing relevant exists, so an empty result means the memory is genuinely silent. Parameters: task is the natural-language task or question to recall for; answer defaults to false and returns the raw bundle, and setting it true spends a configured provider call, which may leave the machine, to produce a grounded cited answer; mode sets that answer's verbosity to concise, normal, or thorough and is ignored when answer is false; token_budget bounds the bundle size in approximate tokens (default 4000); limit caps how many supporting evidence items are considered (default 12); include_history adds superseded evidence; agent is the requesting agent identifier recorded for attribution (default mcp-client); project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the mandatory policy, curated memory, and evidence sections, each carrying source citations, plus the generated answer when answer is true. Input schemasha256:9941bb1c8f5560062bdff9e3ac96176ab3b1b1ca25e5518194f85ea8dc2f3017Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
canonical_memorydocmancer:tool:canonical_memoryObserved interface and hashesREAD-ONLY: read the machine-wide canonical memory, which is what docmancer has reconciled about this user across every agent and project. Local disk read, machine-wide, so it takes no project_path. Call it before asking the user something they may already have told another agent. Not a search tool: it returns whole prepared sections rather than matches, so use search_memory or ask_memory to look something up. To change what it returns, use pin_memory rather than edit_memory. Parameters: section selects one of about (who the user is), preferences (how they want to work), working-principles (cross-project rules), active-projects (what they are working on), or canonical-memory (a description of the store itself); omit section entirely for a status summary of every section. Returns, with a section, that section split into its pinned zone (durable, survives reconciliation) and its generated zone (rewritten automatically), plus content_hash and revision id. Without a section, returns per-section presence and pinned-line counts. Input schemasha256:838b7c4525fe15c519f5b7e139c06385a3d70dfa7a5a1088291b13e20d5f3b4cOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
common_memorydocmancer:tool:common_memoryObserved interface and hashesREAD-ONLY: list the memories that recur across two or more independent agent harnesses. This is a local disk read over already-harvested evidence; docmancer's own generated integration copies are excluded so they cannot manufacture agreement. Recurrence is evidence of salience, not proof of correctness, so treat the result as a signal worth checking rather than settled truth. Takes no query: it returns the whole recurring set. Use search_evidence to look something specific up instead. Parameters: project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns a list of objects describing each recurring memory and the harnesses it was seen in. Returns [] when nothing recurs. Input schemasha256:8e147a1b6f9b9ba0f83fd2f428f0e944452053abc33a9106137b19f24feff516Output schemasha256:8841f249a701b52df1e00129927db4fb9e94a7e6d0381ba0499a494749a4e25eDescription hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
context_deliverydocmancer:tool:context_deliveryObserved interface and hashesREAD-ONLY: show, per agent, whether context is actually reaching it, listing each supported agent's integration mode, hook installation status, and the revision and hash of the last context bundle it was observed to receive. Local disk read with no side effects. This is the delivery question, so use it to diagnose why one agent seems to be missing context that another has. It is one of three context tools: context_status answers what the current context revision contains and how fresh it is, and context_projection renders the actual text one agent would receive. Read-only across all three; installing hooks and refreshing context are deliberately human-only CLI or local-web operations. Parameters: project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns a list with one row per agent giving its integration mode, hook status, and last delivered revision and hash. A stale or absent revision on one row is the signal to look for. Input schemasha256:8d23484b3dbf06faf6fa71f8e7c188fa4c57c9ab8113f93adaaef3316ed64f2aOutput schemasha256:3753053c51cb6bf8240d98be9a676669b73c3156f6b7b820105cd219a5ac5ae4Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
context_projectiondocmancer:tool:context_projectionObserved interface and hashesREAD-ONLY: render the actual bounded context text one named agent would receive, linked to the current revision. Local disk read that renders without writing, refreshing, or delivering anything, so it is safe to preview repeatedly. This is the show-me-the-content question, so use it to check what an agent will actually see before installing or debugging an integration. It is one of three context tools: context_status reports the revision and its freshness, and context_delivery reports whether each agent is receiving it. Refresh, rollback, adopt, and retire are human-only CLI or local-web operations. Parameters: agent is the required target agent identifier, and the projection is shaped for that agent's integration; token_budget bounds the rendered size in approximate tokens (default 2000), so raising it returns more content and lowering it truncates by priority; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the rendered projection text and the revision it was built from. Input schemasha256:a39f94591c123e6a758a5fa7674aa3085bacc9fb96ddd76172c654df877f28b4Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
context_statusdocmancer:tool:context_statusObserved interface and hashesREAD-ONLY: inspect the consolidated Context itself, reporting its current revision id, how fresh it is, which sources are excluded, and its cluster metadata. Local disk read with no side effects. This is the what-and-how-fresh question, so use it to decide whether the context an agent is working from is stale or is missing something on purpose. It is one of three context tools: context_delivery answers whether each agent is actually receiving it, and context_projection renders the actual text one agent would receive. Refresh, rollback, adopt, and retire are deliberately human-only CLI or local-web operations, so no MCP tool can change what this reports. Parameters: project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the current revision, its scope and freshness, the active exclusions, and cluster metadata. Input schemasha256:db308f58ce83dbd7d43d9624dbb367f8ebc1e14aeb9876bcb7e81fe1a7f0d8c2Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
decision_timelinedocmancer:tool:decision_timelineObserved interface and hashesREAD-ONLY: show the append-only history of how memory changed over time, with a human-readable diff per entry. Local disk read over a log that is only ever appended to, so nothing here can be rewritten and the record is trustworthy. Use it to answer when and how a memory changed, or to recover text that an edit replaced. Newest entries come first. This is history, not content: use search_memory or read_memory for what a file says now. Parameters: file_id restricts the timeline to one memory file's own history, which is the usual way to trace a single decision; operation restricts it to one kind of change, one of create, edit, move, duplicate, trash, restore, pin, or reconcile; limit caps how many entries come back (default 100); project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Omit every filter for the whole recent history. Returns a list of entries with the operation, timestamp, affected file, revision ids, and a readable diff. Input schemasha256:fba385e282396d609bf5126e37c1d5795649372e9b8813be1d6d517b74f584b0Output schemasha256:0d4278519fef586eb49e608a7fa626d779b322d128e5f71de3aedc3effcacb02Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
duplicate_memorydocmancer:tool:duplicate_memoryObserved interface and hashesMUTATING: copy one curated memory file to a new path under a new stable identity. Writes to local disk and appends to the change timeline. The original is left untouched, and the copy gets its own docmancer://memory address and its own history, so the two diverge from here and editing one does not affect the other. Use it to fork an existing memory into a variant. Use move_memory instead when the original should not survive. Not idempotent: calling it twice with the same new_relative_path fails on the second call rather than creating a second copy. Parameters: address identifies the file to copy; new_relative_path is the copy's path in the tree, including the .md suffix, and must not already exist; expected_hash is the source file's current content_hash from read_memory, which guards against copying a revision you have not seen; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the new copy's address, path, content_hash, and revision id. Input schemasha256:4153ffe8bff2827c8f2aa7818e7336ab16eeb35aada4533c02539ba933a6c47bOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
edit_memorydocmancer:tool:edit_memoryObserved interface and hashesMUTATING: replace the body of one existing curated memory file while preserving its frontmatter, address, and history. Writes to local disk and appends to the change timeline. The write is guarded: a stale expected_hash fails without changing anything and returns a structured error naming the re-read-and-retry next action, so concurrent edits cannot be lost. Read the file first to obtain the hash. Not for canonical memory about the user, which reconciliation regenerates: use pin_memory there. Not for creating a new file: use write_memory. Parameters: address identifies the file to edit; text is the complete replacement Markdown body, which overwrites rather than appends; expected_hash is the content_hash from the read that produced text; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the address and the new content_hash and revision id. Input schemasha256:49e1802b41e9e6243697884defa338c12ac02d0d8fd3af77006f187387956147Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
evidence_statusdocmancer:tool:evidence_statusObserved interface and hashesREAD-ONLY: report whether the local evidence index that search_evidence queries is present and populated, including its on-disk path and its source and section counts. Local only, and takes no parameters. Call it first when search_evidence returns nothing, to tell an empty index apart from a genuine miss; an empty one means the user has not run `docmancer setup` yet. Not for curated memory health, which is context_status, nor for per-agent delivery, which is context_delivery. Returns an object with the index path and the number of indexed sources and sections. Input schemasha256:ad4cdab07ecbfba231120cbfd1d76c757555931c7b38e92127cf04bcc8e9f1b9Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | No change observed | |
move_memorydocmancer:tool:move_memoryObserved interface and hashesMUTATING and DESTRUCTIVE at the old path: move or rename one curated memory file. Writes to local disk and appends to the change timeline. The file's stable docmancer://memory address survives the move, so existing references by address keep working, but the old relative path stops resolving and anything referring to it by path breaks. Guarded by expected_hash, so a stale hash fails without changing anything. The body is untouched: use edit_memory to change content, or duplicate_memory to copy rather than move. Parameters: address identifies the file to move; new_relative_path is its destination path in the tree, including the .md suffix, and renaming is just a move within the same directory; expected_hash is the file's current content_hash from read_memory; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the unchanged address, the new path, and the new revision id. Input schemasha256:e7ddac0ffe4ecc341c80830f9388909480f1bed2191f9f496d6b3470746d8d3bOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
pin_memorydocmancer:tool:pin_memoryObserved interface and hashesMUTATING: pin one durable line into a canonical memory section. Writes to local disk, machine-wide, so it takes no project_path. The pinned zone is the ONLY part of a canonical section that survives automatic reconciliation, so use this, not edit_memory or write_memory, for any correction, standing preference, or fact the reconciler got wrong or left out. Idempotent: pinning the same line twice changes nothing. Use unpin_memory to reverse it, and canonical_memory to see the result. Parameters: section selects which canonical section to pin into, one of about, preferences, working-principles, or active-projects; text is the complete line to pin, which should read as a standalone statement because it is stored verbatim. Returns an object with the section, its path, and the updated pinned-line count. Input schemasha256:20aa653bd1bc628a10fcc140d0bab1df99f728027b52f61e17068e50415d908aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
read_memorydocmancer:tool:read_memoryObserved interface and hashesREAD-ONLY: read one curated memory file in full, resolved by stable address, relative path, or exact title. Local disk read with no side effects. Ambiguous title or path matches return every candidate address rather than guessing, so a caller can retry with an exact address. This is also how you obtain the content_hash that edit_memory, move_memory, duplicate_memory, and trash_memory all require. Use search_memory first when you do not already know which file you want. Parameters: address is the docmancer://memory/<id> address, the relative path, or the exact title; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the body, frontmatter, address, content_hash, and revision id, or a candidates list when the address was ambiguous. Input schemasha256:87fea8ecf5ae3e00f97c57566eaa2d8d75cca694323fd13762cb2721eb166a3dOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
restore_memorydocmancer:tool:restore_memoryObserved interface and hashesMUTATING: undo a trash_memory call by restoring one curated memory file from its restore token. Writes to local disk and appends to the change timeline. The file returns to its original path with its address and history intact, so references by address resume working. A token is single-use and only valid for the tree it was issued against, so a spent or foreign token fails without changing anything. Restoring is only possible while the token is known: there is no way to browse trash from MCP. Parameters: restore_token is the exact token returned by the trash_memory call being undone; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the restored address, path, and revision id. Input schemasha256:d9d7a72a2dfb0e0e38b48e9719c49c829e837fbb16cdf8bb0a6a03dc0ed15193Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
search_docsdocmancer:tool:search_docsObserved interface and hashesREAD-ONLY: search the local documentation index built by `docmancer docs add`, covering library, API, and vendor documentation the user chose to ingest. Runs entirely locally; no network call, so it only ever returns docs already added on this machine and returns [] when none have been. Use it for version-specific library or vendor behaviour. Not for anything about this user or their projects: use search_memory, search_evidence, or ask_memory for that. Parameters: query is the natural-language text to match against the indexed documentation; limit caps the number of results (default 8). Returns a list of objects with the matching excerpt, its source document, and a relevance score. Input schemasha256:abb354f0d382f7d84d2b7ff3df9fba0b5e644ccb85d724ef251ac5563d3482d8Output schemasha256:64ba9e9c4ade05fdefc6a97819fdc4b9bea54c0b03ee7c7c4fe46b3cc8e55ed2Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
search_evidencedocmancer:tool:search_evidenceObserved interface and hashesREAD-ONLY: semantic search over the raw evidence index, meaning the memory, instruction, and rule files that other coding agents already wrote on this machine and that docmancer harvested. Runs entirely locally against the embedding index; no network call, no cost. Use it to find what an agent originally recorded, with a relevance score and the file it came from. Not for curated memory you or an agent deliberately wrote: that lives in a separate tree, so use search_memory for it, or ask_memory to get both at once. Parameters: query is the natural-language text to match; limit caps the number of results (default 8); include_history adds superseded evidence to the active evidence; expand_relations adds items linked to a direct match. Returns a list of objects with score, excerpt, source_path, scope, kind, lifecycle_state, and a docmancer://record/<id> record_uri. Returns [] when nothing matches. Input schemasha256:d66f51ff1a20b41fc1ee9081587c58c8d020d4f5f06e70eb481ce4307ea79aa8Output schemasha256:3a30d5fbeac0aa251d4089004d8c0556824f908dec83a8b7738c732a6867f61dDescription hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
search_memorydocmancer:tool:search_memoryObserved interface and hashesREAD-ONLY: lexical search over the curated memory tree, meaning the decisions, constraints, and conventions deliberately written by the user or an agent. Local disk read, no embedding call, no cost. Only active entries are searched; archived and trashed files are excluded. Returns [] rather than an error when nothing is relevant or the tree is empty, so an empty result is a real answer and not a failure. Not the same store as search_evidence, which searches raw harvested agent files instead; use ask_memory when you want both stores plus mandatory policy in one bundle. Parameters: query is the natural-language text to match; limit caps the number of results (default 8, capped at 50); project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns a list of objects with the docmancer://memory address, title, excerpt, authority, and source_type. Pass an address to read_memory for the full file. Input schemasha256:a36d823800a06a39df8781c400e7cc571624bcdd47a6dca68ae7621237104531Output schemasha256:d2a09a641ffffed655102c7aac0d14e98fdf569532c910245e331a4036ae7b41Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
trash_memorydocmancer:tool:trash_memoryObserved interface and hashesDESTRUCTIVE BUT REVERSIBLE: move one curated memory file to trash so it stops being read or recalled. Writes to local disk and appends to the change timeline. Nothing is erased: the call returns a restore_token that restore_memory consumes to bring the file back, so keep that token in your reply if the user might change their mind. Guarded by expected_hash, so a stale hash fails without trashing anything. Prefer setting status='archived' with write_memory when the file should stay readable but stop being recalled. Parameters: address identifies the file to trash; expected_hash is its current content_hash from read_memory, confirming you are discarding the revision you actually saw; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the trashed address and the restore_token needed to undo it. Input schemasha256:6aa5f93c4aa5ff99ecc80e9ee2ac70b46cf90c2b37291b59d5337d412b16981cOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
unpin_memorydocmancer:tool:unpin_memoryObserved interface and hashesMUTATING and DESTRUCTIVE: permanently remove pinned lines from a canonical memory section by case-insensitive substring match, with no undo and no restore token. Writes to local disk, machine-wide, so it takes no project_path. A substring can match more lines than intended, so read the section with canonical_memory first and pass text specific enough to hit only what you mean. Fails without changing anything when nothing matches, which makes a dry run safe. Only pinned lines are removable; generated content is rewritten by reconciliation instead. Parameters: section selects which canonical section to modify, one of about, preferences, working-principles, or active-projects; text is the case-insensitive substring, not a whole line and not a pattern, identifying the pinned lines to delete. Returns an object with the section and how many lines were removed. Input schemasha256:8f92bc5323a896c3b3eadc0ab00988afb50938f551623190ad064d6205e51988Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 | |
write_memorydocmancer:tool:write_memoryObserved interface and hashesMUTATING: create or update one curated memory file in the memory tree, addressed as docmancer://memory/<id>. Writes to local disk and appends to the change timeline; never silently clobbers, because the expect guard decides whether an existing file may be replaced. Use it to record a durable decision, constraint, or convention. Not for correcting the reconciled canonical memory about the user, which is regenerated and would discard the edit: use pin_memory for that. To change only the body of an existing file, prefer edit_memory. Parameters: relative_path is the file's path in the tree and must include the Markdown suffix; text is the full Markdown body; expect is the write guard, 'absent' (default) to create only and fail if the path exists, or the current content_hash to permit a guarded overwrite; memory_type, scope, authority, status, and curation_origin are frontmatter labels described in the schema; project_id names the owning project; sources lists backing file paths or URLs; tags lists retrieval labels; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the stable address, the new content_hash, and the revision id, all of which later guarded calls need. Input schemasha256:ae306bd98486d8a5082c9ebcdcc2778d0ba50ef0c4915018dc465838f08fdab6Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 0.9.15 | 0.9.16 |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 0.9.16 0.9.17PASS0 added0 removed0 schema0 write0 destructive0 unknown
- 0.9.15 0.9.16REVIEW0 added0 removed3 schema0 write0 destructive0 unknown