Triagic + Cognee: ticket investigations over your knowledge graph, read-only
Recall 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. Triagic connects to Cognee from the desktop app on each member's machine, with a credential you configure, and shows every call it makes while it investigates a ticket. Nothing is copied out of Cognee.
What you can ask
- Search Cognee for what we already know about this customer's setup
- What does Cognee record as the root cause of the last export incident?
- In Cognee, which systems is the import worker connected to?
- Recall from Cognee every note tagged with this account id
- What did we decide about the legacy export API, according to Cognee?
What the agent can do
These are the 4 tools Triagic exposes from the Cognee MCP server. Anything else the server lists is dropped at connect time.
- recall
- list_datasets_json
- list_dataset_data_json
- get_client_info_json
Connect in three steps
- 1
Mint a read-only credential in Cognee
Create a dedicated user or token that can only read. A self-hosted endpoint; an allowlist of recall and the list and info tools, and cognify and prune are dropped.
- 2
Add it in the Triagic portal
Integrations, then Add shared data source, then Cognee.
- Server URL: A cognee-mcp started with --transport http (or the Docker image with TRANSPORT_MODE=http). That process holds the Cognee API or Cloud credentials; nothing runs on members' machines.
- 3
Let a desktop pick it up
Saving validates the shape of what you typed. The first desktop app to sync starts Cognee locally and reports running or degraded with the error text.
Field-by-field setup, TLS options and the error table: Cognee in the docs.
Read-only, by construction
A self-hosted endpoint; an allowlist of recall and the list and info tools, and cognify and prune are dropped.
FAQ
- Can Triagic change anything in Cognee?
- No. A self-hosted endpoint; an allowlist of recall and the list and info tools, and cognify and prune 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 Cognee?
- Server URL. The desktop app on a member's machine starts the connection; the portal never holds a live process.
- Does Cognee cost extra?
- No. Every connector is included in the seat price. Start a 14-day trial without a card.
Related integrations
- 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.
- 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.
- 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.
Try it on your own Cognee
No card. Install the desktop app, connect Cognee read-only, and triage a real ticket this afternoon.