Your AI gets the compiler's eyes on your code and every library you use.
LSAI gives your AI agent live, compiler-grade intelligence on the code you're writing. xmp4 gives it the same on 900+ OSS libraries and 15,852 projects, pre-indexed. Together: the AI sees everything the compiler sees — no grep, no guessing, no blind spots.
Both free · Both open protocol (MCP) · Work with Claude Code, Cursor, VS Code
Two lenses. One pair of glasses.
LSAI — Your code, live
Install once. Your AI gets compiler-grade intelligence on the codebase you're actively developing — callers, impact, hierarchy, rename.
- "Who calls my
ProcessOrdermethod?" → 15 callers, exact lines - "What breaks if I change
PublishAsync?" → 27 tests, risk: MEDIUM - "Show me the inheritance chain of
BaseService" → full hierarchy - "Rename
userIdsafely across the workspace" → done, all references updated
xmp4 — Every library, pre-indexed
One line in your MCP config. Your AI navigates 900+ OSS libraries with type-resolved precision — callers, source, hierarchy, tests.
- "How does
MongoClient.connect()work?" → full source + 26 callers - "Show me who calls
app.routein Flask" → typed call sites - "What's the hierarchy of
Matrixin Eigen?" → compiler-resolved - "Find tests for
S3Client.PutObject" → real test files
LSAI tells you "your PublishAsync calls GetRequiredService".
xmp4 shows you how GetRequiredService is implemented in dotnet/runtime.
Your AI never guesses. It knows.
One question. Both lenses.
Developer asks: "What does my PublishAsync call, and how does that dependency work?"
lsai_callees("PublishAsync") → CreateScope() — PublishService.cs:22 → GetRequiredService<LsaiDbContext> — PublishService.cs:23 → Where<PublishedProjectEntity> — PublishService.cs:74
xmp4_source("GetRequiredService", project="dotnet/runtime") → public interface ISupportRequiredService { object GetRequiredService(Type serviceType); } // Implementation in ServiceProviderServiceExtensions.cs: // Throws InvalidOperationException if service not registered
lsai_impact("PublishAsync") → MEDIUM risk — 15 references, 15 callers, 27 tests affected Tests: PublishServiceTests, V32SpecComplianceTests, PublishSearchVectorTests... All tests named, all lines numbered.
Same answer. 42× cheaper.
Nine languages live. Both products.
| Language | LSAI | xmp4 | search | callers | hierarchy | source | impact | rename |
|---|---|---|---|---|---|---|---|---|
| C# | ● | ● | ● | ● | ● | ● | ● | ● |
| TypeScript | ● | ● | ● | ● | ● | ● | ● | ● |
| Python | ● | ● | ● | ● | ● | ● | ● | ◐ |
| Java | ● | ● | ● | ● | ● | ● | ● | ● |
| Rust | ● | ● | ● | ● | ● | ● | ● | ● |
| PHP | ● | ● | ● | ● | ● | ● | ● | ◐ |
| Go | ● | ● | ● | ● | ◐ | ● | ● | ● |
| JavaScript | ● | ● | ● | ● | ◐ | ● | ● | ● |
| C / C++ | ● | ● | ● | ◐ | ● | ● | ● | ● |
| Ruby | — | ● | ● | ◐ | ◐ | ● | — | — |
| Dart | — | ● | ● | ◐ | ◐ | ● | — | — |
| Scala | — | ◐ | ◐ | ◐ | ◐ | ◐ | — | — |
● both LSAI + xmp4 · ● LSAI only · ● xmp4 only · ◐ best-effort · — not yet
Good questions.
Two installs. Full vision.
LSAI — your code
One command. Analyzes whatever project you open Claude Code in.
# Install (Linux / macOS / WSL) curl -fsSL https://github.com/0ics-srls/Zerox.Lsai.Public/releases/latest/download/install.sh | bash # Add to .mcp.json (once) { "mcpServers": { "lsai": { "command": "~/.lsai/run", "args": ["--stdio"] } } } # Done. cd into your project, launch claude.
xmp4 — every library
One line in your MCP config. No install. No API key.
# Add to .mcp.json (Claude Desktop, Cursor, VS Code) { "mcpServers": { "xmp4": { "type": "http", "url": "https://mcp.example4.ai/mcp" } } } # Optional: install the xmp4 skill for Claude Code mkdir -p ~/.claude/skills/xmp4 && curl -sfL \ https://example4.ai/xmp4-skill.md \ -o ~/.claude/skills/xmp4/SKILL.md