Dep Scope

Symbol-level npm dependency analysis: scan verdicts, native alternatives, migration prompts.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": [
        "-y",
        "@florianbruniaux/dep-scope"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (5)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Dep Scope.

scan_project

Full dependency scan with verdicts

analyze_package

Symbol-level breakdown of one package

get_migration_candidates

List all RECODE_NATIVE + CONSOLIDATE packages

generate_migration_prompt

Generate a migration prompt inline

find_duplicates

Detect overlapping libraries

Documentation Overview

dep-scope

Florian BRUNIAUX · AI Founding Engineer @ Méthode Aristote
13 years from developer to CTO / VP Eng · Blog ↗ · Projects ↗

Symbol-level dependency analysis + LLM-ready migration prompts for TypeScript/JavaScript projects.

"Knip tells you what's unused. dep-scope tells you how you use what you keep, and generates the prompt to remove it."

When to use dep-scope

Good use cases:

Legacy project audit: Finding lodash functions that now have native equivalents
Library consolidation: Do we really need 3 icon libraries?
Migration: Generate a context-aware prompt and let Claude Code do the refactoring
Curiosity: "Which symbols from this 50KB library do we actually use?"

Not the right tool if:

You just want unused deps → use Knip instead
Your codebase is already well-maintained → dep-scope will mostly say "KEEP"

Quick Example

bash

$ dep-scope scan

═══════════════════════════════════════════
  dep-scope Analysis Report
═══════════════════════════════════════════

Summary:
  Total dependencies: 45
  ✓ Keep:          38
  ↻ Recode Native: 3
  ✗ Remove:        2
  ⊕ Peer Dep:      4

Action Items:
  Remove (unused):
    ✗ moment
    ✗ has-flag

  Recode to native:
    ↻ lodash.debounce (1 symbol) → custom debounce function
    ↻ array-includes (1 symbol) → Array.prototype.includes
    ↻ left-pad (1 symbol) → String.prototype.padStart

How it compares

Feature	Knip	Depcheck	Moderne	dep-scope
Unused detection	✅ Excellent	✅ Good	❌	⚠️ Basic
Config file scanning	✅	✅	❌	✅
Symbol-level analysis	❌	❌	✅	✅
Native alternatives database	❌	❌	✅ (lodash)	✅ 195 packages
e18e micro-utilities coverage	❌	❌	❌	✅
Transitive graph analysis	❌	❌	❌	✅
Monorepo workspace support	⚠️	❌	❌	✅
Duplicate detection	❌	❌	❌	✅
LLM migration prompt	❌	❌	❌	✅
MCP Server (AI editors)	❌	❌	❌	✅
OSS / free	✅	✅	❌ enterprise	✅

Recommendation: Use Knip for unused detection, dep-scope for deeper analysis and migration. They work well together (dep-scope auto-detects Knip if installed).

Installation

CLI (global):

Terminal

npm install -g @florianbruniaux/dep-scope

Without installation:

Terminal

npx @florianbruniaux/dep-scope scan

MCP Server (AI editors — no CLI needed):

Add to your editor's MCP config and the server runs on demand via npx. See the MCP Server section below for per-editor config snippets.

From source:

bash

git clone https://github.com/FlorianBruniaux/node-dep-scope.git
cd node-dep-scope
npm install && npm run build && npm install -g .

Quick Start

bash

cd /path/to/your/project

dep-scope init                        # configure dep-scope for your project (interactive)
dep-scope scan                        # full scan
dep-scope scan --root                 # scan full project, including scripts/ tools/ bin/
dep-scope scan --check-duplicates     # include duplicate detection
dep-scope scan --check-transitive     # surface transitive polyfills (e18e database)
dep-scope scan --each-workspace       # monorepo: scan each package individually
dep-scope migrate                     # generate migration prompts for all candidates
dep-scope migrate lodash              # target a specific package
dep-scope report -o ./audit.md        # markdown report

Setup: `dep-scope init`

Run dep-scope init before your first scan. The wizard detects your project and generates a config in 4 questions:

Code

dep-scope init

  Detected: Next.js project
  Found dirs: src/, scripts/, app/

? Source directories to scan:
  ● Auto-detected: src/, scripts/, app/  (recommended)
  ○ Full project root (.) — includes everything
  ○ Choose directories manually...

? Include devDependencies in scan? (y/N)
? Symbol threshold for RECODE_NATIVE verdict: (5)
? Config format:
  ● .depscoperc.json  (simple JSON, recommended)
  ○ depscope.config.ts  (TypeScript with autocomplete)

✓ Created .depscoperc.json
  Preset: react  |  Dirs: src, scripts, app  |  Threshold: 5

Use -y to skip prompts in CI: dep-scope init --yes.

Getting accurate results

Auto-detection covers: src, app, lib, pages, components, hooks, server, scripts, tools, bin, cli. If your project has code elsewhere, pass --root to scan everything, or set srcPaths explicitly in .depscoperc.json:

config.json

{
  "srcPaths": ["src", "app", "scripts", "tools"]
}

False positive "unused" verdict? The package may be used in a directory outside the scan scope (scripts/, tools/, etc.). Run dep-scope scan --root to verify before removing anything. When a removal recommendation appears with a narrow scan scope, dep-scope will warn you.

Config file detection

dep-scope automatically scans config files at the project root to avoid false "unused" verdicts for packages referenced as strings — a common pattern for CLI tools, test runners, and framework plugins.

Detected automatically:

Config file	Examples detected
`package.json` scripts	`"lint": "oxlint ."`, `"format": "oxfmt ."`
`vitest.config.*`	`environment: "jsdom"`, `setupFiles: ["@testing-library/jest-dom"]`
`vite.config.*`	`plugins: ["@vitejs/plugin-vue"]`
`next.config.*`	`turbo.rules["*.svg"].loaders: ["@svgr/webpack"]`
`.storybook/main.*`	`addons: ["@storybook/addon-mcp"]`

These packages will appear as INVESTIGATE (or KEEP if well-used) rather than REMOVE.

Opt-out — disable specific detectors in .depscoperc.json:

config.json

{
  "stringReferences": {
    "disable": ["storybook-config"]
  }
}

Available detector IDs: package-json-scripts, vitest-config, vite-config, next-config, storybook-config. Use "disable": "all" to turn off config scanning entirely.

Extend with custom detectors — in depscope.config.ts:

server.ts

import { defineConfig, defineDetector } from "@florianbruniaux/dep-scope";

export default defineConfig({
  stringReferences: {
    detectors: [
      defineDetector({
        id: "my-tool-config",
        label: "my-tool.config.json",
        filePatterns: ["my-tool.config.json"],
        async detect(filePath, ctx) {
          // return StringReference[] for packages found in this file
          return [];
        },
      }),
    ],
  },
});

MCP Server

dep-scope exposes a Model Context Protocol server so AI editors (Claude Code, Cursor, Windsurf) can query your dependencies inline — no CLI, no markdown files, no copy-paste.

Listed on the official MCP Registry: io.github.FlorianBruniaux/dep-scope

Available tools

Tool	Params	What it does
`scan_project`	`projectPath`, `srcPaths`, `threshold`, `includeDev`, `checkDuplicates`, `checkTransitive`, `withKnip`	Full dependency scan with verdicts
`analyze_package`	`packageName`, `projectPath`, `srcPaths`	Symbol-level breakdown of one package
`get_migration_candidates`	`projectPath`	List all RECODE_NATIVE + CONSOLIDATE packages
`generate_migration_prompt`	`packageName`, `projectPath`	Generate a migration prompt inline
`find_duplicates`	`projectPath`	Detect overlapping libraries

Setup

Add the following mcpServers entry to your editor's config. The server runs on demand via npx — no global install required.

Claude Code — ~/.claude.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Cursor — ~/.cursor/mcp.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Windsurf — ~/.codeium/windsurf/mcp_config.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

372

Package downloads in the last 30 days.

Last commit

24d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Dep Scope

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "dep-scope": { "command": "npx", "args": ["-y","@florianbruniaux/dep-scope"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/dep-scope?style=directory)](https://allmcps.com/mcp/dep-scope)

HTML Embed

<a href="https://allmcps.com/mcp/dep-scope"><img src="https://allmcps.com/api/badge/dep-scope?style=directory" alt="Dep Scope on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

10/10 checks healthy over the last 46d

57Quality signal: Good · 57/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools24/30

Adoption & activity9/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @florianbruniaux/dep-scope (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Dep Scope →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Dep Scope

Symbol-level npm dependency analysis: scan verdicts, native alternatives, migration prompts.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": [
        "-y",
        "@florianbruniaux/dep-scope"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Capabilities & Tool Schemas (5)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Dep Scope.

scan_project

Full dependency scan with verdicts

analyze_package

Symbol-level breakdown of one package

get_migration_candidates

List all RECODE_NATIVE + CONSOLIDATE packages

generate_migration_prompt

Generate a migration prompt inline

find_duplicates

Detect overlapping libraries

Documentation Overview

dep-scope

Florian BRUNIAUX · AI Founding Engineer @ Méthode Aristote
13 years from developer to CTO / VP Eng · Blog ↗ · Projects ↗

Symbol-level dependency analysis + LLM-ready migration prompts for TypeScript/JavaScript projects.

"Knip tells you what's unused. dep-scope tells you how you use what you keep, and generates the prompt to remove it."

When to use dep-scope

Good use cases:

Legacy project audit: Finding lodash functions that now have native equivalents
Library consolidation: Do we really need 3 icon libraries?
Migration: Generate a context-aware prompt and let Claude Code do the refactoring
Curiosity: "Which symbols from this 50KB library do we actually use?"

Not the right tool if:

You just want unused deps → use Knip instead
Your codebase is already well-maintained → dep-scope will mostly say "KEEP"

Quick Example

bash

$ dep-scope scan

═══════════════════════════════════════════
  dep-scope Analysis Report
═══════════════════════════════════════════

Summary:
  Total dependencies: 45
  ✓ Keep:          38
  ↻ Recode Native: 3
  ✗ Remove:        2
  ⊕ Peer Dep:      4

Action Items:
  Remove (unused):
    ✗ moment
    ✗ has-flag

  Recode to native:
    ↻ lodash.debounce (1 symbol) → custom debounce function
    ↻ array-includes (1 symbol) → Array.prototype.includes
    ↻ left-pad (1 symbol) → String.prototype.padStart

How it compares

Feature	Knip	Depcheck	Moderne	dep-scope
Unused detection	✅ Excellent	✅ Good	❌	⚠️ Basic
Config file scanning	✅	✅	❌	✅
Symbol-level analysis	❌	❌	✅	✅
Native alternatives database	❌	❌	✅ (lodash)	✅ 195 packages
e18e micro-utilities coverage	❌	❌	❌	✅
Transitive graph analysis	❌	❌	❌	✅
Monorepo workspace support	⚠️	❌	❌	✅
Duplicate detection	❌	❌	❌	✅
LLM migration prompt	❌	❌	❌	✅
MCP Server (AI editors)	❌	❌	❌	✅
OSS / free	✅	✅	❌ enterprise	✅

Recommendation: Use Knip for unused detection, dep-scope for deeper analysis and migration. They work well together (dep-scope auto-detects Knip if installed).

Installation

CLI (global):

Terminal

npm install -g @florianbruniaux/dep-scope

Without installation:

Terminal

npx @florianbruniaux/dep-scope scan

MCP Server (AI editors — no CLI needed):

Add to your editor's MCP config and the server runs on demand via npx. See the MCP Server section below for per-editor config snippets.

From source:

bash

git clone https://github.com/FlorianBruniaux/node-dep-scope.git
cd node-dep-scope
npm install && npm run build && npm install -g .

Quick Start

bash

cd /path/to/your/project

dep-scope init                        # configure dep-scope for your project (interactive)
dep-scope scan                        # full scan
dep-scope scan --root                 # scan full project, including scripts/ tools/ bin/
dep-scope scan --check-duplicates     # include duplicate detection
dep-scope scan --check-transitive     # surface transitive polyfills (e18e database)
dep-scope scan --each-workspace       # monorepo: scan each package individually
dep-scope migrate                     # generate migration prompts for all candidates
dep-scope migrate lodash              # target a specific package
dep-scope report -o ./audit.md        # markdown report

Setup: `dep-scope init`

Run dep-scope init before your first scan. The wizard detects your project and generates a config in 4 questions:

Code

dep-scope init

  Detected: Next.js project
  Found dirs: src/, scripts/, app/

? Source directories to scan:
  ● Auto-detected: src/, scripts/, app/  (recommended)
  ○ Full project root (.) — includes everything
  ○ Choose directories manually...

? Include devDependencies in scan? (y/N)
? Symbol threshold for RECODE_NATIVE verdict: (5)
? Config format:
  ● .depscoperc.json  (simple JSON, recommended)
  ○ depscope.config.ts  (TypeScript with autocomplete)

✓ Created .depscoperc.json
  Preset: react  |  Dirs: src, scripts, app  |  Threshold: 5

Use -y to skip prompts in CI: dep-scope init --yes.

Getting accurate results

config.json

{
  "srcPaths": ["src", "app", "scripts", "tools"]
}

False positive "unused" verdict? The package may be used in a directory outside the scan scope (scripts/, tools/, etc.). Run dep-scope scan --root to verify before removing anything. When a removal recommendation appears with a narrow scan scope, dep-scope will warn you.

Config file detection

Detected automatically:

Config file	Examples detected
`package.json` scripts	`"lint": "oxlint ."`, `"format": "oxfmt ."`
`vitest.config.*`	`environment: "jsdom"`, `setupFiles: ["@testing-library/jest-dom"]`
`vite.config.*`	`plugins: ["@vitejs/plugin-vue"]`
`next.config.*`	`turbo.rules["*.svg"].loaders: ["@svgr/webpack"]`
`.storybook/main.*`	`addons: ["@storybook/addon-mcp"]`

These packages will appear as INVESTIGATE (or KEEP if well-used) rather than REMOVE.

Opt-out — disable specific detectors in .depscoperc.json:

config.json

{
  "stringReferences": {
    "disable": ["storybook-config"]
  }
}

Available detector IDs: package-json-scripts, vitest-config, vite-config, next-config, storybook-config. Use "disable": "all" to turn off config scanning entirely.

Extend with custom detectors — in depscope.config.ts:

server.ts

import { defineConfig, defineDetector } from "@florianbruniaux/dep-scope";

export default defineConfig({
  stringReferences: {
    detectors: [
      defineDetector({
        id: "my-tool-config",
        label: "my-tool.config.json",
        filePatterns: ["my-tool.config.json"],
        async detect(filePath, ctx) {
          // return StringReference[] for packages found in this file
          return [];
        },
      }),
    ],
  },
});

MCP Server

dep-scope exposes a Model Context Protocol server so AI editors (Claude Code, Cursor, Windsurf) can query your dependencies inline — no CLI, no markdown files, no copy-paste.

Listed on the official MCP Registry: io.github.FlorianBruniaux/dep-scope

Available tools

Tool	Params	What it does
`scan_project`	`projectPath`, `srcPaths`, `threshold`, `includeDev`, `checkDuplicates`, `checkTransitive`, `withKnip`	Full dependency scan with verdicts
`analyze_package`	`packageName`, `projectPath`, `srcPaths`	Symbol-level breakdown of one package
`get_migration_candidates`	`projectPath`	List all RECODE_NATIVE + CONSOLIDATE packages
`generate_migration_prompt`	`packageName`, `projectPath`	Generate a migration prompt inline
`find_duplicates`	`projectPath`	Detect overlapping libraries

Setup

Add the following mcpServers entry to your editor's config. The server runs on demand via npx — no global install required.

Claude Code — ~/.claude.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Cursor — ~/.cursor/mcp.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Windsurf — ~/.codeium/windsurf/mcp_config.json:

config.json

{
  "mcpServers": {
    "dep-scope": {
      "command": "npx",
      "args": ["--package=@florianbruniaux/dep-scope", "-y", "dep-scope-mcp"]
    }
  }
}

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

372

Package downloads in the last 30 days.

Last commit

24d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Dep Scope

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "dep-scope": { "command": "npx", "args": ["-y","@florianbruniaux/dep-scope"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/dep-scope?style=directory)](https://allmcps.com/mcp/dep-scope)

HTML Embed

<a href="https://allmcps.com/mcp/dep-scope"><img src="https://allmcps.com/api/badge/dep-scope?style=directory" alt="Dep Scope on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

10/10 checks healthy over the last 46d

57Quality signal: Good · 57/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools24/30

Adoption & activity9/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @florianbruniaux/dep-scope (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Dep Scope →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Dep Scope

Quick Install

Client Config & Setup

Documentation Overview

dep-scope

When to use dep-scope

Quick Example

How it compares

Installation

Quick Start

Setup: dep-scope init

Getting accurate results

Config file detection

MCP Server

Available tools

Setup

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Dep Scope

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Dep Scope

Quick Install

Client Config & Setup

Documentation Overview

dep-scope

When to use dep-scope

Quick Example

How it compares

Installation

Quick Start

Setup: dep-scope init

Getting accurate results

Config file detection

MCP Server

Available tools

Setup

Related MCP Servers

Adoption & maintenance

Reviews

Frequently Asked Questions about Dep Scope

AllMCPs Directory Badge

Technical Specs & Signals

Supply-chain signal

Moxie Docs MCP

Own this project?

Share & Embed

Explore more

Setup: `dep-scope init`

Setup: `dep-scope init`