obsidian-mcp-macros

Provides MCP functionality for custom local user scripts written in JavaScript, using the Model Context Protocol SDK and related tooling (including a Qdrant REST client and schema validation via zod).

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Automation mcp obsidian typescript local-automation agents tooling qdrant vector-search sdk

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Security details are not provided in the README/manifest beyond dependencies. Since it’s a local MCP server, TLS/auth/rate limiting behavior cannot be confirmed. Presence of zod suggests some input validation might exist, but secret handling and network exposure practices are not documented here.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a local, developer-controlled MCP tool surface to back Obsidian automation/scripts, and you can review/maintain the codebase yourself.

Avoid When

You need a well-documented, externally hosted API with clear auth/rate-limit guarantees and robust operational reliability; the provided materials don’t show those aspects.

Use Cases

• Expose Obsidian-local scripting capabilities to AI agents via an MCP server interface
• Augment personal knowledge-base workflows in Obsidian with tool calls backed by custom JS scripts
• Index or retrieve vector data (via Qdrant) to support retrieval-augmented operations in local workflows

Not For

• Server-side multi-tenant deployments where strong remote auth, rate limits, and operational guarantees are required
• Use cases needing documented stable MCP tool contracts, pagination, and error semantics
• Production environments requiring audited security controls around authentication, secrets, and network exposure (not evidenced in provided materials)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Yes

Webhooks

Authentication

OAuth: No Scopes: No

No authentication mechanism is described in the provided README/manifest. As a local MCP server, it may rely on local network assumptions, but this is not verifiable from the supplied content.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; likely a local/open-source project dependency tree.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ As provided, there is no visible MCP tool list, schemas, or error-code conventions; agents may need to handle failures generically.
⚠ Local tooling may assume access to the user’s Obsidian vault/filesystem and any configured vector DB; agents may fail if environment variables or paths are missing.
⚠ Idempotency and retry semantics are not documented; agents should avoid assuming safe retries for side-effectful operations.

Alternatives

Use an existing, well-maintained MCP server implementation with documented tools (community) Build a small custom REST API (OpenAPI) for tool calls instead of MCP if you need stronger contract documentation Use Obsidian community plugins that already expose well-defined command/tool behaviors without MCP

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for obsidian-mcp-macros.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.