1. Home
  2. MCP Server for Obsidian
  3. MCP Server for Obsidian for Cursor: Setup & Config

Data as of

MCP Server for Obsidian for Cursor: Setup & Config

MCP Server for Obsidian connects Cursor to an Obsidian vault through the Local REST API plugin.

MCP Server for Obsidian Cursor configuration

  1. Choose Cursor configuration scope

    For MCP Server for Obsidian, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add MCP Server for Obsidian to Cursor

    Use the mcp-obsidian entry below in mcpServers. Keep MCP Server for Obsidian's documented stdio connection fields and your other Cursor entries.

  3. Check MCP Server for Obsidian in Cursor

    MCP Server for Obsidian: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "mcp-obsidian": {
      "command": "uvx",
      "args": [
        "mcp-obsidian"
      ],
      "env": {
        "OBSIDIAN_API_KEY": "<API key from your Obsidian Local REST API plugin>",
        "OBSIDIAN_HOST": "<Obsidian API host; defaults to 127.0.0.1>",
        "OBSIDIAN_PORT": "<Obsidian API port; defaults to 27124>"
      }
    }
  }
}

MCP Server for Obsidian in Cursor: stdio checks

  • Cursor must find uvx mcp-obsidian (from uv, for Python tools) for MCP Server for Obsidian. Enable the project/user entry in MCP settings and inspect its tools.
  • Review OBSIDIAN_API_KEY, OBSIDIAN_HOST, OBSIDIAN_PORT for MCP Server for Obsidian before sharing project .cursor/mcp.json; project scope travels with the repository.
  • MCP Server for Obsidian uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
list_files_in_vault, list_files_in_dir, get_file_contents

MCP Server for Obsidian — details. Cursor guide

Frequently asked questions

Cursor's MCP Server for Obsidian entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's mcp-obsidian example uses stdio.

MCP Server for Obsidian's Cursor configuration invokes uvx mcp-obsidian (from uv, for Python tools).

Cursor's MCP Server for Obsidian example references OBSIDIAN_API_KEY, OBSIDIAN_HOST, OBSIDIAN_PORT. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

MCP Server for Obsidian's stored list contains 7 tools, including list_files_in_vault, list_files_in_dir, get_file_contents. Compare those names with Cursor's connected tool list; the stored list is not a live check.