Vault MCP Tools MCP Server

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 vault-mcp-tools -- npx -y vault-mcp-tools

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

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

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

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

This one needs environment variables set before it will start: OBSIDIAN_VAULT_PATH (Absolute path to the Obsidian vault root directory), OBSIDIAN_REST_TOKEN (Bearer token for the Obsidian REST API (enables 3 bonus tools: execute_command, list_commands, open_in_obsidian)), OBSIDIAN_REST_PORT (REST API port (default: 27124)), OBSIDIAN_TRANSPORT (Transport mode: stdio (default) or http), OBSIDIAN_HTTP_PORT (HTTP transport port (default: 3000)), OBSIDIAN_HTTP_AUTH_TOKEN (Bearer token for HTTP transport authentication). The author declared them in the registry entry; get the values from the project itself.