Ai MCP Server

Scan, export, and import your AI ecosystem. Discover MCP servers, skills, and memories.

Local serverstdioTypeScript

What is the Ai MCP server?

Most developer tooling work still happens through a UI a human drives. Ai MCP server moves it into the conversation instead. Scan, export, and import your AI ecosystem. Discover MCP servers, skills, and memories.

The short version

One command. Every AI config in your project. Instantly.

Getting it running

Installation goes through your MCP client rather than a global install: point it at @cocaxcode/ai-context-inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 8 tools. What each one is for:

  • Scan — Generates a self-contained HTML dashboard with dark/light mode, search, collapsible sections, file previews, and color-coded tool badges. Pass --json
  • Export — The Export tool exposed by this server
  • Import — The Import tool exposed by this server
  • scan — The scan tool exposed by this server
  • introspect_mcp — Connect to a specific MCP server and list its tools, resources, and prompts
  • generate_report — The generate_report tool exposed by this server
  • 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

What it needs from you

Configuration is passed through the environment: VAR1. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ai's toolset — Scan, Export, Import and 5 more — is a fair guide to whether it matches your workflow. It is maintained by cocaxcode; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ai's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
ScanGenerates a self-contained HTML dashboard with dark/light mode, search, collapsible sections, file previews, and color-coded tool badges. Pass --json for raw output.
ExportThe Export tool exposed by this server.
ImportThe Import tool exposed by this server.
scanThe scan tool exposed by this server.
introspect_mcpConnect to a specific MCP server and list its tools, resources, and prompts.
generate_reportThe generate_report tool exposed by this server.
export_ecosystemExport the complete AI ecosystem to a portable .aci/bundle.json.
import_ecosystemImport a bundle into a project, adapting configuration to the target tool.

How to install the Ai MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
VAR1Configuration value read at startup.Optional

Example prompts to try

  • Use Ai to Scan.
  • Use Ai to Export.
  • Use Ai to Import.

Frequently asked questions

It connects Ai to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Scan, Export, Import, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ai directly.