Graphiti Mcp Pro

Created By
itcook10 months ago
Base on Graphiti, Enhanced Core Capabilities, Broader AI Model Compatibility, and Comprehensive Management UI.
Overview

What is Graphiti MCP Pro?

Graphiti MCP Pro is an enhanced memory repository and management platform based on the Graphiti framework, designed for building and querying temporally-aware knowledge graphs tailored for AI agents in dynamic environments.

How to use Graphiti MCP Pro?

To use Graphiti MCP Pro, clone the project from GitHub, configure the environment variables, and run the service using Docker Compose or manually. Access the management interface via the default address: http://localhost:6062.

Key features of Graphiti MCP Pro?

  • Asynchronous parallel processing for adding memory tasks.
  • Task management tools for monitoring and controlling memory tasks.
  • Unified configuration management for consistent settings.
  • Broader AI model compatibility with support for various models.
  • Comprehensive management platform with a user-friendly UI for service control and monitoring.

Use cases of Graphiti MCP Pro?

  1. Managing AI model interactions in real-time.
  2. Building context-aware applications that require dynamic data updates.
  3. Facilitating efficient memory management for AI agents.

FAQ from Graphiti MCP Pro?

  • Is Graphiti MCP Pro suitable for production use?

It is recommended for personal use only due to known limitations and lack of thorough testing.

  • What are the prerequisites for running Graphiti MCP Pro?

You need Python 3.10+, Node.js 20+, and an accessible Neo4j database service.

  • Can I expose the management backend on public servers?

No, it is advised not to expose the service on public servers due to security concerns.

Server Config

{
  "mcpServers": {
    "graphiti_pro": {
      "transport": "http",
      "url": "http://localhost:8082/mcp"
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
itcook
Star
-
Language
-
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)

20 hours ago
Gpt Scrambler

2 days ago