obsidian-local-rest-api logo

MCP'S

obsidian-local-rest-api

by coddingtonbear

mcplead-sourcegithub-mcp-server-repositoriessource:github.comobsidianobsidian-pluginrest-apilocal-apivaultbearer-token

Overview

A secure REST API and Model Context Protocol server for an Obsidian vault.

Details

Local REST API with MCP is an Obsidian plugin by coddingtonbear. The supplied repository metadata describes it as “A secure REST API and Model Context Protocol (MCP) server for your vault.” The Obsidian plugin directory page documents REST API examples and MCP client setup using the local endpoint https://127.0.0.1:27124/mcp/ with bearer-token authentication. The project also publishes interactive API documentation on GitHub Pages.

When to Use

Expose an Obsidian vault through a local REST API for workflows that need documented API access. Connect an MCP client to an Obsidian vault using the documented local MCP endpoint and bearer-token authentication. Review REST API examples or interactive API documentation before integrating with Obsidian vault data.

Getting Started

  1. Open the official GitHub repository at https://github.com/coddingtonbear/obsidian-local-rest-api for the project source and linked resources.
  2. Review the Obsidian plugin directory page for REST API examples and MCP client setup details.
  3. Use the documented MCP endpoint https://127.0.0.1:27124/mcp/ with bearer-token authentication as described by the Obsidian plugin directory.
  4. Consult the interactive API documentation at https://coddingtonbear.github.io/obsidian-local-rest-api/ for API reference details.

Key Features

  • Secure REST API for an Obsidian vault.
  • Model Context Protocol server support for an Obsidian vault.
  • Documented MCP client setup using a local HTTPS endpoint.
  • Bearer-token authentication documented by the Obsidian plugin directory.
  • Interactive API documentation published by the project.

Capabilities

  • obsidian-vault-rest-api
  • mcp-server
  • local-mcp-endpoint
  • bearer-token-authentication
  • interactive-api-docs

Last updated Jun 4, 2026