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

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

These are the 6 tools Triagic exposes from the Memgraph MCP server. Anything else the server lists is dropped at connect time.

• run_cypher_query
• search_schema
• get_node_schema
• get_relationship_schema
• get_enum_schema
• list_databases

1. 1

   Mint a read-only credential in Memgraph

   Create a dedicated user or token that can only read. Started with MCP_READ_ONLY=true, under which the server refuses CREATE, MERGE, SET, DELETE and the other write clauses.

2. 2

   Add it in the Triagic portal

   Integrations, then Add shared data source, then Memgraph.

   • Bolt URL: bolt:// for plain, bolt+s:// for TLS. Memgraph Cloud shows this on the instance page.
3. 3

   Let a desktop pick it up

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

Field-by-field setup, TLS options and the error table: Memgraph in the docs.

Started with MCP_READ_ONLY=true, under which the server refuses CREATE, MERGE, SET, DELETE and the other write clauses.

Can Triagic change anything in Memgraph?

No. Started with MCP_READ_ONLY=true, under which the server refuses CREATE, MERGE, SET, DELETE and the other write clauses. Give it a read-only credential as well, so the guarantee does not rest on one layer.

What do I need to connect Memgraph?

Bolt URL. The desktop app on a member's machine starts the connection; the portal never holds a live process.

Does Memgraph 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.
• 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.
• 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.