[Discovery] zepai/knowledge-graph-mcp - Graphiti Knowledge Graph

Open

#4 opened on Dec 3, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Documentation
Clarity: Needs clarification
Activity status: Stale
Tech stack: docker, ollama, python, redis
Domain: databases, devops, documentation

Research direction

Start with the linked Graphiti project and its graphiti.yaml configuration, then review the zepai/knowledge-graph-mcp:standalone image and its FalkorDB and Ollama requirements. Done means documenting the available tools and configuration options, and recording whether a lighter alternative is practical for simpler use cases.

Written by the indexing model from the issue text.

Description

category/db phase/discovery transport/http-streamed type/research

Project Association

This issue tracks the graphiti MCP server in the core profile.

Server Details

Name: graphiti (memory)
Source: https://github.com/getzep/graphiti
Docker Hub: zepai/knowledge-graph-mcp:standalone
Category: db/knowledge
Language: Python

Transport Status

Current: Native HTTP support
Implementation: Built-in HTTP transport
Docker Image: zepai/knowledge-graph-mcp:standalone

Dependencies

FalkorDB (Redis-compatible graph database)
Ollama (for embeddings)

Tools Provided

Knowledge graph operations (to be documented)

Docker Status

Official image: zepai/knowledge-graph-mcp:standalone
Requires FalkorDB and Ollama services
Complex multi-service setup

Notes

Requires significant resources (1 CPU, 1GB RAM)
Depends on external services (FalkorDB, Ollama)
Uses graphiti.yaml config file

Tracking

Document all tools comprehensively
Document configuration options
Consider lighter alternative for simpler use cases

Dominant language: Just
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: session_search misses a short non-Latin query typed in the other case Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

use-agent-os/agent-os#3312 · Opened Sep 22, 2026
Document that a SQLite trail allows only one writer Open

documentation help wanted

Difficulty 2/5 1-3 hours Newbie friendliness 90/100

rajfirke/provena#202 · Opened Sep 22, 2026
Cache revalidation responds before commit: undocumented read-after-write window Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

HarperFast/documentation#677 · Opened Sep 22, 2026
/trades holds two read-pool connections per request with no parallelism benefit Open

bug team:backend track:services-maintenance

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

cowprotocol/services#4950 · Opened Sep 21, 2026
Batched `completeJobs`/`failJobs` are never retried: the retry loop in `batch()` exits after the first failure Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

graphile/worker#636 · Opened Sep 21, 2026

More Databases issues