Ovellum MCP server

Read from the package source without running it. The installed server may list more.

• ovellum_buildwrite action

  Run an Ovellum build (parse + generate + merge, or site build). Returns the build summary.

• ovellum_check

  Validate the project without writing: broken internal links, unsafe URL schemes, and stale translations (and, with strict, id-less protected zones, stale anchors, and title-less pages). Returns counts and a per-issue list.

• ovellum_diff

  Compare the current source against the last build IR snapshot. Returns added / removed / changed / renamed symbols and which docs would change. Read-only.

• ovellum_get_page

  Read a built page's Markdown from the output directory (the AI-friendly .md mirror). Path is relative to the output dir; must stay inside it.

• ovellum_list_orphans

  List quarantined manual blocks under protect.orphanDir, with age, last-seen, and (vs the IR snapshot) whether each anchor is back in source. Optional stale filter.

• ovellum_query_symbol

  Look up a documented symbol in the persisted IR snapshot by exact anchor id or by name. Returns kind, signature, source location, description, params, and returns.

• ovellum_reattach

  Rescue an orphaned manual block: splice its prose back into a @manual zone under a target anchor (defaulting to the suggested present-again / renamed anchor) and remove the archive, or delete the orphan. The non-interactive counterpart of `ovellum orphans --reattach`.

• ovellum_search_docs

  Full-text search over the built docs. Returns ranked pages with a path, title, score, and snippet. Run a build first so the output exists.

• ovellum_write_zonewrite action

  Write Markdown prose into a protected @manual zone under an anchor id, so it survives the next hybrid regeneration. Inserts a new block or replaces an existing one with the same blockId. Use dryRun to preview without writing. Survival requires hybrid mode.

• review-doc-drift

  Review what a rebuild would change and surface orphaned prose to reattach.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 57 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

89/100

higher than 80% of 1,299 Productivity servers

Tools

10

the typical Productivity server has 7

Tools that change things

20%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 50% of 854 Productivity servers

Downloads a week

206

more than 72% of 427 Productivity servers with a package

Ovellum: common questions

Is Ovellum MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the Ovellum safety report

How do I install Ovellum?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Ovellum need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Ovellum maintained?

The last commit was 96 days ago (2026-07-31). The latest release is v0.24.0.

What can I use instead of Ovellum?

Servers from other publishers that do the same job: loci MCP server, Open & Async MCP server and Context7 MCP server.

How does Ovellum compare with other Productivity MCP servers?

safety score 89/100 (higher than 80% of 1,299 Productivity servers); tools 10 (the typical Productivity server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.