[Trend Scout] pvliesdonk/markdown-vault-mcp

[github-actions]

🔭 Trend Scout: pvliesdonk/markdown-vault-mcp

Auto-generated by trend-scout.py — review and edit as needed.

📌 What problem it solves

Generic markdown collection MCP server with FTS5 + semantic search, frontmatter-aware indexing, and incremental reindexing

📅 Timeline

Field	Value
Created	2026-03-07
Last pushed	2026-04-26
Stars	5
Forks	3
Open issues	23
License	MIT
Language	Python
Topics	claude, embeddings, fastmcp, fts5, knowledge-base, markdown, mcp, mcp-server, model-context-protocol, obsidian, python, search, semantic-search, sqlite, vault

✅ Strengths

• Well-tagged: claude, embeddings, fastmcp, fts5, knowledge-base, markdown
• Primary language: Python
• Actively maintained (pushed within 30 days)

⚠️ Weaknesses / Risks

• Low star count (5) — limited community validation

💡 What this repo can learn

• Hybrid FTS+semantic retrieval: combining keyword and embedding-based search could improve recall in query-session.py / briefing.py — e.g., a query for 'docker networking' would also surface entries tagged 'container' or 'network_mode' even without exact term overlap
• MCP tool-server surface: the MCP server interface here could expose query-session.py and briefing.py as directly callable MCP tools — e.g., a Copilot agent could invoke the briefing lookup in-process rather than shelling out to a subprocess, reducing latency in hook-driven workflows
• Frontmatter-aware indexing: parsing YAML frontmatter in session markdown files could extend build-session-index.py and extract-knowledge.py to use structured metadata (category, tags, date) as indexed fields — e.g., frontmatter category: mistake could pre-populate the knowledge type without relying on regex heuristics
• Incremental reindex / changed-file tracking: the change-detection approach here could improve watch-sessions.py's polling loop — e.g., storing per-file content hashes so only modified or new session files trigger re-extraction, reducing redundant extract-knowledge.py passes on large session directories
• Document conversion pipeline: the file/attachment ingestion approach here could extend build-session-index.py to normalise non-markdown sources — e.g., a pre-processing stage that converts attachments or exported documents to plain text before the FTS5 insert path

README excerpt

<!-- mcp-name: io.github.pvliesdonk/markdown-vault-mcp -->
# markdown-vault-mcp

[![CI](https://github.com/pvliesdonk/markdown-vault-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/pvliesdonk/markdown-vault-mcp/actions/workflows/ci.yml) [![codecov](https://codecov.io/gh/pvliesdonk/markdown-vault-mcp/graph/badge.svg)](https://codecov.io/gh/pvliesdonk/markdown-vault-mcp) [![PyPI](https://img.shields.io/pypi/v/markdown-vault-mcp)](https://pypi.org/project/markdown-vault-mcp/) [![Python](https://img.shields.io/pypi/pyversions/markdown-vault-mcp)](https://pypi.org/project/markdown-vault-mcp/) [![License](https://img.shields.io/github/license/pvliesdonk/markdown-vault-mcp)](LICENSE) [![Docker](https://img.shields.io/github/v/release/pvliesdonk/markdown-vault-mcp?label=ghcr.io&logo=docker)](https://github.com/pvliesdonk/markdown-vault-mcp/pkgs/container/markdown-vault-mcp) [![Docs](https://img.shields.io/badge/docs-GitHub%20Pages-blue)](https://pvliesdonk.github.io/markdown-vault-mcp/) [![llms.txt](https://img.shields.io/badge/llms.txt-available-brightgreen)](https://pvliesdonk.github.io/markdown-vault-mcp/llms.txt) [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/pvliesdonk/markdown-vault-mcp)

<!-- DOMAIN-START -->
A generic markdown collection [MCP](https://modelcontextprotocol.io/) server with FTS5 full-text search, semantic vector search, frontmatter-aware indexing, incremental reindexing, and non-markdown attachment support.

**[Documentation]

*(truncated)*

---

Scouted on 2026-04-27 · View on GitHub

[magicpro97]

Closing this old Trend Scout report because it was generated by the previous heuristic-only pipeline and is too repetitive / low-signal to be actionable.

This repo now has the improved Trend Scout flow with GitHub Models-backed analysis. If this target repo is still worth evaluating, we should re-scout it with the new pipeline instead of keeping the old report open.