RDF Explorer

Created By
Emeka Azuka Okoyea year ago
A Model Context Protocol (MCP) server that provides the conversational interface for the exploration and analysis of RDF Turtle based Knowledge Graph in either Local File mode or SPARQL Endpoint mode.
Overview

What is RDF Explorer?

RDF Explorer is a Model Context Protocol (MCP) server that provides a conversational interface for exploring and analyzing RDF Turtle-based Knowledge Graphs in both Local File mode and SPARQL Endpoint mode.

How to use RDF Explorer?

To use RDF Explorer, set it up on Claude Desktop by configuring it to either a local RDF Turtle file or a SPARQL endpoint. You can then interact with the server using natural language queries to explore graph data.

Key features of RDF Explorer?

  • Execute SPARQL queries on local files or external endpoints.
  • Perform full-text searches on the graph.
  • Generate statistics and reports about the graph.
  • Analyze graph structure and find relationships.

Use cases of RDF Explorer?

  1. Exploring employee data in a corporate knowledge graph.
  2. Analyzing customer purchase patterns in a retail dataset.
  3. Generating reports on relationships within a semantic web dataset.

FAQ from RDF Explorer?

  • Can RDF Explorer handle large datasets?

Yes, RDF Explorer is designed to work with large RDF datasets efficiently.

  • Is RDF Explorer free to use?

Yes, RDF Explorer is open-source and free to use under the MIT License.

  • What types of queries can I run?

You can run SPARQL queries, full-text searches, and natural language queries to explore your data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Emeka Azuka Okoye
Star
-
Language
-
License
-
Category

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