solograph
Code intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.
README
solograph
Code intelligence MCP server for Claude Code. Multi-project code graph, semantic search, session history, knowledge base, web search.
PyPI:
pip install solograph/uvx solograph
All vector search powered by FalkorDB (embedded, no Docker). No ChromaDB dependency.
Embeddings
Two backends, both produce 384-dimensional vectors:
| Backend | Model | Platform | Languages |
|---|---|---|---|
| MLX (primary) | multilingual-e5-small-mlx |
Apple Silicon | RU + EN |
| sentence-transformers (fallback) | all-MiniLM-L6-v2 |
Any | EN |
Auto-detects Apple Silicon → uses MLX. Falls back to sentence-transformers on other platforms.
Install MLX support (optional):
uv add solograph[mlx]
Install
uv add solograph
# or
pip install solograph
Usage
MCP Server (for Claude Code)
claude mcp add -s project solograph -- uvx solograph
Or add manually to .mcp.json:
{
"mcpServers": {
"solograph": {
"command": "uvx",
"args": ["solograph"]
}
}
}
CLI
solograph-cli init ~/my-projects # First-time setup (scan + build graph)
solograph-cli init ~/my-projects --deep # + imports, calls, inheritance
solograph-cli scan # Re-scan projects into graph
solograph-cli scan --deep # + imports, calls, inheritance (tree-sitter)
solograph-cli stats # Graph statistics
solograph-cli explain my-app # Architecture overview
solograph-cli xray ~/my-projects # Portfolio X-Ray (all projects at once)
solograph-cli diagram my-app # Mermaid diagram
solograph-cli query "MATCH (n) RETURN n LIMIT 5"
solograph-cli web-search "query" # Web search via SearXNG/Tavily
solograph-cli index-youtube -c GregIsenberg -n 10 # Index YouTube channel
solograph-cli index-youtube -u "https://youtube.com/watch?v=ID" # Index specific video by URL
solograph-cli index-youtube # Index all channels from channels.yaml
Install globally:
uv tool install solograph # → solograph + solograph-cli in PATH
Quick Start
# 1. Install
uv tool install solograph
# 2. Init — creates ~/.solo/, scans projects, builds graph
solograph-cli init ~/my-projects
# 3. Add MCP to Claude Code
claude mcp add -s project solograph -- uvx solograph
# 4. Done — MCP tools available in Claude Code
Configuration
Environment variables:
| Variable | Default | Description |
|---|---|---|
CODEGRAPH_DB_PATH |
~/.solo/codegraph.db |
FalkorDB code graph path |
CODEGRAPH_REGISTRY |
~/.solo/registry.yaml |
Project registry path |
CODEGRAPH_SCAN_PATH |
~/projects |
Where to scan for projects |
KB_PATH |
(none) | Knowledge base root (markdown files with YAML frontmatter) |
TAVILY_API_URL |
http://localhost:8013 |
Tavily-compatible search URL |
TAVILY_API_KEY |
(none) | API key for Tavily |
15 MCP Tools
codegraph_query— Cypher queries against code graphcodegraph_stats— graph statistics (projects, files, symbols, packages)codegraph_explain— architecture overview of a projectcodegraph_shared— packages shared across projectsproject_code_search— semantic code search (auto-indexes on first call)project_code_reindex— reindex project code into FalkorDB vectorssession_search— Claude Code session history searchproject_info— project registry infokb_search— knowledge base semantic searchweb_search— web search (Tavily/SearXNG)source_search— search indexed external sources (YouTube, Telegram)source_list— list indexed sources with document countssource_tags— auto-detected topics with video countssource_related— find related videos by shared tags
Web Search
The web_search tool connects to any Tavily-compatible API. Works great with self-hosted SearXNG + Tavily Adapter — private, no API keys, smart engine routing.
# Self-hosted (Docker, 1 minute setup)
git clone https://github.com/fortunto2/searxng-docker-tavily-adapter.git
cd searxng-docker-tavily-adapter
cp config.example.yaml config.yaml
docker compose up -d
# → http://localhost:8013/search (Tavily API)
# → http://localhost:8999 (SearXNG UI)
Or use Tavily API directly — set TAVILY_API_URL=https://api.tavily.com and TAVILY_API_KEY.
Smart engine routing auto-selects search engines by query type:
- tech: github, stackoverflow (keywords: python, react, code)
- academic: arxiv, google scholar (keywords: research, paper)
- product: brave, reddit, app stores (keywords: app, competitor, pricing)
- news: google news (keywords: news, latest, trend)
- general: google, duckduckgo, brave (default)
Graph Schema
Nodes
| Node | Key Properties | Source |
|---|---|---|
Project |
name, stack, path | registry.yaml |
File |
path, lang, lines, project | tree-sitter scan |
Symbol |
name, kind (class/function/method), file, line | tree-sitter AST |
Package |
name, version, source (npm/pip/spm/gradle) | manifest files |
Session |
session_id, project_name, started_at, slug | .claude/ history |
Edges
| Edge | From → To | Description |
|---|---|---|
HAS_FILE |
Project → File | Project contains file |
DEFINES |
File → Symbol | File defines symbol |
IMPORTS |
File → File/Package | Import relationship |
CALLS |
File → Symbol | File calls symbol |
INHERITS |
Symbol → Symbol | Class inheritance |
DEPENDS_ON |
Project → Package | Package dependency |
MODIFIED |
Session → File | Git history (lines added/removed) |
TOUCHED / EDITED / CREATED |
Session → File | Session file operations |
IN_PROJECT |
Session → Project | Session belongs to project |
Example Cypher Queries
-- Hub files (most imported)
MATCH (f:File)<-[:IMPORTS]-(other:File)
RETURN f.path, COUNT(other) AS importers
ORDER BY importers DESC LIMIT 10
-- Shared packages across projects
MATCH (p1:Project)-[:DEPENDS_ON]->(pkg:Package)<-[:DEPENDS_ON]-(p2:Project)
WHERE p1.name <> p2.name
RETURN pkg.name, COLLECT(DISTINCT p1.name) AS projects
-- Impact analysis: what breaks if I change this file?
MATCH (f:File {path: 'lib/utils.ts'})<-[:IMPORTS*1..3]-(dep:File)
RETURN dep.path
-- Most edited files (from session history)
MATCH (s:Session)-[:EDITED]->(f:File)
RETURN f.path, COUNT(s) AS sessions
ORDER BY sessions DESC LIMIT 10
-- Files touched by sessions in a project
MATCH (s:Session {project_name: 'my-app'})-[r]->(f:File)
RETURN f.path, type(r) AS action, COUNT(s) AS times
ORDER BY times DESC
YouTube Source Graph
Separate FalkorDB graph at ~/.solo/sources/youtube/graph.db:
| Node | Key Properties |
|---|---|
Channel |
name, handle, subscriber_count |
Video |
video_id, title, duration, view_count, created |
VideoChunk |
text, chapter, start_time, start_seconds, chunk_index, chunk_type, embedding (384-dim) |
Tag |
name |
| Edge | Description |
|---|---|
HAS_VIDEO |
Channel → Video |
HAS_CHUNK |
Video → VideoChunk |
TAGGED |
Video → Tag (weighted by confidence) |
Indexer: solograph-cli index-youtube — discovers videos via SearXNG, fetches metadata + VTT via yt-dlp, chunks by chapters, embeds, upserts into graph.
Channels: ~/.solo/sources/youtube/channels.yaml — YAML list of YouTube handles to index. Symlink from your project's channels.yaml.
Chunking: VTT subtitles parsed into timestamped segments, grouped by chapter boundaries via chunk_segments_by_chapters(). Each chunk has accurate start_seconds from real VTT timestamps.
VTT cache: ~/.solo/sources/youtube/vtt/{videoId}.vtt — persistent, reused on re-index.
ProductHunt Source Graph
Separate FalkorDB graph at ~/.solo/sources/producthunt/graph.db:
| Node | Key Properties |
|---|---|
SourceDoc |
doc_id, title, url, content, tags, created, popularity, embedding (384-dim) |
Maker |
username, name, headline, bio, points, streak_days, followers, twitter, linkedin |
Indexer: solograph-cli index-producthunt — scrapes ProductHunt GraphQL API v2, maps products to SourceDoc with upvotes as popularity.
solograph-cli index-producthunt -d 30 # Last 30 days
solograph-cli index-producthunt --all --resume # Full 3-year dump with checkpoint
solograph-cli import-producthunt data.jsonl # Import from JSONL file
Ranking: Search results are boosted by popularity (upvotes). At equal semantic relevance, products with more upvotes rank higher.
Search Server
HTTP API for vector search across all indexed sources. Designed to run as a Docker service alongside SearXNG.
# Standalone
solograph-search # starts on port 8002
# Docker (in searxng-docker-tavily-adapter)
docker compose up -d solograph-search
Endpoints:
GET /search?q=AI+tool&source=producthunt&n=5— semantic search (source optional)GET /sources— list indexed sources with countsGET /health— status
Popularity boost: Products with more upvotes rank higher at equal relevance. Score = cosine_similarity * 0.85 + log10(upvotes) * boost. Fetch 3x candidates, re-rank, return top N.
| Variable | Default | Description |
|---|---|---|
SOLOGRAPH_SEARCH_PORT |
8002 |
HTTP server port |
SOURCES_ROOT |
~/.solo/sources |
FalkorDB graphs directory |
Storage
- Code graph:
~/.solo/codegraph.db(FalkorDB) - Session vectors:
~/.solo/sessions/graph.db(FalkorDB) - KB vectors:
{KB_PATH}/.solo/kb/graph.db(FalkorDB) - Project vectors:
{project_path}/.solo/vectors/graph.db(per-project FalkorDB) - YouTube source:
~/.solo/sources/youtube/graph.db(FalkorDB) +youtube/vtt/(cached VTT files) +youtube/channels.yaml - ProductHunt source:
~/.solo/sources/producthunt/graph.db(FalkorDB) — 26k+ products with upvote-based ranking
Part of Solo Factory
Solograph is the MCP backend for Solo Factory — 9 skills and 3 agents for shipping startups faster. PyPI
Install skills + MCP together:
# Option 1: Skills for any agent (Claude Code, Cursor, Copilot, Gemini CLI, etc.)
npx skills add fortunto2/solo-factory --all
# Option 2: Claude Code plugin (skills + agents + MCP auto-start)
claude plugin marketplace add fortunto2/solo-factory
claude plugin install solo --scope user
Or use solograph standalone — just add to .mcp.json as shown above.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。