pulsemcp verified Safe content atomic mcp-remote

Obsidian Advanced

This MCP server provides AI assistants with advanced Obsidian vault management capabilities through the Local REST API plugin, built by Jason Guo using Python with obsidiantools integration for enhanced metadata extraction and NetworkX for graph analysis. The implementation offers 13 specialized tools including simple and complex search with JsonLogic queries, batch file operations with comprehensive metadata, periodic notes management, vault structure analysis with directory trees and connection graphs, active note tracking, recent changes monitoring, and Obsidian command execution. Built with configurable tool selection via environment variables, enhanced API approaches combining REST endpoints with obsidiantools for richer metadata, and robust error handling with fallback mechanisms, it serves knowledge workers needing AI-assisted note management and analysis, researchers requiring automated vault organization and content discovery, and teams wanting to integrate Obsidian workflows with AI assistants for enhanced productivity and knowledge graph exploration.

Cognium trust score

84%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: monitoring
Source: PulseMCP
Repository: github.com/tokidoo/mcp-obsidian-advanced
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Obsidian Advanced from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"