Skip to directory

Obsidian Local REST API MCP

Community-maintained plugin by coddingtonbear (not an official Obsidian server)

Streamable HTTP20 documented tools0

About Obsidian Local REST API MCP

The Local REST API Obsidian community plugin now includes its own authenticated MCP server for vault file CRUD, section edits, search, tags, commands, active file and event subscriptions.

What you can use it for

  • Search and read notes in a running local vault
  • Inspect tags, open notes, and invoke available Obsidian commands
  • Create, update, or delete vault content through exposed operations
Connection and setup
Hosting
local Obsidian desktop plugin
Transport
Streamable HTTP
Endpoint
https://127.0.0.1:27124/mcp/
Authentication
Local API key in Authorization: Bearer header; trust the plugin-generated local CA or enable optional HTTP endpoint.

Requirements

  • Obsidian desktop application with the community Local REST API plugin installed and enabled
  • MCP client supporting Streamable HTTP and request headers
  • Plugin API key; trust the generated CA for HTTPS or explicitly enable local HTTP

Setup steps

  1. Install and enable the community Local REST API plugin in Obsidian.
  2. Open Settings → Local REST API with MCP and copy the generated API key into the MCP client’s protected local header configuration as Authorization: Bearer <OBSIDIAN_API_KEY>.
  3. Connect to https://127.0.0.1:27124/mcp/. If the client cannot trust the plugin-generated CA, trust its certificate locally or enable HTTP in plugin settings and use http://127.0.0.1:27123/mcp/.
  4. Reload the client and inspect available tools. Start with a read-only search on a non-sensitive note; do not enable broad vault writes without reviewing the tool descriptions.
Tools 20

All 20 tools in the current plugin documentation Available tools table are recorded. Other installed plugins may register additional tools.

  • vault_list

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    01
  • vault_read

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    02
  • vault_read_binary

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    03
  • vault_get_download_url

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    04
  • vault_get_upload_url

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    05
  • events_get_listener_url

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    06
  • vault_write

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    07
  • vault_append

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    08
  • vault_patch

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    09
  • vault_delete

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    10
  • vault_move

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    11
  • vault_copy

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    12
  • vault_get_document_map

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    13
  • active_file_get_path

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    14
  • search_query

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    15
  • search_simple

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    16
  • tag_list

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    17
  • command_list

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    18
  • command_execute

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    19
  • open_file

    Local REST API with MCP plugin operation; requires a running Obsidian vault and API-key permission.

    20
Limitations and notes
  • Community plugin and not developed or supported by Obsidian.
  • Local endpoint grants potentially broad vault access, including write/delete operations; protect the API key and use loopback only.
  • HTTPS requires trusting the plugin-generated, name-constrained CA; do not disable TLS checks globally.
  • The plugin avoids the Obsidian configuration directory by default, but explicit settings can change that behavior.
Original sources
  • maintainer repository setup

    README documents MCP endpoint, Bearer key, HTTPS/HTTP options, plugin settings, supported operations, and access limitations.

  • maintainer clarification

    Maintainer confirms MCP is served at /mcp/ and uses the same API key as REST.

  • official product brand assets

    Obsidian brand page identifies the product and provides official logo assets; used as product logo while publisher remains community plugin maintainer.

  • official documentation

    Current official publisher/maintainer documentation checked 2026-10-28T19:00:00.000Z.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.

Similar tools