Knowledge & memory: 6 read-only integrations
Each page lists the exact tools Triagic exposes and the mechanism that keeps them read-only. Setup steps for every one live on the knowledge and memory docs page. 14-day trial, no 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.2 tools
- Neo4j knowledge graph memoryRead an agent memory graph stored in Neo4j by the mcp-neo4j-memory server: search entities, look them up by name, or read the whole graph. Create, add and delete tools are never exposed.3 tools
- 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.6 tools
- 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.6 tools
- 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.6 tools
- CogneeRecall from a Cognee memory (its graph and vector layers) and list its datasets. Connects over HTTP to a cognee-mcp server you run in http mode; remember, forget and cognify are never exposed.4 tools
Connect one and ask it something
Install the desktop app, add a read-only credential for one system, and run a real investigation against it.