Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
cocaxcode avatar

Ai Context Inspector

  • 1 repo stars
  • Updated March 29, 2026
  • cocaxcode/ai-context-inspector

AI Context Inspector is an MCP server that discovers, exports, and imports MCP servers, skills, and agent memories.

About

AI Context Inspector is an MCP server that scans, exports, and imports the surrounding AI toolchain—MCP servers, skills, and memories—so developers treating Claude Code or Cursor as production environments can see what is actually on disk. Install it during Build’s agent-tooling subphase when your `.cursor` rules, skill folders, and MCP JSON have grown faster than your documentation. The npm package runs over stdio, fits alongside other dev MCPs, and helps before Ship when you want a manifest of dependencies your agent relies on. It also supports Operate-style hygiene when you rotate laptops or clone a repo: export once, import on the new machine, and diff what changed. It does not replace version control for application code; it governs agent context artifacts. Pair it with disciplined secrets handling—exports may contain paths or memory snippets you should redact before sharing.

  • Scans the local AI ecosystem for MCP servers, skills, and memories
  • Export and import workflows for backup and machine migration
  • Published as @cocaxcode/ai-context-inspector on npm with stdio MCP (v0.4.9)
  • Reduces silent config drift when you run multiple agents or repos

Ai Context Inspector by the numbers

  • Data as of Jul 7, 2026 (Skillselion catalog sync)
terminal
claude mcp add ai-context-inspector -- npx -y @cocaxcode/ai-context-inspector

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars1
Package@cocaxcode/ai-context-inspector
TransportSTDIO
AuthNone
Last updatedMarch 29, 2026
Repositorycocaxcode/ai-context-inspector

What it does

Inventory, export, and re-import your MCP servers, skills, and agent memories so stacks stay portable across machines and clients.

Who is it for?

Best when you're juggling multiple MCP servers and custom skills and need visibility before shipping or migrating dev setups.

Skip if: Pure application developers with no agent/MCP footprint, or teams wanting cloud-wide IAM governance instead of local context tooling.

What you get

After install, you get scannable inventories and portable export/import of your AI ecosystem for safer moves and audits.

  • Discoverable list of local MCP servers, skills, and memories
  • Export bundles for migration or backup
  • Import path to restore AI context on a new workstation

By the numbers

  • Package version 0.4.9 on npm registry
  • Stdio MCP transport via identifier @cocaxcode/ai-context-inspector
README.md

@cocaxcode/ai-context-inspector

One command. Every AI config in your project. Instantly.
CLI + MCP server · 19 tools detected · Export/Import across 7 targets

npm version npm downloads License Node 19 AI tools

Quick Start · MCP Server · What It Detects · Features · Tool Reference · Architecture


The most comprehensive AI ecosystem scanner available. AI Context Inspector discovers every AI configuration file, MCP server, custom skill, agent, and persistent memory in your project — across 19 tools — and gives you the full picture in seconds. Export your entire AI setup and import it into any of 7 supported tools (Claude, Cursor, Windsurf, Copilot, Gemini, Codex, OpenCode) with automatic secret redaction. Zero config. Zero runtime dependencies beyond MCP SDK and Zod. Everything runs locally — your configs and credentials never leave your machine.


Quick Start

npx -y @cocaxcode/ai-context-inspector@latest

That's it. An HTML dashboard opens with everything your AI tools know about your project.

# Scan a specific directory
npx -y @cocaxcode/ai-context-inspector@latest --dir /path/to/project

# Include user-level configs (~/.claude, ~/.gemini, etc.)
npx -y @cocaxcode/ai-context-inspector@latest --user

# Live-connect to each MCP server and list its tools
npx -y @cocaxcode/ai-context-inspector@latest --introspect

# Output raw JSON instead of HTML
npx -y @cocaxcode/ai-context-inspector@latest --json
All CLI flags
Flag Description Default
--dir <path> Directory to scan . (current)
--user Include user-level configs (~/) false
--introspect Connect to MCP servers and list tools false
--timeout <ms> Introspection timeout per server 10000
--json Output JSON instead of HTML false
--mcp Run as MCP server (stdio transport) false

MCP Server Setup

Run as an MCP server so your AI tools can inspect their own ecosystem.

Claude Code

claude mcp add --scope user ai-context-inspector -- npx -y @cocaxcode/ai-context-inspector@latest --mcp

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "ai-context-inspector": {
      "command": "npx",
      "args": ["-y", "@cocaxcode/ai-context-inspector@latest", "--mcp"]
    }
  }
}
Cursor / Windsurf / VS Code / Codex CLI

Cursor / Windsurf — add to .cursor/mcp.json or equivalent:

{
  "mcpServers": {
    "ai-context-inspector": {
      "command": "npx",
      "args": ["-y", "@cocaxcode/ai-context-inspector@latest", "--mcp"]
    }
  }
}

VS Code — add to .vscode/mcp.json:

{
  "servers": {
    "ai-context-inspector": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cocaxcode/ai-context-inspector@latest", "--mcp"]
    }
  }
}

Codex CLI:

codex mcp add ai-context-inspector -- npx -y @cocaxcode/ai-context-inspector@latest --mcp

Or add directly to any .mcp.json:

{
  "mcpServers": {
    "ai-context-inspector": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@cocaxcode/ai-context-inspector@latest", "--mcp"]
    }
  }
}

What It Detects

Tool Context Files What's Found
Claude Code CLAUDE.md, .claude/, .mcp.json Instructions, MCP config, skills, agents, memory
Cursor .cursorrules, .cursor/rules/, .cursorignore Rules, ignore patterns
Windsurf .windsurfrules, .windsurf/rules/ Codeium/Windsurf rules
GitHub Copilot .github/copilot-instructions.md, .github/agents/ Instructions, custom agents
Gemini CLI GEMINI.md, .gemini/, .geminiignore Config, rules
OpenAI Codex AGENTS.md, AGENT.md, .codex/ Agent instructions
OpenCode OPENCODE.md, .opencode/, opencode.json CLI config
Aider .aider.conf.yml, .aiderignore Config, model settings
Cline .clinerules, .clineignore Rules (file or directory)
Roo Code .roo/rules/, .roorules, .rooignore Rules
Continue.dev .continuerules, .continue/config.yaml Rules, config
Amazon Q .amazonq/rules/ Developer rules
Augment .augment/rules/, .augment-guidelines Code rules
Replit .replit.md Agent instructions
Firebase Studio .idx/airules.md AI rules
VS Code .vscode/mcp.json MCP configuration
Tabnine .tabnine.yaml AI config
Sourcegraph .sourcegraph/ Cody config
Universal CONVENTIONS.md Multi-tool conventions

Tip: Pass --user to also scan user-level configs: ~/.claude/, ~/.gemini/, ~/.codex/, ~/.continue/, ~/.aider.conf.yml, ~/.augment/, ~/.github/agents/, ~/.codeium/, ~/.opencode/, ~/.tabnine/.

Beyond context files, the scanner also detects:

  • MCP servers from .mcp.json, ~/.claude.json, .vscode/mcp.json, Claude Desktop config — with optional live introspection
  • Custom skills in .claude/skills/ (including symlinks from npx skills add)
  • Custom agents in .claude/agents/ with memory detection
  • Persistent memories — Claude Memory, agent memory, engram, OpenSpec, ATL

Features

Scan

npx -y @cocaxcode/ai-context-inspector@latest
npx -y @cocaxcode/ai-context-inspector@latest --user --introspect

Generates a self-contained HTML dashboard with dark/light mode, search, collapsible sections, file previews, and color-coded tool badges. Pass --json for raw output.

Export

# Export your AI ecosystem to .aci/bundle.json
npx -y @cocaxcode/ai-context-inspector@latest export

# Export only MCP and context configs, redact secrets
npx -y @cocaxcode/ai-context-inspector@latest export --only mcp,context --secrets none
Export flags
Flag Description Default
--dir <path> Directory to export .
--output <path> Output directory .aci/
--include-user Include user-level configs false
--only <categories> Filter: mcp,skills,agents,memories,context all
--secrets <mode> none (redact) or all (include) interactive

Import

# Import into a Cursor project
npx -y @cocaxcode/ai-context-inspector@latest import --target cursor

# Auto-detect tool, skip confirmation, overwrite existing
npx -y @cocaxcode/ai-context-inspector@latest import --yes --force
Import flags
Flag Description Default
[file] Path to bundle JSON auto-detect .aci/bundle.json
--dir <path> Target directory .
--target <tool> Target tool (see table) auto-detect
--scope <scope> project or user per-resource
--force Overwrite existing resources false
--yes Skip confirmation prompt false
--only <categories> Filter: mcp,skills,agents,memories,context all
--secrets <mode> none or all interactive

Supported Import Targets

Target MCP Config Context File Rules Dir Skills Agents
claude .mcp.json CLAUDE.md -- .claude/skills/ .claude/agents/
cursor .cursor/mcp.json .cursorrules .cursor/rules/ -- --
windsurf .mcp.json .windsurfrules .windsurf/rules/ -- --
copilot .vscode/mcp.json .github/copilot-instructions.md .github/instructions/ -- .github/agents/
gemini .gemini/settings.json GEMINI.md .gemini/rules/ -- --
codex .mcp.json AGENTS.md .codex/rules/ -- --
opencode opencode.json OPENCODE.md .opencode/rules/ -- --

Note: Secrets handling has three modes: none (redact all — safe for sharing), all (include as-is), or interactive (prompt per variable, CLI default). Environment variables in MCP configs are detected automatically.


MCP Tool Reference

When running as an MCP server (--mcp), five tools are exposed:

scan

Discover the complete AI ecosystem in a project directory.

Parameter Type Required Description
directory string No Path to scan (default: cwd)
include_user boolean No Include user-level configs
introspect boolean No Live-connect to MCP servers
timeout number No Introspection timeout (ms)

introspect_mcp

Connect to a specific MCP server and list its tools, resources, and prompts.

Parameter Type Required Description
command string Yes* Command to launch the server
args string[] No Arguments for the command
env object No Environment variables
url string Yes* URL for HTTP/SSE servers
transport string No stdio (default) or http
timeout number No Connection timeout (ms)

*Either command (stdio) or url (http) is required.

generate_report

Generate a standalone HTML dashboard from scan results.

Parameter Type Required Description
directory string No Path to scan
include_user boolean No Include user-level configs
introspect boolean No Introspect MCP servers
timeout number No Introspection timeout (ms)

export_ecosystem

Export the complete AI ecosystem to a portable .aci/bundle.json.

Parameter Type Required Description
dir string No Directory to scan (default: cwd)
include_user boolean No Include user-level configs
only string[] No Categories: mcp, skills, agents, memories, context
secrets string No "none" (default), "all", or ["VAR1", "VAR2"]

import_ecosystem

Import a bundle into a project, adapting configuration to the target tool.

Parameter Type Required Description
file string No Path to bundle (auto-detects .aci/bundle.json)
dir string No Target directory (default: cwd)
target string No Target tool (auto-detects): claude, cursor, windsurf, copilot, gemini, codex, opencode
scope string No project or user
force boolean No Overwrite existing resources
confirm boolean No Execute import (default: false = dry-run)
only string[] No Categories to import
secrets string No "none", "all", ["VAR1"], or {"VAR1": "value"}

Warning: import_ecosystem defaults to dry-run mode (confirm: false). Set confirm: true to actually write files.


Architecture

src/
├── index.ts              # Entry: CLI vs MCP mode routing
├── cli.ts                # CLI arg parsing + orchestration
├── server.ts             # createServer() MCP factory
├── scanner/              # 6 parallel scanners (Promise.all)
│   ├── catalog.ts        # AI_FILE_CATALOG — 50+ entries, 19 tools
│   ├── context-files.ts  # Scan .md, rules, configs
│   ├── mcp-configs.ts    # Parse .mcp.json, ~/.claude.json, etc.
│   ├── mcp-introspect.ts # Connect to servers, list tools/resources
│   ├── skills.ts         # Skills + symlinks + frontmatter
│   ├── agents.ts         # Agents + memory detection
│   └── memories.ts       # engram, openspec, .atl, claude memory
├── ecosystem/            # Export/import engine
│   ├── export.ts         # Scan → bundle → .aci/bundle.json
│   ├── import.ts         # Load → plan → execute
│   ├── target-map.ts     # Path configs for 7 AI tools
│   ├── detect-target.ts  # Auto-detect tool in project
│   └── secrets.ts        # Env var detection + redaction
├── report/               # HTML dashboard generator
│   ├── generator.ts      # generateHtml(ScanResult) → string
│   ├── sections.ts       # Section renderers
│   ├── styles.ts         # CSS (dark/light)
│   └── scripts.ts        # JS (collapse, search, preview)
└── tools/                # 5 MCP tool handlers
    ├── scan.ts
    ├── introspect.ts
    ├── report.ts
    ├── export.ts
    └── import.ts

Stack: TypeScript 5 (strict, ESM) / MCP SDK / Zod / tsup / Vitest


MIT · Built by cocaxcode

Recommended MCP Servers

How it compares

Local AI stack inspector MCP, not a runtime monitor for production errors or a skill marketplace.

FAQ

Who is AI Context Inspector for?

Agent-heavy developers who maintain MCP servers, skills, and memories locally and need inventory plus backup across machines.

When should I use AI Context Inspector?

Use it while building agent workflows, before shipping a release that depends on specific skills, or when migrating or cloning a dev environment.

How do I add AI Context Inspector to my agent?

Install @cocaxcode/ai-context-inspector from npm, add the stdio MCP entry to your client config, and invoke scan/export tools from the repository README.

Developer Toolsintegrationsdevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.