AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
MCP verified MIT Self-run

Obsidian Rest Mcp

mcp-alexw00-obsidian-rest-mcp · by AlexW00

Obsidian MCP server wrapping the Obsidian Local REST API

↗ Repository
— No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add mcp-alexw00-obsidian-rest-mcp

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Obsidian Rest Mcp? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Obsidian REST MCP

An MCP (Model Context Protocol) server that wraps the Obsidian Local REST API plugin, enabling AI assistants to interact with your Obsidian vault.

Built with FastMCP - automatically generates tools from the OpenAPI specification.

Why this server

Most MCP wrappers for REST APIs are maintained by manually re-implementing each endpoint as a bespoke tool. That approach tends to drift over time: when the underlying REST API adds/renames/changes endpoints, the MCP server needs a code update (and a new release) to catch up.

This server is different: it dynamically generates tools directly from the Obsidian Local REST API OpenAPI spec.

  • Stays in sync with the REST API: when the plugin’s OpenAPI spec changes, this server’s tool surface updates automatically (no hand-updating dozens of wrappers).
  • Less breakage / less maintenance: fewer places for the MCP implementation to get out of date compared to the plugin.
  • Full coverage: you get the complete set of documented endpoints exposed as tools.

Prerequisites

  1. Obsidian with the Local REST API plugin installed and enabled
  2. Docker

Configuration

Get your API key from Obsidian Settings → Local REST API.

Environment Variables

| Variable | Description | Default | | ----------------------- | ------------------------------------------- | ------------------------- | | OBSIDIAN_API_KEY | API key from Obsidian Local REST API plugin | (required) | | OBSIDIAN_REST_URL | Base URL of the REST API | https://127.0.0.1:27124 | | OBSIDIAN_OPENAPI_PATH | Path to OpenAPI spec | /openapi.yaml |

Usage

VS Code (MCP)

See the checked-in VS Code MCP configuration at .vscode/mcp.json.

> Note: On macOS/Windows, containers can usually reach services on your machine via https://host.docker.internal:27124. > On Linux, you may need --network=host (or an equivalent host gateway setup) for the container to reach the Obsidian REST API.

Available Tools

This server exposes all endpoints from the Obsidian Local REST API.

Documentation (Swagger): https://coddingtonbear.github.io/obsidian-local-rest-api/

License

MIT

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Productivity