by samyama-ai
Graph-vector database that queried 1 billion edges for $2.50. Rust, OpenCypher, vector search, 14 graph algorithms. 74M nodes / 1B edges on a single machine.
# Add to your Claude Code skills
git clone https://github.com/samyama-ai/samyama-graphGuides for using mcp servers skills like samyama-graph.
Last scanned: 7/27/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-07-27T07:30:42.718Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}samyama-graph is an open-source mcp servers skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by samyama-ai. Graph-vector database that queried 1 billion edges for $2.50. Rust, OpenCypher, vector search, 14 graph algorithms. 74M nodes / 1B edges on a single machine. It has 117 GitHub stars.
Yes. samyama-graph passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/samyama-ai/samyama-graph" and add it to your Claude Code skills directory (see the Installation section above).
samyama-graph is primarily written in Rust. It is open-source under samyama-ai on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other MCP Servers skills you can browse and compare side by side. Open the MCP Servers category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh samyama-graph against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Samyama Graph is a Rust-native graph-vector database that lets developers store, query, search, and analyze connected data in one system.
It brings together graph traversal, OpenCypher-style querying, vector search, graph algorithms, and Redis-compatible access, making it useful for GraphRAG, knowledge graphs, AI agent memory, and large-scale relationship analytics.
Step 1 — Prerequisites
Step 2 — Pull the Docker image
docker pull public.ecr.aws/f9f6l5u4/samyama-graph:1.1.0
Step 3 — Docker Compose setup
Create a clean folder, then create docker-compose.yml inside it.
Linux & Mac:
mkdir -p samyama-graph
cd samyama-graph
touch docker-compose.yml
Windows (PowerShell):
mkdir C:\samyama-graph
cd C:\samyama-graph
notepad docker-compose.yml
ℹ️ Replace
<your-openai-api-key>with your actual key. Generate one at platform.openai.com/api-keys.
version: "3.9"
services:
samyama-graph:
image: public.ecr.aws/f9f6l5u4/samyama-graph:1.1.0
container_name: samyama-graph
restart: unless-stopped
ports:
- "6379:6379"
- "8080:8080"
environment:
EMBED_ENABLED: "true"
EMBED_PROVIDER: openai
EMBED_MODEL: text-embedding-3-small
EMBED_API_KEY: <your-openai-api-key>
EMBED_DIMENSION: 1024
volumes:
- samyama-data:/app/samyama_data
networks:
- samyama-network
networks:
samyama-network:
driver: bridge
volumes:
samyama-data:
Step 4 — Start the server
docker compose up -d
Server will be available at http://localhost:8080
Step 5 — Verify it's running
docker ps
docker logs -f samyama-graph
You should see samyama-graph with status Up.
Step 6 — Samyama Visualizer
Visualize your imported graph data using the Samyama cloud visualizer at https://graph.samyama.cloud/
http://localhost:8080.7a — Download snapshot
| Dataset | Description | File |
|---|---|---|
| DBMS Research | Database management systems research knowledge graph | dbms-research.sgsnap |
Tip: Save the file in the same folder as docker-compose.yml to avoid path errors.
C:\samyama-graph\dbms-research.sgsnap./samyama-graph/dbms-research.sgsnap7b — Create tenant
Linux & Mac:
curl -X POST http://localhost:8080/api/tenants \
-H "Content-Type: application/json" \
-d '{"id": "dbms-research", "name": "dbms-research"}'
Windows (PowerShell):
curl.exe -X POST http://localhost:8080/api/tenants `
-H "Content-Type: application/json" `
-d '{"id": "dbms-research", "name": "dbms-research"}'
7c — Import snapshot
Linux & Mac:
curl -X POST http://localhost:8080/api/snapshot/import \
-F "file=@./samyama-graph/dbms-research.sgsnap" \
-F "tenant_id=dbms-research"
Windows (PowerShell):
curl.exe -X POST http://localhost:8080/api/snapshot/import `
-F "file=@C:\samyama-graph\dbms-research.sgsnap" `
-F "tenant_id=dbms-research"
Note: On Windows always use curl.exe — PowerShell's curl alias does not support -F.
Step 8 — Stop / reset
Stop the server:
docker compose down
Reset all data (⚠️ deletes volume):
docker compose down -v
⚠️ This deletes all graph data stored in the Docker volume.
# Build from source
git clone https://github.com/samyama-ai/samyama-graph && cd samyama-graph
cargo build --release
./target/release/samyama # RESP on :6379, HTTP on :8080
# Connect with any Redis client
redis-cli -p 6379
GRAPH.QUERY mydb "CREATE (a:Person {name: 'Alice'})-[:KNOWS]->(b:Person {name: 'Bob'})"
GRAPH.QUERY mydb "MATCH (a)-[:KNOWS]->(b) RETURN a.name, b.name"
Samyama Graph is useful when your application needs both connected-data reasoning and semantic retrieval.
You can use it to build:
We loaded the entire PubMed corpus — every article published since 1966 — plus ClinicalTrials.gov, Reactome pathways, and DrugBank into one graph. Then we asked:
"What drugs are most tested in cancer clinical trials?"
MATCH (m:MeSHTerm)<-[:ANNOTATED_WITH]-(a:Article)
-[:REFERENCED_IN]->(t:ClinicalTrial)-[:TESTS]->(i:Intervention)
WHERE m.name = 'Neoplasms'
RETURN i.name, count(DISTINCT t) AS trials
ORDER BY trials DESC LIMIT 5
| Drug | Trials |
|---|---|
| Placebo | 521 |
| Pembrolizumab | 137 |
| Carboplatin | 106 |
| Paclitaxel | 106 |
| Cyclophosphamide | 98 |
5.2 seconds. One query. Four databases. 74 million nodes. 1 billion edges. A single machine.
See all 100 benchmark queries →
⭐ Find this useful? A GitHub star helps more developers discover Samyama Graph.
Cricket KG — 36K nodes, 1.4M edges, live graph simulation
Click for full demo (1:56)
One query family — reachability, criticality, N-1 contingency — runs identically across infrastructure domains. Both demos use real CC BY 4.0 data.
Power Grid — IEEE 14-bus system (pglib-opf): degree centrality → connectivity → N-1 line contingency.

Telecom — GÉANT 2012 pan-European backbone (Internet Topology Zoo): 40 PoPs across 37 countries; N-1 link contingency exposes 8 single points of failure.

case_studies/ lets anyone who clones this repo download a real
public knowledge graph, import it, run showcase Cypher (and vector search), and
render the session as a narrated GIF — one command, no database to install.
Every showcase query is gated to return real rows before any GIF is recorded
(see the Definition of Done).
cargo build --release && pip install rich requests
cd case_studies/cricket && ./run.sh # fetch snapshot → import → validate → demo
RECORD=1 ./run.sh # also (re)generate demo.gif
Each snapshot is small enough to run on a laptop; every query returns real rows.
GIFs can't pause in a browser, so each domain also ships its demo.cast — replay
it pausably (space) with asciinema play case_studies/<domain>/demo.cast.
| Domain | Scale | Highlight | Snapshot | Demo |
|---|---|---|---|---|
| cricket | 37K / 1.4M | dismissal-rivalry networks, venues, awards | cricket.sgsnap |
gif |
| drug-interactions | 245K / 388K | polypharmacy shared-target risk, CYP hubs | druginteractions.sgsnap |
gif |
| [surveillance](case_studies/su |