Kg

By default, graphs are stored in~/.kg/graphsas.kgfiles.

You are connected to kg-mcp. Project graph name: payments Build or extend this graph from the project documentation I provide. Use payments as the graph name for all graph operations. Only add facts grounded in source material. If an important fact is missing and can be inferred safely from the provided docs, update the graph. If something is ambiguous, ask or record it as a note instead of inventing facts.

Use kg-mcp to build or extend the payments graph from these documents: - docs/payments/overview.md - docs/payments/retries.md - docs/payments/providers.md Only add facts grounded in the documents. If something is ambiguous, keep it out of the graph or record it as a note. When you finish, summarize what was added, what remains unclear, and what document should be ingested next.

For a ready-made repository example, runcargo run --bin repo-exampleto generaterepo-example.kgfrom this repo.

kgcan turn an existing folder into a graph automatically. It scans the directory tree, recognizes many common file types, extracts symbols for Rust, Java, JavaScript/TypeScript, Python, and C/C++, and keeps the generated structure separate from the manual graph.

For markdown-like documents, it also creates document (GDOC) and chapter (GSEC) nodes with section content.

It is a fast way to get a useful map of a codebase or workspace without modeling everything by hand. The generated index is local, refreshable, and safe to ignore in git.

This generatesrepo-example.kgfrom this repository as a local demo.

Ask the Assistant About Facts in the Graph

Once the graph exists, the normal workflow is to ask the assistant to inspect it and answer questions from it.

Use kg-mcp to inspect my existing payments graph. I want to understand: - how payment authorization works, - what triggers retries, - which external providers are involved, - which datastore reads and writes are part of the flow. If the graph is missing critical information, say exactly what is missing.

- "What rules control retries in thepaymentsgraph?"
- "Which systems write to the orders datastore?"
- "What is missing or weak in this graph?"
- "Which nodes and edges explain the authorization flow?"

Add or Update Facts Through the Assistant

You can also ask the assistant to improve the graph while you work.

Use kg-mcp to review my existing payments graph. Find: - missing important nodes, - weak descriptions, - missing facts, - suspicious or low-value edges. Apply safe improvements where possible. Only add facts grounded in the graph, the provided docs, or the current discussion. If something is ambiguous, leave it out or add a note. When you finish, summarize: - what was wrong, - what you changed, - what still needs manual review.

This works best when your main system prompt or project prompt already tells the assistant which graph belongs to the project.

You are connected to kg-mcp. Project graph name: payments. Use this graph for relevant reads and updates in this project. If you notice important missing information that is grounded in the available docs or conversation context, update the graph as part of your work. If uncertain, ask or add a note instead of inventing facts.

kglooks for.kg.tomlin the current directory and its parent directories.

For questions or feedback:nnar10@proton.me

Neo4j graph database server (schema + read/write-cypher) and separate graph database backed memory

Query a hybrid graph (Neo4j) and vector (Qdrant) database for powerful semantic and graph-based document retrieval.

Connects to Neo4j graph databases with ability to use GDS functions ( when available), a read only mode , and set the sample size for schema detection

Integrate the Neo4j graph database with clients through natural language interactions.

MCP server for Neo4j — run Cypher queries, explore schema, and inspect database info over stdio

Interact with and explore graph data in a Neo4j database.

Cognitive memory for AI agents - persistent semantic memory with knowledge graph and adaptive recall

A server for interacting with ArangoDB, a native multi-model database system.

Manage graph-based data models, schemas, and ontologies with CoreModels. 16 MCP tools for visual data modeling with full JSON Schema support.