cognee-mcp-server

Created By
topoteretesa year ago
Overview

what is cognee-mcp-server?

The cognee-mcp-server is a server designed for 'cognee', an AI memory engine that builds a knowledge graph from user-input text and facilitates searching within it.

how to use cognee-mcp-server?

To use the cognee-mcp-server, configure it according to your environment, including setting up necessary parameters in the claude_desktop_config.json, and run it with the specified commands related to your installation path.

key features of cognee-mcp-server?

  • Constructs knowledge graphs based on textual input.
  • Allows for searching within the generated knowledge graph.
  • Supports custom graph model implementations through flexible configuration options.

use cases of cognee-mcp-server?

  1. Enhancing AI systems with memory by building contextual knowledge graphs.
  2. Performing efficient searches across complex datasets based on user queries.
  3. Supporting applications needing robust data retrieval and organization capabilities.

FAQ from cognee-mcp-server?

  • What is required to run cognee-mcp-server?

You will need to configure the server with your API key and local paths, and it works with various database providers.

  • Can I use custom models with cognee-mcp-server?

Yes, you can use your own Pydantic graph model implementations by specifying the filenames and class names in the configuration.

  • Is cognee-mcp-server compatible with existing AI frameworks?

Yes, it is designed to integrate smoothly with systems like Claude Desktop and can be adapted for other AI frameworks.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
topoteretes
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)

a day ago