KnowledgeGraph MCP Server

Created By
n-r-wa year ago
MCP server for enabling persistent knowledge storage for Claude through a knowledge graph with multiple storage backends and fuzzy search
Overview

What is KnowledgeGraph MCP Server?

KnowledgeGraph MCP Server is a tool designed to provide persistent memory for large language models (LLMs) like Claude, enabling them to remember information about users, projects, and preferences through a structured knowledge graph.

How to use KnowledgeGraph MCP Server?

To use the KnowledgeGraph MCP Server, you can install it via NPX or Docker, choose your preferred database (SQLite for simplicity or PostgreSQL for advanced use), and configure it to work with Claude or VS Code by editing the respective configuration files.

Key features of KnowledgeGraph MCP Server?

  • Multiple Storage Backends: Supports both PostgreSQL and SQLite.
  • Project Separation: Automatically isolates different projects based on prompts.
  • Enhanced Search: Utilizes fuzzy search and pagination for better information retrieval.

Use cases of KnowledgeGraph MCP Server?

  1. Managing project-related information and preferences for team members.
  2. Storing and retrieving complex relationships between entities in project management.
  3. Enhancing LLM capabilities by providing contextual memory across conversations.

FAQ from KnowledgeGraph MCP Server?

  • Can I use both SQLite and PostgreSQL?

Yes, you can choose either SQLite for local use or PostgreSQL for production environments.

  • Is there a guide for setting it up?

Yes, a complete setup guide is provided in the documentation.

  • How does the fuzzy search work?

Fuzzy search allows for finding similar or misspelled terms, enhancing the search experience.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
n-r-w
Star
4
Language
TypeScript
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