Skip to content

Commit 54cb3ec

Browse files
DevRohit06claude
DevRohit06
and
claude
committed
Add comparison page (Lito Graph vs Context7) and public hosting docs
- README: add public graph hosting section + comparison table - docs/introduction/comparison.mdx: detailed feature comparison with concrete examples showing graph vs RAG tradeoffs - Sidebar: add comparison page to Introduction group Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 18c62c3 commit 54cb3ec

File tree

3 files changed

+175
-1
lines changed

3 files changed

+175
-1
lines changed

‎README.md‎

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,61 @@ Add to your MCP settings:
135135
}
136136
```
137137

138+
## Public Graph Hosting
139+
140+
Build with `--base-url` so every node gets a full public URL:
141+
142+
```bash
143+
lito-graph build -i ./docs -o ./graph.json --base-url https://docs.example.com
144+
```
145+
146+
Each node gets a `url` field agents can navigate to:
147+
148+
```json
149+
{
150+
"title": "Create Workspace",
151+
"slug": "/api/create-workspace",
152+
"url": "https://docs.example.com/api/create-workspace"
153+
}
154+
```
155+
156+
Host `graph.json` alongside your docs (e.g., in `public/`), then any agent can connect remotely:
157+
158+
```bash
159+
lito-graph serve --url https://docs.example.com/graph.json
160+
```
161+
162+
Works with **any** docs framework — Lito, Mintlify, Docusaurus, Fern, VitePress, GitBook. If it has Markdown files, Lito Graph can compile them.
163+
164+
## Lito Graph vs Context7 MCP
165+
166+
Lito Graph and [Context7](https://context7.com) solve **different problems**. Use both.
167+
168+
| | Context7 | Lito Graph |
169+
|---|---|---|
170+
| **Purpose** | Look up third-party library docs | Operate on your own product/domain |
171+
| **Data** | Flat text chunks (RAG) | Typed nodes + 14 edge types (graph) |
172+
| **Relationships** | None — isolated text | `ACTS_ON`, `USES_API`, `RELATED_TO`, etc. |
173+
| **Planning** | Single page at a time | Full workflows with ordered steps + linked APIs |
174+
| **Safety** | Hope the agent reads the warning | `requires_human_approval`, `risk_level`, `guardrails` as machine-readable fields |
175+
| **Completeness** | Top-k search (might miss things) | Graph traversal (guaranteed exhaustive) |
176+
| **Setup** | Zero — works instantly | Requires build step + optional frontmatter |
177+
| **Privacy** | Cloud service | Fully local, self-hosted |
178+
179+
### When to use what
180+
181+
| Scenario | Best tool |
182+
|----------|-----------|
183+
| "How do I use Express middleware?" | Context7 |
184+
| "What's the full onboarding flow for our platform?" | **Lito Graph** |
185+
| "What's the React useState API?" | Context7 |
186+
| "Which of our APIs require admin permissions?" | **Lito Graph** |
187+
| "How do I configure Tailwind?" | Context7 |
188+
| "What happens if workspace creation fails?" | **Lito Graph** |
189+
190+
**Context7** prevents hallucinating API signatures (external knowledge).
191+
**Lito Graph** prevents unsafe actions on your own systems (internal knowledge).
192+
138193
## Graph Data Model
139194

140195
### Node Types

‎docs/docs-config.json‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,8 @@
4545
"label": "Introduction",
4646
"items": [
4747
{ "label": "What is Lito Graph?", "slug": "introduction" },
48-
{ "label": "Architecture", "slug": "introduction/architecture" }
48+
{ "label": "Architecture", "slug": "introduction/architecture" },
49+
{ "label": "Lito Graph vs Context7", "slug": "introduction/comparison" }
4950
]
5051
},
5152
{

‎docs/introduction/comparison.mdx‎

Lines changed: 118 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,118 @@
1+
---
2+
title: Lito Graph vs Context7
3+
description: "How Lito Graph compares to Context7 MCP and other docs-for-agents tools — when to use each, and why they're complementary."
4+
keywords:
5+
- lito graph vs context7
6+
- mcp comparison
7+
- rag vs graph
8+
- agent documentation
9+
author: Lito Team
10+
publishDate: "2026-02-27"
11+
tags:
12+
- introduction
13+
- comparison
14+
section: Introduction
15+
---
16+
17+
# Lito Graph vs Context7
18+
19+
Lito Graph and [Context7](https://context7.com) solve **different problems**. They're complementary — use both.
20+
21+
## The Core Difference
22+
23+
**Context7** is a **live docs lookup** for third-party libraries. Ask "how do I use React hooks?" and it fetches the latest React docs. It prevents hallucination by giving agents real API signatures.
24+
25+
**Lito Graph** compiles **your own docs** into a typed knowledge graph that agents can traverse, plan with, and act on safely. It's not a search tool — it's a reasoning layer.
26+
27+
```
28+
Your agent's toolbox:
29+
├── Context7 MCP → "How do I use this library?" (external knowledge)
30+
└── Lito Graph MCP → "How does our system work?" (internal knowledge)
31+
├── What entities exist?
32+
├── What APIs act on them?
33+
├── What workflows should I follow?
34+
└── What guardrails must I respect?
35+
```
36+
37+
## Feature Comparison
38+
39+
| | Context7 | Lito Graph |
40+
|---|---|---|
41+
| **Purpose** | Look up third-party library docs | Operate on your own product/domain |
42+
| **Data format** | Flat text chunks (RAG-style) | Typed nodes + 14 edge types (graph) |
43+
| **Relationships** | None — isolated text results | `ACTS_ON`, `USES_API`, `RELATED_TO`, etc. |
44+
| **Planning** | Returns one page at a time | Full workflows with ordered steps + linked API details |
45+
| **Safety** | Hopes the agent reads warnings | `requires_human_approval`, `risk_level`, `guardrails` as machine-readable fields |
46+
| **Completeness** | Top-k search results (might miss things) | Graph traversal (guaranteed exhaustive) |
47+
| **Setup** | Zero — works instantly | Requires build step + optional frontmatter annotations |
48+
| **Freshness** | Always live, no build step | Requires rebuild when docs change |
49+
| **Privacy** | Cloud service (queries go to their servers) | Fully local, self-hosted, private |
50+
| **Breadth** | Thousands of libraries out of the box | Only your own docs |
51+
52+
## Where Each Wins
53+
54+
### Context7 is better for:
55+
56+
- **Third-party libraries** — "How does Express.js routing work?"
57+
- **Quick lookups** — zero setup, instant results
58+
- **Staying current** — always fetches the latest published docs
59+
- **Breadth** — covers thousands of popular libraries
60+
61+
### Lito Graph is better for:
62+
63+
- **Your own domain** — "What entities exist in our platform?"
64+
- **Relationships** — "What APIs act on the Workspace entity?"
65+
- **Multi-step planning** — "Walk me through the full onboarding workflow"
66+
- **Safety enforcement** — "Does this workflow need human approval?"
67+
- **Impact analysis** — "If I change Workspace, what breaks?"
68+
- **Completeness** — "Show me everything connected to this entity"
69+
- **Privacy** — internal docs never leave your machine
70+
71+
## Concrete Example
72+
73+
### With Context7
74+
75+
```
76+
Agent: "How do I create a workspace?"
77+
Context7: Returns a docs page about workspace creation
78+
Agent: Reads it, tries to call the API
79+
→ Might miss the preconditions
80+
→ Might not know about the onboarding workflow
81+
→ Doesn't know it needs human approval
82+
```
83+
84+
### With Lito Graph
85+
86+
```
87+
Agent: "How do I create a workspace?"
88+
→ search("workspace") finds ConceptNode(Workspace)
89+
→ find_apis_for_entity("Workspace") returns 3 APIs with full metadata
90+
→ get_workflow("onboard_new_workspace") returns:
91+
- 4 ordered steps with linked API details
92+
- preconditions: user_authenticated, billing_plan_active
93+
- guardrails: "Never delete existing workspaces"
94+
- requires_human_approval: true
95+
→ Agent asks for approval before proceeding
96+
→ Executes steps in order, checking preconditions
97+
→ If step fails, follows recovery path
98+
```
99+
100+
## The Bottom Line
101+
102+
Context7 prevents hallucinating API signatures.
103+
Lito Graph prevents **unsafe actions on your own systems**.
104+
105+
Different problems. Complementary solutions. Use both.
106+
107+
## When to Use What
108+
109+
| Scenario | Best tool |
110+
|----------|-----------|
111+
| "How do I use Express.js middleware?" | Context7 |
112+
| "What's the full onboarding flow for our platform?" | Lito Graph |
113+
| "What's the React useState API?" | Context7 |
114+
| "Which of our APIs require admin permissions?" | Lito Graph |
115+
| "How do I configure Tailwind?" | Context7 |
116+
| "What happens if workspace creation fails?" | Lito Graph |
117+
| "What's new in Next.js 15?" | Context7 |
118+
| "What entities does the delete API affect?" | Lito Graph |

0 commit comments

Comments
 (0)