Clone, mirror, or snapshot the MCP server under Artifact Store.
Capability Catalog
Model-facing normalized capabilities built from imported MCP servers. This is the stable interface that future AI agents should use.
Autopilot MCP Import → Normalized Capability
The intended operator flow is one address only. The Hypervisor acquires the source, analyzes runtime, prepares dependencies, introspects MCP tools, registers raw tools, then maps them into our stable capability catalog.
Detect Node, Python, uv, Docker, stdio, HTTP, package scripts, credentials needs, and missing dependencies.
Run initialize + tools/list and capture the real schema returned by the server.
Record raw tools with quality, protocol, runtime candidate, impact, and invocation evidence.
Map raw upstream tools into stable names like meta.system.run_command.
Paste one MCP server address. The URL is only a source; Meta-MCP localizes, extracts, registers, and normalizes.
The system will infer source type, clone or mirror locally, analyze runtime, prepare an import job, run introspection, register tools, rebuild indexes, and map results into normalized capabilities where possible.
Capability-first Interface
Stable capability IDs, categories, purpose, quality, impact, and preferred backend tools.
How a model should find the right tool
The model should never browse thousands of raw tools directly. It should search normalized capabilities, inspect exact use guidance, then invoke one stable capability ID.
meta.system.run_commandmeta.notes.searchmeta.math.*describe_capabilitySelected Capability / AI Usage Guidance
AI Model Tool Selection Contract
This is the intended flow for future models: discover categories first, inspect normalized capabilities, then invoke through our stable interface.
Overview
Meta-MCP Hypervisor / Local-first / Maximum Local Ownership
Recent Invocations
Recent Errors
Import MCP Server
Create a manifest, run ingestion, inspect capabilities, and register tools.
Automatic MCP Import Wizard
Paste only the MCP server URL or local path. The dashboard will infer the manifest, create the import job, run the pipeline, show live progress, and surface registered tools or exact failure reasons.
Latest Import Job & Result
Step 1: Source
Step 2: Runtime
Step 3: Actions
Remote endpoint registration is recognized but execution remains controlled by current policy.
Step 4: Progress Timeline
Server Fleet
External MCP Quality
Raw Tool Registry
Diagnostics layer for imported upstream tools. Model-facing usage should prefer normalized capabilities.
Tool Details
Runtime Monitor
Supervised Processes
Runtime Units
Host Runtime
Check host dependencies, prepare local repositories, and retry MCP introspection.
Host Dependencies
Runtime Missing
Ledger
Summary
Recent Invocations
Recent Errors
Graph
Graph Summary
Categories
Hot Tools
Error Tools
Normalized Capabilities
Our own stable capability names mapped from raw imported MCP tools.
Normalized Summary
Capabilities
Selected Capability
Meta-MCP Super Server
Model-facing MCP endpoint over normalized capabilities, not raw upstream tool names.