Second Brain MCP
Related Servers
Alternatives to Second Brain MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching imported AI conversations locally across different providers from an MCP client, with read-only access to the archive.36 PyPI1Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables local full-text and semantic search over saved content, providing search and retrieval capabilities via MCP for AI assistants.-
- FlicenseNot gradedqualityAmaintenanceEnables AI hosts and agents to query a local hybrid index of scattered notes and documents, retrieve section-level citations, and access resources and prompts through MCP.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to search and ask questions across a local hybrid-retrieval index of scattered notes, documents, PDFs, and chat logs, returning section-level citations and agent-usable tools, resources, and prompts.-
- AlicenseNot gradedqualityBmaintenanceEnables searching and retrieving ChatGPT and Claude conversation exports locally, allowing assistants to fetch handoff context and continue conversations through read-only MCP tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query your complete local conversation history and knowledge graph over MCP, including full-fidelity transcripts, search, and typed, dated entity relationships.AGPL 3.0
TDQS
Scored across 7 tools
The set forms a readable retrieval pipeline: search_memory finds snippets, get_record fetches a record by search ID, get_evidence_bundle returns exact quotes with citation IDs, and get_facts/get_fact_history/get_context_brief cover derived views. The closest overlap is search_memory vs get_evidence_bundle, which both rank BM25/embedding results with similar filters and differ mainly in output shape (scores vs exact quotes). Descriptions do disambiguate, so an attentive agent can pick correctly, but the boundary takes reading.
All names are snake_case verb_noun pairs: six get_* accessors plus search_memory. The single search_ verb is a meaningful, not arbitrary, deviation since that tool ranks rather than fetches by identity.
Seven tools is well within the sweet spot and each has a distinct role in the read path (search, record, evidence, facts, history, brief, status). Nothing appears redundant or padding.
The read surface is thorough: discovery, ID-based fetch, evidence with citations, current facts, revision history, briefings, and sync health are all covered. The obvious gap is the write side — no tool creates or updates memories — though the descriptions frame this as deliberate (imports and paid inference happen outside MCP), and there is no browse/list-by-project tool for exploration.