MCP Tools DirectoryAbout this integration
Long-term memory for AI agents — your Obsidian vault as searchable persistent memory.
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 3.11.6
- Package
- @oomkapwn/enquire-mcp
- Last compatibility test
- Not independently tested
Connect your agent
@oomkapwn/enquire-mcpPublisher README and package manifest reviewed. The directory did not install or execute the package, inspect a vault, validate benchmark claims, or security-audit the implementation. Optional writes, HTTP exposure, model downloads, and client-side cloud processing remain operator-controlled boundaries.
Capabilities: Hybrid search over Markdown and PDF content with source paths and page citations, Structured Canvas, Dataview-style, and Obsidian Bases access, Read-only vault navigation with separately gated write tools
Connected profiles
Additional details
io.github.oomkapwn/enquire-mcp
Source ↗ · Checked 2026-09-173.11.6
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@oomkapwn/enquire-mcp
Source ↗ · Checked 2026-09-194.0.0-rc.7
Source ↗ · Checked 2026-09-19Publisher documents a headless Node.js MCP server launched with a vault path; the reviewed local configuration runs over stdio and is read-only unless write tools are explicitly enabled.
Source ↗ · Checked 2026-09-19The reviewed local stdio configuration supplies only the package command and vault path, with no credential or account setting. Publisher documentation separately requires a bearer token for the optional remote HTTP transport; that transport is outside this stdio listing.
Source ↗ · Checked 2026-09-19Run npx -y @oomkapwn/enquire-mcp serve --vault as the MCP client's local stdio child process.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19