Vault Mcp Tools

io.github.afable702Published by GitHub account afable702v1.0.1Updated Oct 30, 2026

Complete Obsidian vault MCP server. 35 tools: notes, search, graph, tags, canvas.

VerifiedSTDIODesktop onlyFiles & Storage Knowledge & Memory

Server details

Identifier: io.github.afable702/vault-mcp-tools
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account afable702 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.afable702%2Fvault-mcp-tools.svg)](https://sourceweft.com/mcp/io.github.afable702%2Fvault-mcp-tools?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that gives an assistant 35 tools to work with an Obsidian vault: notes, search, graph, tags and canvas.

What you can do: Read and write notes in an Obsidian vault
Search the vault and browse tags
Explore the vault graph and canvas files
Optionally run Obsidian commands and open items in the app when a REST token is supplied
When to use it: Useful when your notes live in an Obsidian vault and you want an assistant to search, summarize, link or edit them from a desktop MCP client.
Requirements: Runs locally over stdio from the npm package vault-mcp-tools. Requires the absolute path to the vault root in OBSIDIAN_VAULT_PATH. Optional settings: OBSIDIAN_TRANSPORT (stdio or http), OBSIDIAN_HTTP_PORT, OBSIDIAN_REST_PORT, and the secret tokens OBSIDIAN_HTTP_AUTH_TOKEN and OBSIDIAN_REST_TOKEN.

Before you install

The server can modify vault content, so changes to notes should be reviewed. It asks for two secret tokens: OBSIDIAN_HTTP_AUTH_TOKEN protects the HTTP transport and OBSIDIAN_REST_TOKEN unlocks command execution and opening items in Obsidian. Keep the vault path scoped to a dedicated vault.

Installation

In SourceWeft

Open Vault Mcp Tools in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.