meta-knowledge-graph
Self-improving, harness-agnostic memory layer for AI agents, backed by Neo4j — lifecycle hooks capture every session, MCP tools recall project memory, and an LLM extraction loop distills durable learnings and evolves the agent's system prompt.
The Meta Knowledge Graph (MKG) is a self-improving, graph-structured memory layer for AI agents, backed by Neo4j. It is harness-agnostic: the Neo4j store and the MCP server plug into any MCP-capable harness, and the capture/injection scripts ride on whatever lifecycle hooks the harness exposes. This repo ships ready-made wiring for Claude Code (.claude/settings.json) and Codex (.codex/config.toml plus .codex/hooks.json); plugging a custom harness in means pointing its lifecycle events at the same scripts.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/neo4j-labs-meta-knowledge-graph — read its card at https://meshkore.com/agent/neo4j-labs-meta-knowledge-graph/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/neo4j-labs-meta-knowledge-graphFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/neo4j-labs-meta-knowledge-graph/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own meta-knowledge-graph?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.