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

> Neo4j knowledge graph memory in Triagic: Read an agent memory graph stored in Neo4j by the mcp-neo4j-memory server: search entities, look them up by...

Source: https://triagic.com/integrations/neo4j-memory

## What you can ask

- 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?

## What the agent can do

- `read_graph`
- `search_memories`
- `find_memories_by_name`

## Connect in three steps

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. **Add it in the Triagic portal.** Integrations, then Add shared data source, then Neo4j knowledge graph memory. Fill in: Connection URI (required): The same database the memory server writes to. Aura: Instance details → Connection URI. Self-hosted: bolt:// or neo4j://.; Username (required); Password (required): 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. **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.

Setup reference: https://triagic.com/docs/integrations/knowledge#neo4j-knowledge-graph-memory

## Read-only, by construction

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

## FAQ

**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.

## Related integrations

- [Neo4j](https://triagic.com/integrations/neo4j)
- [Memgraph](https://triagic.com/integrations/memgraph)
- [Graphiti](https://triagic.com/integrations/graphiti)
- [Mem0](https://triagic.com/integrations/mem0)