Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow Obsidian version and vault-operation changes as the plugin evolves
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Legacy Obsidian semantic-search and prompt integration
What we know
Archived Obsidian MCP integration that added semantic search and custom prompt workflows for MCP clients.
Maintenance / activity evidence
- Observed (UTC)0.2.33
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Access follows configured Obsidian/plugin scope. Writes: Depends on configured tools.
- Authentication not yet verified.
- Sensitive access: Obsidian vault content
- The archive/maintenance status is the primary operational caveat; note content may be sensitive.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
832 repository stars
Stars observed Sep 25, 2026.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
All limitations / Review context
Which note, tag, and vault operations are currently exposed?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- The archive/maintenance status is the primary operational caveat; note content may be sensitive.
- Access follows configured Obsidian/plugin scope.
- Vault note content is exposed to the local integration.
- Reviewed write actions: Depends on configured tools
- Sensitive access: Obsidian vault content
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- No independent runtime, installation, or comprehensive security audit was performed.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- Current install path after archive
- Detailed authentication model
- Repository was archived by the owner on May 13, 2026 and is now read-only.
- Use actively maintained alternatives for new deployments.
Original activity observations
- 2026-05-13T16:13:22Z: 0.2.33
Technical identity
github.com/jacksteamdev/obsidian-mcp-tools- Exact implementation source
- https://github.com/jacksteamdev/obsidian-mcp-tools ↗
- Reviewed resource type
- MCP Server
- Repository identity
- jacksteamdev/obsidian-mcp-tools
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
jacksteamdev/obsidian-mcp-tools
Recorded repository material and project history.
Setup · Watchlist
Install & Agents
obsidian-app
Publisher instructions with a documented client setup path.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsObsidian → Community Plugins: install MCP Tools for Obsidian and Local REST API, configure REST API key, then in MCP Tools settings click **Install Server** and approve the Claude Desktop integration. No npm package install is required.
Obsidian → Settings → Community plugins → install `MCP Tools for Obsidian` and `Local REST API` → enter REST API key → MCP Tools settings → Install Server → approve Claude Desktop configuration.
Configure / authenticate
Publisher instructionsInstall Obsidian Community Plugin and Local REST API plugin; use the plugin Install Server button to configure Claude Desktop with explicit permission. Do not replace this GUI setup with an invented global npm command.
Check connection
Suggested checkCheck that Local REST API is enabled, server installed and Claude Desktop has the entry.
Remove / uninstall / revoke
Suggested checkObsidian Settings → Community plugins → MCP Tools for Obsidian → Disable (or Uninstall); in Claude Desktop MCP settings remove its auto-added server. Keep Local REST API only if used elsewhere.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
What it does
Archived Obsidian MCP integration that added semantic search and custom prompt workflows for MCP clients.
- Capability
- Files & Knowledge
- Resource type
- MCP Server
- Best fit
- Legacy Obsidian semantic-search and prompt integration
Representative uses
- Search Obsidian notes
- Expose custom prompt workflows
- Connect Obsidian content to MCP clients
Limitations
- Repository was archived by the owner on May 13, 2026 and is now read-only.
- Use actively maintained alternatives for new deployments.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Not documented in the reviewed sources
- Permissions
- Access follows configured Obsidian/plugin scope.
- Data handling
- Vault note content is exposed to the local integration.
- Cost
- free
- Risk and cautions
- The archive/maintenance status is the primary operational caveat; note content may be sensitive.
Access scope and cautions
- Write actions
- Depends on configured tools
- Sensitive access
- Obsidian vault content
- Risk level
- moderate
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which implementation does this page cover?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
jacksteamdev is listed as Community implementation in MCP100’s current evidence.