vault-mcp-tools

Install vault-mcp-tools in your MCP client

vault-mcp-tools is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

1. Locate your client's MCP config file.
   • Cursor: ~/.cursor/mcp.json
   • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
   • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
   • VS Code: Settings → Extensions → MCP
   • Windsurf: Settings → MCP Servers
2. Add vault-mcp-tools to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
3. Restart your client so it picks up the new server.
4. Verify — ask the assistant to list available tools; vault-mcp-tools's tools should appear.

{
  "mcpServers": {
    "vault-mcp-tools": {
      "command": "npx",
      "args": [
        "-y",
        "vault-mcp-tools"
      ],
      "env": {
        "OBSIDIAN_VAULT_PATH": "<your-obsidian-vault-path>",
        "OBSIDIAN_REST_TOKEN": "<your-obsidian-rest-token>",
        "OBSIDIAN_REST_PORT": "<your-obsidian-rest-port>",
        "OBSIDIAN_TRANSPORT": "<your-obsidian-transport>",
        "OBSIDIAN_HTTP_PORT": "<your-obsidian-http-port>",
        "OBSIDIAN_HTTP_AUTH_TOKEN": "<your-obsidian-http-auth-token>"
      }
    }
  }
}

npm package: vault-mcp-tools

Required environment variables

vault-mcp-tools needs the following environment variables set before it can run. Add them to the env block of your mcpServers entry, or export them in your shell before launching the client.

• OBSIDIAN_VAULT_PATH
• OBSIDIAN_REST_TOKEN
• OBSIDIAN_REST_PORT
• OBSIDIAN_TRANSPORT
• OBSIDIAN_HTTP_PORT
• OBSIDIAN_HTTP_AUTH_TOKEN

Transport

vault-mcp-tools supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

More automate.personal.notes MCP servers

Other Model Context Protocol servers in the same space as vault-mcp-tools. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

• vir-cli

  An LLM Wiki for Claude Code, in your Obsidian vault.

• genexus-mcp

  GeneXus 18 MCP server — read, edit, and analyze GeneXus knowledge base objects (transactions, web panels, procedures, SDTs) directly from Claude, Cursor, and other AI agents over the Model Context Protocol.

• enquire-mcp

  The most advanced MCP server for Obsidian vaults. Hybrid retrieval (BM25 + TF-IDF + multilingual ML embeddings, RRF-fused) with BGE cross-encoder reranking, HNSW vector index, int8 quantization, late-chunking, HyDE-augmented retrieval, sub-question decomp

• knowledge-keeper-mcp

  AI Memory & Knowledge Management MCP Server — 32 tools, BM25 R@5=95%, hybrid search (RRF), knowledge graph, analytics, cloud sync, Obsidian compatible. Works with Claude Code, Cursor, Gemini CLI, Windsurf, hermes-agent.

• Nouz

  Semantic knowledge engine for Obsidian with auto-classification and DAG hierarchy

• Sprintra

  The project brain for AI coding agents — memory, decisions, sprints, knowledge base via MCP.

• obsidian-mcp-server

  MCP server for Obsidian vaults — read, write, search, and edit notes via the Local REST API plugin.

• obsidian-mcp-server

  MCP server for Obsidian vaults — read, write, search, and surgically edit notes, tags, and frontmatter via the Local REST API plugin. STDIO or Streamable HTTP.

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.