
Ai Context Inspector
io.github.cocaxcodePublished by GitHub account cocaxcodev0.4.9Updated Oct 24, 2026
Scan, export, and import your AI ecosystem. Discover MCP servers, skills, and memories.
Overview
A local MCP server that scans a project's AI tool configurations, MCP servers, skills, agents and memories, and exports or imports them across seven AI tools.
- What you can do
- Scan a project directory, optionally including user-level configs, for AI context files, MCP server configs, skills, agents and persistent memories across 19 tools, with optional live introspection of MCP servers to list their tools, resources and prompts. Generate a standalone HTML dashboard or raw JSON report from scan results. Export the whole ecosystem to a portable bundle file, filtering by category and choosing whether secrets are redacted, included, or selected per variable. Import a bundle into a target tool (Claude, Cursor, Windsurf, Copilot, Gemini, Codex, OpenCode), adapting paths and config formats, with dry-run by default.
- When to use it
- Useful when you want an assistant to inventory what AI tooling and configuration a project already contains, compare setups across tools, or migrate MCP servers, rules, skills and agents from one AI tool to another.
- Requirements
- Runs locally as a Node.js process via npx (stdio transport, started with the --mcp flag). No accounts, API keys or environment variables are declared. Network access is only needed to fetch the package and, if introspection is enabled, to reach HTTP/SSE MCP servers.
Installation
In SourceWeft
- Open Ai Context Inspector in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@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
That's it. An HTML dashboard opens with everything your AI tools know about your project.
All CLI flags
MCP Server Setup
Run as an MCP server so your AI tools can inspect their own ecosystem.
Claude Code
Claude Desktop
Add to claude_desktop_config.json:
Cursor / Windsurf / VS Code / Codex CLI
Cursor / Windsurf — add to .cursor/mcp.json or equivalent:
VS Code — add to .vscode/mcp.json:
Codex CLI:
Or add directly to any .mcp.json:
What It Detects
Tip: Pass
--userto 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 fromnpx skills add) - Custom agents in
.claude/agents/with memory detection - Persistent memories — Claude Memory, agent memory, engram, OpenSpec, ATL
Features
Scan
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 flags
Import
Import flags
Supported Import Targets
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.
introspect_mcp
Connect to a specific MCP server and list its tools, resources, and prompts.
*Either command (stdio) or url (http) is required.
generate_report
Generate a standalone HTML dashboard from scan results.
export_ecosystem
Export the complete AI ecosystem to a portable .aci/bundle.json.
import_ecosystem
Import a bundle into a project, adapting configuration to the target tool.
Warning:
import_ecosystemdefaults to dry-run mode (confirm: false). Setconfirm: trueto actually write files.
Architecture
Stack: TypeScript 5 (strict, ESM) / MCP SDK / Zod / tsup / Vitest
Source: README.md at commit 2e12a55
Tools
0Version history
1- v0.4.9LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts