Ai Context Inspector
Inventory, export, and re-import your MCP servers, skills, and agent memories so stacks stay portable across machines and clients.
Overview
AI Context Inspector is an MCP server for the Build phase that discovers, exports, and imports MCP servers, skills, and agent memories.
What is this MCP server?
- 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
- Package version 0.4.9 on npm registry
- Stdio MCP transport via identifier @cocaxcode/ai-context-inspector
Community signal: 1 GitHub stars.
What problem does it solve?
Your agent stack sprawls across hidden config dirs and you cannot tell which MCP servers and skills are active on this machine.
Who is it for?
Solo builders juggling multiple MCP servers and custom skills who 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Agent-tooling is the canonical Build shelf for utilities that shape how your coding agent sees configured capabilities. Context inspection directly supports wiring and maintaining the agent layer—discovering what is installed before you ship or debug configs.
How it compares
Local AI stack inspector MCP, not a runtime monitor for production errors or a skill marketplace.
Common Questions / 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.