A
licenseNot graded
qualityB
maintenanceEnables MCP clients to query a local drill-down work map and knowledge graph, supporting work map, project context, related projects, reuse finding, search, and graph statistics, all read-only.
Apache 2.0
Ravenroot Second Brain MCP
Officialby ravenroot-ai
Related Servers
Alternatives to Ravenroot Second Brain MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceLocal-first MCP graph intelligence server providing RRF hybrid search, multi-hop traversal, source snippets, and rationale nodes for AI agents, without Docker or web UI.5-
- AlicenseAqualityBmaintenancePersistent knowledge graph MCP server with SQLite backend. Enables graph traversal, fuzzy search, temporal queries, and timestamps for entity management.12MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA Knowledge Graph MCP server optimized for LLM context efficiency through compact JSON and SQLite persistence. It enables full graph management including node/edge CRUD operations, full-text search, and subgraph traversal.-
- AlicenseNot gradedqualityCmaintenanceExposes the local GraphRAG knowledge base over MCP, letting clients such as Claude Desktop query the markdown vault with cited answers and check graph or ingestion status.MIT
- FlicenseNot gradedqualityBmaintenanceEnables local, deterministic semantic operations on OWL/RDF ontologies, including Description Logic reasoning, SPARQL querying, TBox/ABox mutation, and interactive graph visualization via an MCP interface.1-
TDQS
A3.5/5.0
Scored across 10 tools
Disambiguation4/5
The graph tools (query_graph, get_node, get_neighbors, get_community, god_nodes, graph_stats, shortest_path) each target a clearly distinct operation. The PR tools are mostly distinct, though list_prs and triage_prs overlap heavily—both return open PRs with graph-impact data—and only the descriptions' filtering nuance (actionable/correct base/not stale) separates them.
Naming Consistency4/5
All names use consistent snake_case, which is predictable and readable. However, the verb pattern is not strictly uniform: several are noun phrases (god_nodes, graph_stats, shortest_path) while others are verb_noun (get_node, list_prs), a minor deviation.
Tool Count5/5
Ten tools is well-scoped for a knowledge-graph query plus PR-triage server, with each tool earning its place. No redundancy that would push it toward bloat.
Completeness4/5
Read-side graph coverage is solid (search, fetch, neighbors, community, hubs, stats, pathfinding) and the PR workflow is covered from listing to impact to triage. The only gap is the absence of any mutation tools (add/update/delete node or edge), which an agent might expect for a 'second brain'.
Maintenance
ActivityMaintained
ResponsivenessNo issues