Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Org Roam is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server for org-roam knowledge management. Provides AI agent tools for semantic search, note creation, and daily entries. Install with: pip install org-roam-mcp or curl -fsSL https://raw.githubusercontent.com/dcruver/org-roam-ai/main/install.sh | bash
Quickstart
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Org Roam as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Enhanced search with full context for RAG applications
No parameter schema on file.
Basic search across note titles and content
No parameter schema on file.
Read full content of a note by ID or path. Use this to retrieve note contents without searching.
No parameter schema on file.
Semantic vector search using AI embeddings to find conceptually related notes
No parameter schema on file.
Create a new org-roam note with optional structured formatting for videos
No parameter schema on file.
Add structured entry to daily note
No parameter schema on file.
Get content of daily note
No parameter schema on file.
Sync org-roam database to ensure latest data
No parameter schema on file.
Generate semantic embeddings for org-roam notes using org-roam-semantic. Processes notes missing embeddings or with stale embeddings.
No parameter schema on file.
Generate semantic embedding for a single org-roam note. Use after creating or updating a note instead of regenerating all embeddings.
No parameter schema on file.
Add an inbox entry to today
No parameter schema on file.
Create a person node with structured fields for tracking relationships and follow-ups
No parameter schema on file.
Create a project node with structured fields for tracking status and next actions
No parameter schema on file.
Create an idea node with a one-liner summary and optional elaboration
No parameter schema on file.
Create an admin task node for tracking administrative tasks with due dates
No parameter schema on file.
Get all active projects with their next actions, ordered by last modified. Use for daily digest.
No parameter schema on file.
Get all people with pending follow-up items. Use for daily digest.
No parameter schema on file.
Get projects with no activity in X days that might be stuck or forgotten.
No parameter schema on file.
Get inbox entries from the past N days for weekly review.
No parameter schema on file.
Get all data needed for daily digest in a single call. Combines active projects, pending follow-ups, and stale projects.
No parameter schema on file.
Log text to inbox section of daily note. Auto-creates person nodes for any [[Name]] links found.
No parameter schema on file.
Find unchecked items with [[Name]] links where the person node doesn
No parameter schema on file.
Get metadata for a note without full content.
No parameter schema on file.
Delete or archive a note.
No parameter schema on file.
Rename a note.
No parameter schema on file.
Add or remove filetags from a note.
No parameter schema on file.
Create an org-roam link from one note to another.
No parameter schema on file.
Change the TODO state of a task in an org-roam project file. Triggers journal logging hooks for state change tracking.
No parameter schema on file.
Update content in a note by appending, prepending, or replacing. Can target specific sections.
No parameter schema on file.
List org-roam notes with optional filters by type and status. Use when you need to discover notes without a search query.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Org Roam or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.1.15.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Org Roam can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.