GraphDB MCP Server

Created By
ianormya year ago
MCP server tools for GraphDB
Overview

what is GraphDB MCP Server?

GraphDB MCP Server is a Model Context Protocol (MCP) server implementation that facilitates database interaction and graph exploration capabilities through GraphDB, enabling users to run SPARQL graph queries.

how to use GraphDB MCP Server?

To use the GraphDB MCP Server, set up the server with the required configurations in your claude_desktop_config.json file, specifying the database URL and schema file, and execute SPARQL queries using the provided tools.

key features of GraphDB MCP Server?

  • Execute SPARQL read queries to retrieve data from a repository.
  • Retrieve the RDF triples that define the ontology for the GraphDB database.
  • Supports integration with Claude Desktop for enhanced functionality.

use cases of GraphDB MCP Server?

  1. Querying and retrieving data from a GraphDB repository.
  2. Exploring and understanding the structure of RDF data through ontology retrieval.
  3. Integrating with applications that require graph database capabilities.

FAQ from GraphDB MCP Server?

  • What is SPARQL?

SPARQL is a query language and protocol used to query RDF data.

  • Is the GraphDB MCP Server free to use?

Yes, the server is open-source and licensed under the MIT License, allowing free use and modification.

  • What are the prerequisites for using the server?

You need to install uv (Universal Virtualenv) and set up a development environment as specified in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ianormy
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago