Enterprise Knowledge MCP Server

Enterprise Knowledge MCP Server

Provides read-only, citation-backed semantic search and retrieval-augmented generation over enterprise documents via standardized MCP tools, with local embeddings for privacy.

Category
访问服务器

README

Enterprise Knowledge MCP Server

MCP server that exposes semantic search + RAG over enterprise documents as standardized tools, so any MCP client (Claude Desktop, etc.) gets read-only, citation-backed access without touching source systems directly.

Connector #1 (local PDF/DOCX/XLSX) is implemented. Embeddings run locally via sentence-transformers — no document text leaves the machine.

Architecture

connector.list_documents()          # SourceDocument objects
        v
ingestion/extractor.py              # per-mime text extraction -> ExtractedSection
        v
ingestion/chunker.py                # sentence-packed chunks w/ overlap -> Chunk
        v
ingestion/embedder.py               # sentence-transformers -> vectors
        v
storage/vector_store.py             # Chroma upsert/query (metadata filtering)
        v
rag/retriever.py (KnowledgeService)  # orchestrates the above; search() + build_rag_context()
        v
server.py                            # FastMCP tools wrapping KnowledgeService

Adding a new source (SharePoint, Confluence, Notion, Google Drive, Slack) means writing one class implementing connectors/base.py::BaseConnector (list_documents, get_document). Nothing downstream changes.

Setup

pip install -r requirements.txt

Drop files into data/raw/ (or point at another directory), then from src/:

from connectors.local_files import LocalFileConnector
from rag.retriever import KnowledgeService

svc = KnowledgeService()
svc.ingest_connector(LocalFileConnector(root_dir="../data/raw"))

Or just run the ingest tool through the MCP server itself once connected.

Running the server

python src/server.py

Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "enterprise-knowledge": {
      "command": "python",
      "args": ["/absolute/path/to/enterprise-knowledge-mcp/src/server.py"]
    }
  }
}

Tools exposed

Tool Purpose
ingest_local_directory(directory?) Scan + index PDF/DOCX/XLSX from a directory
search_knowledge(query, top_k?, source_type?, department?, author?) Semantic search with metadata filters
get_rag_context(query, top_k?, source_type?, department?) Retrieved chunks + citation markers, ready for an LLM prompt
list_indexed_documents() All indexed docs + chunk counts
index_stats() Total indexed chunk count

Metadata schema (per chunk)

doc_id, title, source_type, path_or_uri, section_label, author, department, tags, modified_at, ingested_at — section_label is page number (PDF), heading/table (DOCX), or sheet name (XLSX), so citations point to a specific location, not just a document title.

Config

Environment variables (see src/config.py): EKM_RAW_DIR, EKM_CHROMA_DIR, EKM_COLLECTION, EKM_CHUNK_SIZE, EKM_CHUNK_OVERLAP, EKM_EMBEDDING_MODEL, EKM_TOP_K.

Roadmap (modular connectors, in priority order)

  1. Local files — done.
  2. SharePoint — Microsoft Graph API (/sites/{id}/drive/items), delta queries for incremental sync, app-only auth via client credentials.
  3. Confluence — REST API v2 (/wiki/api/v2/pages), CQL search for incremental sync, API token auth.
  4. Notion — Notion API (/v1/search, block children pagination), integration token auth.
  5. Google Drive — Drive API v3, service account or OAuth, export Google Docs/Sheets as text/csv before extraction.
  6. Slack — conversations.history + file downloads, bot token auth, respect channel membership for access control.

Security notes for production

  • Never embed credentials in connector code — use env vars / a secrets manager per connector.
  • Enforce source-level ACLs at query time (filter where clauses by the requesting user's permitted departments/channels), not just at ingest time.
  • Log every search_knowledge / get_rag_context call (query + returned doc_ids) for audit trails.
  • Rate-limit and sandbox connector network calls; SharePoint/Confluence/ Notion/Drive/Slack connectors will need outbound HTTPS to their respective APIs only.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选