
What you can do once it is connected, each in one short section below, with a link to the full guide: connect, find gaps, reason with a map, keep a memory, and build graphs you reuse everywhere.
1Connect InfraNodus to Your AI
Get your API key from the InfraNodus API panel (needs a free InfraNodus account), then add this address to your AI client. It is the same for every client:
https://mcp.infranodus.comSettings → Connectors → Add custom connector, paste the address, click Connect, and sign in with your API key.
Apps → Advanced settings → Developer mode → Create app, paste the address, leave OAuth empty, connect with your API key.
claude mcp add infranodus -s user --transport http https://mcp.infranodus.com/mcpRun this in your terminal, then /mcp → Authenticate.
Cursor Settings → MCP → New MCP Server, paste the address, then click Login next to the server.
Codex, Claude Desktop config, n8n, and local setup: see the setup page.
Then ask your AI for a graph. This is what a session looks like in Claude Code:
2Find the Gaps from the Chat
A content gap is two topics in your material that should be connected but are not. Ask for them and your AI calls generate_content_gaps: it gets the two clusters that sit far apart and a question that would bridge them. This works on your notes, a document, a codebase, Google results, or a whole conversation.

Do not stop at the first answer. Pick the gap that matters for your work and ask the AI to develop it:
Then open the same graph in the web app to read the statements behind each cluster. That is where the idea gets checked against your actual material.

3Reasoning Maps
An LLM predicts one step at a time and has no structure to check its reasoning against. A reasoning map gives it one: a graph of concepts with typed relations such as [influences] or [constrains], written in plain text with [[wikilinks]]. Your AI retrieves the relations between the concepts it is working with via GraphRAG, instead of the most similar passages.
[[market sentiment]] [influences] [[price volatility]] [constrained by] [[liquidity]]Build it in InfraNodus, check where it is thin or lopsided with the gap analysis from section 2, and connect it to Claude, Cursor, or your agents. Point the model at the graph and it calls retrieve_from_knowledge_base on it:

4Memory Graphs
Claude Code remembers with CLAUDE.md and auto memory: flat files on one machine. A memory graph stores what you and your agents learned as short statements in your InfraNodus account, so Claude Code, Cursor, Claude Desktop, and the web app all read the same memory.
- Insight memory: the AI saves with
memory_add_relations, andmemory_get_relationsbrings it back in the next chat. - Agent learnings: with the Project Learnings skill, your agent reads the
learn-<project>graph when a task starts and proposes new learnings when it ends. Nothing is saved until you approve the batch.
Because the memory is a graph, you can see it. Open it in InfraNodus and the gap between two clusters shows what your agent keeps relearning: it knows the deploy routine and the caching rule, but not that one breaks the other.
Set up Claude Code memory with a knowledge graph →
More on memory: the memory MCP server, the AI memory stack, and agent memory tools compared.
5Create and Analyze Your Graphs
Any data can become a graph: a PDF, a folder of Markdown notes, a web page or a YouTube video, interview transcripts, a column from a CSV, the Google results for a query, or your codebase with the /infranodus skill. Ask your AI to save it under a name and it calls create_knowledge_graph. The graph is stored in your InfraNodus account, not in the chat.
Once it is saved, any session can analyze it by name: the topics and gaps with analyze_existing_graph_by_name, what one graph has that another lacks with difference_between_texts, and the graph you need with list_graphs and search.
The same graph works in every tool you connect. Build it from Claude today, query it from Claude Code in Cursor or ChatGPT next week, open it in the web app or in the Obsidian plugin to read the statements, or let an n8n agent use it as context. Each new session starts from what the graph already holds.
