kObsidian MCP Server

What the code does

We read the source, 1 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const absolutePath = path.join(vaultRoot, args.path);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add kobsidian-mcp -- npx -y kobsidian-mcp

{
  "mcpServers": {
    "kobsidian-mcp": {
      "args": [
        "-y",
        "kobsidian-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.kobsidian-mcp]
command = "npx"
args = ["-y", "kobsidian-mcp"]

{
  "mcpServers": {
    "kobsidian-mcp": {
      "args": [
        "-y",
        "kobsidian-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "kobsidian-mcp": {
      "args": [
        "-y",
        "kobsidian-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: OBSIDIAN_VAULT_PATH (Absolute path to the Obsidian vault this server should operate on.), OBSIDIAN_API_URL (Base URL of the Obsidian Local REST API plugin. Only required for workspace.* / commands.* / live dataview.query* tools.), OBSIDIAN_API_VERIFY_TLS (Set to 'true' if you've trusted the Local REST API's self-signed certificate.), OBSIDIAN_REST_API_KEY (Bearer key for the Obsidian Local REST API plugin (only needed for REST-bridged tools).). The author declared them in the registry entry; get the values from the project itself.