How do I install Xmp4 — Semantic Code Knowledge For Your Stack?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Xmp4 — Semantic Code Knowledge For Your Stack need an API key?

No required environment variable is listed on this record.

What transport does Xmp4 — Semantic Code Knowledge For Your Stack use?

Xmp4 — Semantic Code Knowledge For Your Stack is reached over HTTP.

When was Xmp4 — Semantic Code Knowledge For Your Stack last checked?

Last checked 2026-10-18. OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.

Xmp4 — Semantic Code Knowledge For Your Stac MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.example4.ai/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http ai.example4-xmp4 https://mcp.example4.ai/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "ai.example4-xmp4": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.example4.ai/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.2.6
Last checked

16 tools

Tools

tools/listVoice mode preview

Tool	What it does
xmp4_callees	Find direct callees (methods called by) a symbol in a project. Navigate step-by-step by calling xmp4_callees again on interesting results.
xmp4_callers	Find direct callers of a symbol in a project. Navigate step-by-step by calling xmp4_callers again on interesting results.
xmp4_deps	List external dependencies of a project.
xmp4_grep	Server-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config ke
xmp4_guide	Usage guide for xmp4 tools — read this first to learn the correct workflow
xmp4_hierarchy	Get type hierarchy (base, interfaces, derived) for a symbol in a project.
xmp4_info	Get detailed information about a symbol in a project.
xmp4_outline	Get outline (all symbols) for a file in a project.
xmp4_projects	Search and browse projects by language and name. Use this first to discover projects, then use other tools with the repo name.
xmp4_search	Search symbols in a project. Use xmp4_projects first to find the project identifier.
xmp4_server	Get server information, version, and capabilities
xmp4_source	Extract source code for a symbol in a project.
xmp4_symbol_at	LSP-style position→symbol lookup. Given (file_path, line, column) returns the symbol whose occurrence covers that cursor position. line is 1-based; column is 0-based. Use after xmp4_outline/xmp4_view when you know coordinates and want the canonical symbol.
xmp4_tests_for	Find direct tests that exercise a given symbol (direct callers filtered to test-file candidates per language pattern: CSharp/Java/PHP: Test(s).<ext>; Python: test_.py / _test.py; TypeScript/JavaScript: .spec/test.{ts,js}; Rust: *_tests.rs / tests/; etc.).
xmp4_usages	Find all usages/references of a symbol in a project.
xmp4_view	Read a raw file excerpt from an indexed project by line range. Use after xmp4_search/xmp4_outline locates the region of interest, or to expand a truncated xmp4_source snippet. Hard cap of 500 lines per call.

xmp4

Stop grepping library source.

Your AI gets the compiler's view of 856 OSS libraries via MCP.

Real callers. Real source. Real hierarchy. In 3 tool calls.

→ Landing page · → Benchmark whitepaper · → Connect in 30 seconds

The 30-second pitch

Your AI coding agent is burning tokens grepping OSS libraries it will barely use. xmp4 is a hosted MCP server that pre-indexes 856 popular open-source libraries with SCIP — the semantic code format Sourcegraph uses — and serves them through 17 tools. No clone. No grep. No false positives.

ASK: "Who calls Flask.wsgi_app in the flask repo and what does it do?"

with grep + local clone:
  git clone flask/flask          ~40 MB,   ~2 min
  grep -rn "wsgi_app" .          200+ matches, mostly noise
  cat src/flask/app.py | sed ... read 1000+ lines to find the body
  filter false positives         model spends tokens deciding what's real
  ──────────────────────────────────────
  total:                         ~15,000 tokens + disk + wall time

with xmp4:
  xmp4_info(symbol_name="Flask",    file_path="src/flask/app.py")         → signature,  20 tok
  xmp4_source(symbol_name="wsgi_app", file_path="src/flask/app.py")       → body,      180 tok
  xmp4_callers(symbol_name="wsgi_app", file_path="src/flask/app.py")      → 1 caller,   50 tok
  ──────────────────────────────────────
  total:                                                                    ~250 tokens

xmp4 is 60× cheaper here — and every result is SCIP-resolved, not text-matched.

The measured numbers (4 big OSS libs · reproducible)

Same realistic question on spring-boot · tokio · django · efcore: "give me the signature, body, and real callers of X."

	xmp4	grep + clone	GitMCP	Context7
Total tokens (same question)	1 558	2 978	65 629	—
vs xmp4	1×	1.9× more	42× more	can't answer
Returns real source body?	✅	✅ noisy	✗ file paths only	✗ curated docs only
Semantic callers?	✅	✗	✗	✗
Type hierarchy?	✅	✗	✗	✗
Setup cost	0	GBs of clone	0	0

GitMCP and Context7 look cheaper per call because they return less. To reach the same answer, GitMCP balloons to 42× more tokens — and still can't produce the semantic caller list. Context7 can't at any cost. Full whitepaper with Python harness →

Connect in 30 seconds

// Claude Code / Cursor / Claude Desktop — project `.mcp.json` or client config
{
  "mcpServers": {
    "xmp4": {
      "type": "http",
      "url": "https://mcp.example4.ai/mcp"
    }
  }
}

(The ready-to-paste config also lives at .mcp.json in this repo.)

Teach Claude how to use xmp4 (optional but recommended)

Install the xmp4 skill once per version — Claude will pick the cheapest tool path automatically (tests_for + view over grep):

# Claude Code
mkdir -p ~/.claude/skills/xmp4 && \
  curl -sfL https://example4.ai/xmp4-skill.md -o ~/.claude/skills/xmp4/SKILL.md

# Other clients: just tell Claude to read the URL when using xmp4 tools
#   https://example4.ai/xmp4-skill.md

Restart your client. Then try (every step verified live 2026-04-24):

"Using xmp4, find the Flask class in flask/Flask and list its usages."

You should see Type Flask src/flask/app.py:81 and 165 usages across 33 result pages. One semantic call per question. Zero grep loops.

Setup for Cursor · Claude Desktop · Continue · Windsurf → docs/connect-instructions.md

The 17 tools

Full reference with live examples

Semantic core (where the value lives) xmp4_projects · xmp4_search · xmp4_info · xmp4_usages · xmp4_callers · xmp4_callees · xmp4_hierarchy · xmp4_outline · xmp4_source · xmp4_tests_for · xmp4_deps · xmp4_symbol_at

Convenience xmp4_view (raw file excerpt by line range) · xmp4_grep (server-side regex when semantics isn't enough)

Meta xmp4_guide (returns a versioned skill pointer to https://example4.ai/xmp4-skill.md — fetch once per version and save as a local Claude Code skill; embeds a minimal cheatsheet as offline fallback) · xmp4_server (version + stats)

Language coverage

Tier 1 — full coverage contract C# · TypeScript · Python · Java · Rust · PHP

Tier 2 — best-effort, documented quirks Go · JavaScript · Dart · Ruby · C++

Every known limitation — empty hierarchy.base on TS/Rust/Java/PHP, Python cross-module usages under-count, C# explicit-interface-impl dotted-name behaviour — is listed verbatim in docs/tiers-and-quirks.md. We'd rather set expectations correctly than have a reviewer find a gap and assume the whole thing is inflated.

Coverage grows by demand, not by guesswork

The index currently holds 856 repositories / 15 921 SCIP-indexed projects. We add new libraries based on two signals, combined:

Aggregate query logs — symbol names and project filters, no PII, no user code. If many AI agents search for a library we don't have, we see it.
Your request — file a repo-request issue with the GitHub URL, the language, and one concrete query you want to run. A single user request + downstream query demand almost always means indexed within days.

A public /stats/top-missing endpoint is planned — full transparency on what drives the growth loop.

Privacy — short version

✓ We log: aggregate query counts (symbol/project/tool names, coarse timestamps) to grow the index by demand.
✗ We don't log: the contents of your codebase · personal identifiers · request bodies beyond declared tool parameters.
Standard nginx access logs kept 7 days for abuse prevention, then purged. Not joined with query tallies.

Full detail → docs/privacy.md.

Status

🟢 Live — mcp.example4.ai v1.2.1 · 856 repos · 15 921 projects · 17 tools · 11 languages
🟢 Benchmark published — reproducible whitepaper with Python harness
🟢 Listed on the Official MCP Registry as ai.example4/xmp4 (DNS-authed on example4.ai)
🟢 Smithery — smithery.ai/servers/0ics-srl/xmp4
🟢 Cursor Directory — cursor.directory/plugins/lsai-xmp4public
🔧 More registry submissions in flight — MCP.so, mcpservers.org, [email protected], awesome-lists (PRs open on punkpeye/jaw9c/appcypher)
🔧 Demand-driven growth loop — in progress

What's in this repository

Path	Purpose
`docs/connect-instructions.md`	5 MCP clients, proof-of-life sequence, troubleshooting
`docs/tool-reference.md`	17 tools with live-verified examples and workflow rules
`docs/tiers-and-quirks.md`	Language tier matrix + every known limitation, verbatim
`docs/privacy.md`	What we log, what we don't, GDPR contact
`docs/request-repo.md`	How the demand-driven queue actually works
`.mcp.json`	Ready-to-paste MCP client config (`type: http`, URL)
`skills/xmp4/SKILL.md`	Claude Code skill — workflow, cost budget, grep policy, common mistakes
`html/xmp4-skill.md`	Same skill, served publicly at `https://example4.ai/xmp4-skill.md`
`server.json`	Official MCP Registry manifest (DNS-authed `ai.example4/xmp4`)
`glama.json`	Glama catalog auto-index hook
`.github/ISSUE_TEMPLATE/`

LSAI protocol — open spec for semantic code intelligence in AI agents.
SCIP — the semantic code format xmp4 is built on (Sourcegraph-developed, BSD-3).
Model Context Protocol — the open transport spec xmp4 speaks.

License

Apache 2.0 for this documentation repository — see LICENSE. The hosted mcp.example4.ai endpoint is free for personal and commercial use (TOS link pending).

Commercial licensing or self-hosted deployment enquiries → open a GitHub issue labelled commercial on this repo.

Made with semantic intelligence instead of grep.

SCIP · MCP · LSAI

Xmp4 — Semantic Code Knowledge For Your Stack

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Xmp4 — Semantic Code Knowledge For Your Stack?

Does Xmp4 — Semantic Code Knowledge For Your Stack need an API key?

What transport does Xmp4 — Semantic Code Knowledge For Your Stack use?

When was Xmp4 — Semantic Code Knowledge For Your Stack last checked?

Documentation

xmp4

Stop grepping library source.

Your AI gets the compiler's view of 856 OSS libraries via MCP.

The 30-second pitch

The measured numbers (4 big OSS libs · reproducible)

Connect in 30 seconds

Teach Claude how to use xmp4 (optional but recommended)

The 17 tools

Language coverage

Coverage grows by demand, not by guesswork

Privacy — short version

Status

What's in this repository

Related

License