Triagic + Neo4j knowledge graph memory: ticket investigations over your knowledge graph, read-only

• Search Neo4j knowledge graph memory for what we already know about this customer's setup
• What does Neo4j knowledge graph memory record as the root cause of the last export incident?
• In Neo4j knowledge graph memory, which systems is the import worker connected to?
• Recall from Neo4j knowledge graph memory every note tagged with this account id
• What did we decide about the legacy export API, according to Neo4j knowledge graph memory?

These are the 3 tools Triagic exposes from the Neo4j knowledge graph memory MCP server. Anything else the server lists is dropped at connect time.

• read_graph
• search_memories
• find_memories_by_name

1. 1

   Mint a read-only credential in Neo4j knowledge graph memory

   Create a dedicated user or token that can only read. An allowlist of read_graph, search_memories and find_memories_by_name; the memory write tools are dropped.

2. 2

   Add it in the Triagic portal

   Integrations, then Add shared data source, then Neo4j knowledge graph memory.

   • Connection URI: The same database the memory server writes to. Aura: Instance details → Connection URI. Self-hosted: bolt:// or neo4j://.
   • Username
   • Password: Prefer a user with only the `reader` role. This server has no read-only switch of its own; Triagic hides its write tools, and a read-only grant makes that hold at the database.
3. 3

   Let a desktop pick it up

   Saving validates the shape of what you typed. The first desktop app to sync starts Neo4j knowledge graph memory locally and reports running or degraded with the error text.

Field-by-field setup, TLS options and the error table: Neo4j knowledge graph memory in the docs.

An allowlist of read_graph, search_memories and find_memories_by_name; the memory write tools are dropped.

Can Triagic change anything in Neo4j knowledge graph memory?

No. An allowlist of read_graph, search_memories and find_memories_by_name; the memory write tools are dropped. Give it a read-only credential as well, so the guarantee does not rest on one layer.

What do I need to connect Neo4j knowledge graph memory?

Connection URI, Username, Password. The desktop app on a member's machine starts the connection; the portal never holds a live process.

Does Neo4j knowledge graph memory cost extra?

No. Every connector is included in the seat price. Start a 14-day trial without a card.

• Neo4jRun read-only Cypher against a Neo4j database and inspect its schema. The server is started with NEO4J_READ_ONLY=true, so the write tool is never registered.
• MemgraphRun read-only Cypher against a Memgraph instance and inspect its node, relationship and enum schema. The server is started with MCP_READ_ONLY=true, which refuses CREATE, MERGE, SET, DELETE, REMOVE and DROP.
• GraphitiSearch a Graphiti temporal knowledge graph (Zep's open-source memory engine) for entities, facts and episodes. Connects to your own Graphiti MCP server over HTTP; the add, delete and clear tools are never exposed.
• Mem0Search and read the memories a Mem0 workspace holds for its users, agents and apps. Connects to Mem0's hosted MCP server with an API key; the add, update and delete tools are never exposed.