ExpertPack MCP

io.github.brianhearn由 GitHub 账号 brianhearn 发布v0.7.0更新于 Oct 25, 2026

通过 MCP 提供 ExpertPack 知识包,支持混合搜索、图遍历和来源追溯。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

Serve ExpertPack knowledge packs over MCP with hybrid search, graph traversal and provenance.

已验证STDIO仅桌面

概览

ExpertPack 的本地 MCP 服务;无需登录;STDIO。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

  1. 打开 控制台中的 ExpertPack MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

ep-mcp

Expertise-as-a-Service over the Model Context Protocol.

An MCP server that turns any ExpertPack into a live, queryable knowledge service. Any MCP-compatible agent (Claude Desktop, Cursor, Windsurf, Claude.ai, custom hosts) can connect and retrieve high-quality, provenance-rich domain expertise via standardized tools.

🌐 expertpack.ai · 📦 ExpertPack Framework · 📖 Architecture

97.6% retrieval hit rate / 0 full misses on a 22-question benchmark against a production v4.1 atomic-conceptual pack (658 chunks). Prior v4.0 baseline on the same pack and eval set: 65.1%.

Features

  • Schema-aware hybrid retrieval: BM25 + vector search (sqlite-vec), metadata boosting, MMR re-ranking, adaptive threshold filtering, length penalty
  • requires: expansion (schema v4.1 atomic-conceptual): When a top-K atom's frontmatter declares requires: [B, C], the referenced atoms are auto-appended to results as additional SearchResults flagged requires_expanded=True. Directional (A→B does not imply B→A), transitive up to 2 hops, capped at 3 atoms and 3,500 cumulative tokens, appended after the max_results slice so it never displaces top-K.
  • Intent-aware routing: Automatic query classification (ENTITY/HOW/WHY/WHEN/GENERAL) adjusts vector/BM25 fusion weights per query — no LLM required
  • Query embedding cache: SQLite-backed cache keyed by (model, dimension, sha256(query)) — warm query latency drops from ~4s (live Gemini API) to ~1ms
  • Deep graph traversal: Optional multi-hop BFS expansion over knowledge graph edges with per-hop score decay and drift prevention
  • Reserved-slot graph merge: Configurable protected slots in the final top-K reserved for graph-expanded neighbors so related files surface even against dominant core results
  • BM25 fallback mode: Embedding provider outage degrades gracefully to lexical-only search (coverage + density + path + length scoring) instead of a hard error
  • Cross-encoder reranker: Optional second-pass precision reranker (disabled by default, ~70ms warm latency when enabled)
  • Provenance-first: Every result includes id, content_hash, verified_at, source_file
  • Reconstruct mode (RFC-003): Opt-in reconstruct=true / reconstruct: true enriches results with fragment_id, line_range, original_markdown, span-level content_hash, excerpt, stale, and byte offsets so agents can prove exactly what source text grounded an answer
  • EP-native chunking: Files are treated as atomic retrieval units (split at ##/### only for oversized content). Split chunks keep the original span as content/span_hash, carry a computed line_range, and record a heading_path (0.7.0+)
  • Heading paths (0.7.0+): every hit carries heading_path (e.g. ["Routing", "Setup", "Ports"]) so an H3 hit keeps its H2 parent; ep_read(path, section=..., neighbors=true) reads just that section plus its previous/next siblings
  • Freshness (0.7.0+, ExpertPack Core 4.2): hits and ep_read carry verified_age_days, age_stale (verified_at older than the file's refresh or the manifest freshness.refresh_cycle), expired and expires_at (volatile TTL). stale keeps its old meaning — index drift (file changed since indexing, reconstruct mode only). Optional down-rank via retrieval.freshness_penalty (default 0.0 = off)
  • Skills over MCP (0.7.0+, opt-in): set mcp.skills.enabled: true in a pack's manifest.yaml to declare the io.modelcontextprotocol/skills extension (SEP-2640). Each pack becomes one skill at skill://{slug}/SKILL.md (generated) with every non-on_demand file served verbatim at skill://{slug}/{path}; skills/list / skills/get publish the manifest with SHA-256 digests, sizes, ttlMs and cacheScope. Host support is still thin, so the ep_* tools remain the primary path
  • Frontmatter aware: Strips metadata for embedding, extracts type, tags, requires, etc. for boosting/expansion/filtering
  • Incremental indexing: Content-hash based staleness detection — only re-embeds changed files
  • Multi-pack support: Path-based routing at /packs/{slug}/mcp
  • Graph-aware retrieval: optional post-retrieval expansion via _graph.yaml adjacency, including accepted ontology/entity nodes when graph export provides them
  • context_prefix (RFC-004): sidecar situating strings are prepended at index time for embed + BM25 only; returned/reconstruct text stays the original atom body
  • Tier / navigation filter: retrieval_strategy: navigation, _index.md, source-coverage.md, and context.on_demand files are excluded from the RAG pool (still readable via ep_read / resources)
  • Tools:
    • ep_search — primary hybrid retrieval tool
    • ep_read — load a whole atom by path or provenance id (consume-loop step 2)
    • ep_list_topics — browse pack structure and available content types
    • ep_graph_traverse
    • Multi-pack stdio support: All tools accept a pack parameter for routing when multiple packs are configured. Single-pack configs make pack optional (defaults to the only configured pack).
  • Resources:
    • ep://{slug}/manifest
    • ep://{slug}/authority
    • ep://{slug}/files
    • ep://{slug}/file/{+path} (raw content with frontmatter)
    • skill://{slug}/SKILL.md, skill://{slug}/{+path} (only when mcp.skills.enabled: true)
  • Transports: Streamable HTTP (primary, cloud-ready), stdio (local dev)
    • stdio multi-pack support (0.6.0+): When using --transport stdio with multiple packs configured, all tools accept an optional pack parameter (slug string) to specify which pack to query. For single-pack configurations, the pack parameter is optional and defaults to the only configured pack. This allows MCP hosts (Cursor, Claude Desktop) to use a single stdio process for multiple packs instead of requiring one process per pack.
  • HTTP endpoint: GET /search (for non-MCP HTTP clients)
  • Golden retrieval eval (0.7.0+): tests/eval/ — YAML query sets (expected best-first, must_not, category) scored as recall@1/3/5, MRR and must_not violations per pack and category. Skipped in the default run; pytest tests/eval -m golden --golden <dir> --packs-root <dir> with EP_EVAL_TODAY=2026-10-20 and optional EP_EVAL_MIN="recall@5=0.9,mrr=0.7", or python tests/eval/golden_eval.py --golden <dir> --today 2026-10-20
  • Auth: API key (Phase 1), designed for OAuth 2.1 (Phase 2)

Quick Start

Installation

bash
git clone https://github.com/brianhearn/ep-mcp.gitcd ep-mcppip install -e .[dev]

Configuration

Create config.yaml with at minimum:

yaml
server:  host: "127.0.0.1"  port: 8000  log_level: "info"  # Required for public Host headers (SDK v2 DNS-rebinding protection).  # See DEPLOYMENT.md — omit and Streamable HTTP returns 421.  mcp_allowed_hosts:    - "localhost"    - "localhost:*"    - "127.0.0.1"    - "127.0.0.1:*"
packs:  - slug: "my-pack"    path: "/path/to/your/expertpack"    api_keys:      - "your-secret-key-here"
embedding:  provider: "gemini"           # "gemini" (default) or "azure-openai"  model: "gemini-embedding-001"

For the full configuration reference — embedding providers, retrieval tuning (mmr_lambda, min_score, default_max_results, graph expansion, reranker, requires: expansion, etc.), production systemd setup, and deployment gotchas — see DEPLOYMENT.md.

Running

bash
ep-mcp serve --config config.yaml

The server builds/updates the SQLite index (FTS5 + sqlite-vec) on startup. 0.5.0 requires a rebuild of existing indexes (index_features=context_prefix_v1+nav_filter_v1); startup does this automatically, or delete <pack>/.ep-mcp/ first.

The GET /search HTTP endpoint is available at:

GET /search?q=<query>&pack=<slug>&n=10

Add &reconstruct=true to include original markdown spans and provenance blocks for verification.

with header Authorization: Bearer <key>.

Environment Variables

Only the key for your configured embedding provider is required.

VariableRequiredDescription
GEMINI_API_KEYIf embedding.provider: geminiGemini embedding API key
AZURE_OPENAI_ENDPOINTIf embedding.provider: azure-openaiAzure OpenAI resource endpoint
AZURE_OPENAI_API_KEYIf embedding.provider: azure-openaiAzure OpenAI API key
EP_MCP_KEY_{SLUG}OptionalPer-pack API key override (uppercase slug, hyphens→underscores)
EP_MCP_REMOTE_HOSTOptionalDeploy target for scripts/deploy.sh
EP_MCP_REMOTE_SRCOptionalRemote source path for deploy.sh
EP_MCP_REMOTE_SITE_PKGOptionalRemote site-packages path for deploy.sh

Tech Stack

  • Language: Python 3.12+
  • MCP Framework: official mcp SDK v2 (MCPServer, spec 2026-07-28, dual-era with 2025 clients)
  • Storage: SQLite with FTS5 + sqlite-vec
  • Embeddings: Gemini (default), configurable Azure OpenAI / OpenAI providers
  • Web: Starlette + Uvicorn (for Streamable HTTP)
  • CLI: Click

See pyproject.toml for exact dependencies.

Project Structure

See ARCHITECTURE.md for detailed module breakdown, retrieval pipeline, indexing strategy, and design decisions.

Related

  • expertpack.ai — Framework website, community packs, and documentation
  • ExpertPack — Schema framework, validation tools, Obsidian compatibility, community packs
  • ExpertPacks — Published knowledge packs (private)
  • EasyTerritory MCP (future) — Domain-specific layer built on top of this repo + ezt-designer pack

License

Apache 2.0 © 2026 Brian Hearn

Author

Brian Hearn — Built in 3 days (April 10–11, 2026).

来源:README.md,提交 dcda343

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.7.0最新Oct 20, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。