What systems does MCP Server integrate with?
SharePoint (Documents library) for metadata and Neo4j for knowledge graph entities. It also requires an embedding model API endpoint and key for semantic search.
@JanithSilva
基本情報
MCP server that provides tools for metadata retrieval from SharePoint and entity retrieval from a Neo4j knowledge graph using semantic similarity search.
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"mcp-server-janithsilva": {
"command": "python",
"args": [
"-m",
"venv",
"venv"
]
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
A Python-based server that provides tools for retrieving metadata from SharePoint's 'Documents' library and querying a Neo4j knowledge graph using semantic similarity search. Built on the FastMCP framework, it is intended for applications needing structured document metadata and entity-relationship information.
Clone the repository, create a Python virtual environment, install dependencies from requirements.txt, and configure environment variables in a .env file (including SharePoint credentials, Neo4j URI, and embedding model settings). Start the server with python mcp_server.py, then invoke the metadata_retrieve or entity_retrieve tools.
SharePoint (Documents library) for metadata and Neo4j for knowledge graph entities. It also requires an embedding model API endpoint and key for semantic search.
Python 3.x, a running Neo4j database, access credentials for SharePoint, and an embedding model API (e
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.

AI agents start every session with amnesia — you re-explain the project, repeat your preferences, and correct the same mistakes over and over. PLUR gives them a memory that persists. Your agent's corrections, preference
Project context your AI can query through MCP — with source evidence.

The official Semantic-UI-React integration

Model Context Protocol Servers
コメント