MCP -vault

MCP -vault is a centralized, human-curated database of MCP servers designed to be browsed and searched within Obsidian. It provides a single source of truth for server metadata, tags, and relationships, enabling you to quickly discover servers by category, technology, or purpose. Use the vault to explore existing MCP servers, review their documentation, and understand how different implementations fit into the Model Context Protocol ecosystem. The vault emphasizes rich frontmatter tagging and a consistent structure so AI agents and other tools can effectively filter, query, and extract relevant information about MCP servers.

Within the vault, you can browse the servers/ directory to find individual server notes, apply filters by tags (such as #category/database or #tech/typescript), and perform semantic searches with supported Obsidian plugins. For automation or AI-assisted workflows, you can leverage the Obsidian Local REST API plugin to query metadata, and use the MCP Tools plugin to surface MCP-specific data. The vault also supports template-driven additions, so contributors can add new servers with standardized frontmatter and tagging to keep the database comprehensive and navigable.

Prerequisites:

• Git
• Obsidian (optional but recommended for full experience as described in the vault)
• Basic familiarity with Markdown and frontmatter

Installation steps:

1. Install Obsidian from https://obsidian.md/ (recommended if you want to browse and search the vault with rich UI features).
2. Clone the vault repository: git clone https://github.com/amir-arad/MCP-server-vault.git
3. Open the cloned directory as a vault in Obsidian: In Obsidian, choose: Open folder as vault -> select the MCP-server-vault directory.
4. Install recommended community plugins (optional but recommended):
   • Obsidian Local REST API
   • Obsidian Git
   • Smart Connections
   • Templater
   • MCP Tools
5. Optional: Set up Git-based versioning for the vault by enabling Obsidian Git and configuring a remote repository if you plan to contribute changes via PRs.

If you prefer a non-Obsidian workflow, you can still browse the Markdown notes directly from the repository or render them with any Markdown viewer.

Notes and tips:

• This MCP vault uses a single-note-per-server approach with standardized frontmatter and tagging. When contributing, follow the templates in templates/server.md to ensure consistency.
• Common environment variables and configuration options may appear in individual server notes; refer to the repo's tag conventions (e.g., #source, #tech, #category) to understand metadata at a glance.
• If you encounter issues with search or tagging in Obsidian, ensure your plugins are up to date and that the vault structure mirrors the documented layout (servers/ for notes and templates/ for new note templates).
• For AI-assisted workflows, the Obsidian Local REST API plugin can be used to programmatically query server metadata; ensure the API is enabled and reachable from your Obsidian instance.
• When adding new servers, include canonical repository URLs, owner, and a clear status (active, inactive, deprecated) in the frontmatter to maintain the integrity of the vault’s dataset.