MCP Server

Created By
JanithSilvaa year ago
MCP server that provides tools for metadata retrieval from SharePoint and entity retrieval from a Neo4j knowledge graph using semantic similarity search.
Overview

what is MCP Server?

MCP Server is a Python-based application designed to facilitate metadata retrieval from SharePoint and entity retrieval from a Neo4j knowledge graph using semantic similarity search.

how to use MCP Server?

To use MCP Server, clone the repository, set up a virtual environment, install the required dependencies, configure the necessary environment variables, and start the server to access its tools.

key features of MCP Server?

  • Metadata Retrieval: Fetches structured metadata from SharePoint's 'Documents' library.
  • Entity Retrieval: Queries a Neo4j knowledge graph using semantic similarity to find relevant entities and their relationships.
  • FastMCP Integration: Built on the FastMCP framework for efficient tool management and execution.

use cases of MCP Server?

  1. Retrieving and managing metadata from SharePoint for data analysis.
  2. Exploring relationships and entities within a Neo4j knowledge graph for research purposes.
  3. Integrating semantic search capabilities into applications that require knowledge graph interactions.

FAQ from MCP Server?

  • What are the prerequisites for using MCP Server?

You need Python 3.x, access to a Neo4j database, SharePoint credentials, and an OpenAI API key for semantic search.

  • Is MCP Server free to use?

Yes! MCP Server is open-source and free to use.

  • How can I contribute to MCP Server?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JanithSilva
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago