Skip to main content

Give your AI coding assistant real code understanding — powered by the same engines VS Code uses

Project description

scope-mcp

A tool that gives your AI coding assistant superpowers. Instead of guessing what your code does, it gets real answers straight from the same engines VS Code uses — so it actually understands functions, classes, types, and where things connect.

No setup. No indexing. Just works.

What's the problem?

When you ask an AI to "find where get_lsp is called," most tools do a text search — like Ctrl+Shift+F. That returns everything named get_lsp: the definition, comments, imports, false positives. You have to dig through the noise.

┌─ grep (text search) ─────────────────────┐
│  project.py:75  def get_lsp(self, lang)   │  ← definition (not a call)
│  project.py:110 return await get_lsp(lang)│  ← actual call
│  project.py:117 lsp = await get_lsp(lang) │  ← actual call
│  project.py:81  cfg = LSP_REGISTRY...     │  ← noise
│  project.py:109 async def get_lsp_for...  │  ← noise
│    5 results · 3 are noise                │
└───────────────────────────────────────────┘

┌─ scope (smart search) ────────────────────┐
│  [call site] project.py:110               │
│  [call site] project.py:117               │
│    2 results · 0 noise                    │
└───────────────────────────────────────────┘

Scope asks the compiler instead. You get only what you actually asked for.

What you can do with it

Instead of digging through files... Just ask scope... You get
Grepping for a function name and filtering out junk find_references("get_lsp") Only the places where it's actually called — no noise
Reading a whole file to figure out what's in it explain_file("server.py") A clean summary: language, line count, every function and class
Hunting through 50 files to find where an interface is used implementations("IEventHandler") One answer with all the implementations
Tracing who calls what by hand call_hierarchy("validate_token") A tree of callers and callees, 3 levels deep
Scanning a big diff to see what changed changed_since("HEAD~3") Just the changed files and affected symbols

How it works

  1. Scope looks at your project — it spots what languages you're using (Python, TypeScript, Rust, Go, C++) from files like package.json or Cargo.toml.
  2. It sets up the brain — launches the same language engine your editor uses (pyright, tsserver, rust-analyzer, gopls). If missing, it installs one automatically.
  3. Your AI asks, scope answers — every question hits that engine live. No stale data, no sync jobs, no waiting.
AI Assistant (Claude, Codex, etc.)  ←→  scope  ←→  Language Engine
                                              (pyright, tsserver, etc.)

Setup

pip install scope-mcp

Then add one line to your AI client's config:

Claude Desktop / Code

{
  "mcpServers": {
    "scope": {
      "command": "scope",
      "args": ["--project", "."]
    }
  }
}

Any AI coding tool

command:  scope
args:     ["--project", "/path/to/your/project"]
transport: stdio

From source

git clone https://github.com/yourname/scope-mcp
cd scope-mcp
pip install -e .

Optional extras: rg (ripgrep) for text searches, git for change tracking.

Languages scope understands

Language Detected when it sees... Scope handles setup
Python pyproject.toml · setup.py · requirements.txt ✅ Installs pyright automatically
TypeScript / JavaScript tsconfig.json · package.json ✅ Installs tsserver automatically
Rust Cargo.toml ✅ Installs rust-analyzer automatically
Go go.mod ✅ Installs gopls automatically
C / C++ CMakeLists.txt · compile_commands.json ⚠️ You install clangd manually

Project layout

scope/
├── __init__.py
├── __main__.py       # Where scope starts — just runs `scope --project .`
├── server.py         # All the commands (tools) your AI can call
├── project.py        # Figures out your project and starts language engines
├── lsp_client.py     # Talks to language engines behind the scenes
└── lsp_registry.py   # Knows which engine to use for each language

Requirements

  • Python 3.11 or newer
  • ripgrep (optional, for text search)
  • git (optional, for change tracking)

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

scope_mcp-0.1.0.tar.gz (16.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

scope_mcp-0.1.0-py3-none-any.whl (15.7 kB view details)

Uploaded Python 3

File details

Details for the file scope_mcp-0.1.0.tar.gz.

File metadata

  • Download URL: scope_mcp-0.1.0.tar.gz
  • Upload date:
  • Size: 16.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.10

File hashes

Hashes for scope_mcp-0.1.0.tar.gz
Algorithm Hash digest
SHA256 dbaecd18031cd926ad3e393ee203394cdce83257e50b07163c2f7b3abdde550a
MD5 d3368af63fe729adfd8d317d87eb15c3
BLAKE2b-256 020c54420665530fdb750f13c9628e122a1918f91f26b96dc1be518e1a0397c4

See more details on using hashes here.

File details

Details for the file scope_mcp-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: scope_mcp-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 15.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.10

File hashes

Hashes for scope_mcp-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 e9c2b0f09a2f7ee7d04124db28d8758fbf2240b8a25babd77538353c63a75293
MD5 7462bb7f88264f048d249ee534cc0d93
BLAKE2b-256 f8b01b4521e0e73f3afd8353ce3f477fa2a4563176b9a06c3ea90be02b651a2e

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page