Knowledge Graph MCP Server
Enables searching DBLP publication titles by topic and returning citation-count results.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Knowledge Graph MCP Serversearch DBLP for graph neural network papers and show citation counts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Knowledge Graph MCP Server
An MCP server that exposes SPARQL-backed knowledge graph tools for DBpedia and DBLP. It uses the MCP Python SDK and serves Streamable HTTP.
Tools
query_dbpedia(query): Sends the supplied SPARQL query to DBpedia as a URL-encoded HTTP GET and returns SPARQL Results JSON.query_dblp_topic(topic): Searches DBLP publication titles for the supplied topic and returns up to 10 results with citation counts.query_arxiv(topic): Searches arXiv for papers matching the topic that were submitted during the current UTC calendar week, returning Atom XML.
DBpedia and DBLP use public SPARQL endpoints configured in settings.py. The arXiv tool uses the public arXiv API.
Related MCP server: mcp-sparql
Run Locally
Requires Python 3.11 or later.
python -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt
python server.pyThe MCP Streamable HTTP endpoint is http://localhost:8080/mcp. The server uses the PORT environment variable when set, and defaults to port 8080.
Build and Run with Docker
docker build -t knowledge-graph-mcp .
docker run --rm -p 8080:8080 -e PORT=8080 knowledge-graph-mcpConnect an MCP client to http://localhost:8080/mcp using Streamable HTTP.
Deploy to Cloud Run
The compile_and_test_gcp.yaml GitHub Actions workflow builds and pushes the image to Artifact Registry. It deploys when a push commit message contains [deploy] or when a pull request is merged. Configure the workflow's docker-env environment with the GCP_SA_KEY and GCP_PROJECT secrets.
The workflow configures the service to listen on port 8080 and disables unauthenticated access. Callers therefore need Cloud Run invoker permission and a valid Google identity token. The MCP endpoint is https://<cloud-run-service-url>/mcp.
This server cannot be deployed
Maintenance
Related MCP Connectors
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceFederates 13 gene-related MCP backends (gnomAD, GTEx, etc.) behind a single Streamable HTTP endpoint with collision-free namespacing and search-based tool discovery.6MIT
- AlicenseAqualityCmaintenanceMCP server exposing SPARQL query functionalities for LLMs, enabling query execution, validation, and graph exploration across SPARQL endpoints.7MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving academic papers, authors, citations, and references from Semantic Scholar via an HTTP MCP server with caching and rate limiting.308 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with wiki content over Streamable HTTP, with spec-correct tool calls, error handling, and CORS preflight support.507 npmMIT