The Model Context Protocol (MCP) lets AI assistants connect directly to your knowledge graph.
Search, explore relationships, and write insights back - all through natural conversation.
What is MCP?
MCP is an open standard that lets AI assistants connect to external data sources and tools.
Graphory provides an MCP server that gives your AI read and write access to your knowledge graph.
Instead of copy-pasting data into chat, your AI can directly search your graph, look up specific items,
explore connections, and save findings back for future reference.
Setup
See the Getting Started guide for platform-specific
configuration instructions covering Claude Desktop, Claude Code, ChatGPT, Gemini CLI, Cursor,
Windsurf, VS Code, Codex CLI, and direct API access.
Available Tools
Once connected, your AI has access to these tools:
search_graph
Search your knowledge graph for items matching a query. Supports filtering by type and business entity.
Parameter
Description
query
Search terms
node_type
Optional type filter (e.g. "person", "company", "email")
entity
Optional business entity filter
limit
Max results (default: 20)
get_entity
Get full details for a specific item including all its properties and direct relationships.
Parameter
Description
node_id
The item's unique identifier
traverse
Explore the relationship network starting from a specific item. Reveals connections up to N hops away.
Parameter
Description
start_id
Item ID to start from
depth
Hops to traverse (default: 2, max: 5)
edge_types
Optional relationship type filter
timeline
Get a chronological feed of recent activity across your data sources.
Parameter
Description
entity
Optional business entity filter
days
Lookback window (default: 30)
limit
Max items (default: 50)
graph_stats
Get a summary overview of your graph - total counts, breakdowns by type and source.
No parameters required.
write_to_graph
Save findings or new information back to the graph. Confidence gating applies (auto-merge at 0.9+, review queue at 0.7-0.89, rejected below 0.7).
Parameter
Description
action
add, connect, or correct
confidence
Confidence score (0 to 1)
data
JSON payload for the write operation
ingest
Push raw data into your graph from within a conversation. Useful for capturing insights on the fly.
Parameter
Description
payload
JSON string with entity, source, title, and body fields
Example Conversations
Searching your graph
You
Who are the key contacts at Acme Corp?
Your AI will use search_graph to find Acme Corp, then traverse to discover connected people. It combines results from emails, calendar events, and other sources into a unified answer.
Exploring recent activity
You
What happened in the last week across all my business entities?
Your AI calls timeline with a 7-day window and summarizes activity across all connected data sources.
Writing back insights
You
Based on those emails, it looks like Jane Smith just moved from Acme to Beta Inc. Update the graph.
Your AI uses write_to_graph to update Jane's company association with high confidence, since you confirmed the change.
Getting oriented
You
What does my graph look like? Give me the overview.
Your AI calls graph_stats to get total node/edge counts and breakdowns by type and source, then presents a summary.
Tips for Best Results
Be specific about what you want. "Find all emails from Jane in March" works better than "Tell me about Jane."
Name the business entity when your org has multiple. "What's happening at Acme Corp?" scopes the search.
Ask your AI to explore. "Who else is connected to this deal?" triggers traversals that reveal hidden relationships.
Let it write back. When you discover something new in conversation, ask to save it to the graph for next time.
Start with stats. Ask "What does my graph look like?" to get oriented before diving into specific queries.
Chain operations. "Find Jane, then show me everyone she's connected to, then check her recent activity" works as one request.
Troubleshooting
Tools not appearing
Make sure you fully restarted your AI client (not just closed the window)
Check that the config JSON is valid - a missing comma or bracket will break it
Verify your API key is correct and has not been revoked
Authentication errors
Confirm the key starts with gs_ak_
Make sure there are no extra spaces in the Authorization header value
Try generating a new key from the Settings page
Slow responses
Large graphs (100K+ nodes) may take a few seconds for complex traversals
Use filters (node_type, entity) to narrow search scope
Reduce depth on traverse operations if results are too broad