cog-brain
OfficialRelated Servers
Alternatives to cog-brain
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents and developers to inspect Obsidian vault knowledge graphs, navigate backlinks, detect broken wikilinks, lint note compliance, search indexed notes, and scaffold standards-compliant Markdown notes via MCP.6MIT
- AlicenseNot gradedqualityBmaintenanceGives any MCP-capable AI agent long-term memory from a self-hosted Obsidian vault, exposing tools to read, search, list and write markdown notes over MCP or a REST API with keyword plus semantic search. Agent writes are confined to a drafts inbox so they never overwrite your own notes.1 npmMIT
- AlicenseAqualityBmaintenanceExposes a typed, provenance-aware knowledge graph over an Obsidian vault to coding agents over MCP, so they can trace what grounds a claim, compute which other notes a change makes wrong, surface contradictions and admitted gaps, and assemble a task-specific token-budgeted subset of the vault. Indexing, retrieval, and impact analysis run with zero third-party runtime dependencies beyond the Python standard library.10MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first knowledge backend for AI agents that connects MCP hosts to an Obsidian-compatible vault with indexed retrieval, token-budgeted memory recall, and secure ingestion.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes an Obsidian-style markdown vault as agent-readable memory. It provides tools for search, read, graph, and guarded capture without using embeddings.1MIT
- AlicenseNot gradedqualityAmaintenanceTurns your Obsidian vault into an MCP-enabled workspace with tools for reading/writing notes, managing folders, running semantic searches, and maintaining long-term memory—all while keeping data local to your vault.309,216 npm158MIT
TDQS
Scored across 12 tools
Each tool targets a distinct action or resource: status, inventory, outline, full read, search, related notes, backlinks, broken links, graph overview, create, update, and index. Overlaps are minimal and descriptions clearly differentiate.
Some tools use verb_noun (list_notes, read_note, write_note, update_note, find_related), while others are noun phrases (vault_status, semantic_search, backlinks, broken_links, graph_overview). The mix is readable but not a consistent pattern.
12 tools is well within the typical 3-15 range and each tool has a clear, non-redundant purpose for managing an Obsidian vault.
The surface covers create, read, update, search, linking, and indexing, but lacks a delete_note operation and any move/rename capability. These are notable gaps for full vault lifecycle management.