Import / Export

Export full design specs (MCP Servers, Agent Cards, and REST APIs including names, descriptions, scenarios, and mock data) and restore them in another instance or share with other users. Import assets from external sources and export your A²D assets for backup or sharing.

Overview

Import/Export is available under Settings > Import / Export. It supports bringing in MCP servers from URLs or OpenAPI specs and exporting your existing assets.

• Export – Download a design spec that includes everything needed to recreate your MCP Servers, Agent Cards, and REST APIs: names, descriptions, tools, resources, prompts, endpoints, mock scenarios, mock content, OpenAPI specs, and (for agent cards) skills and A2A mock scenarios.
• Import – Upload a design spec file (JSON or ZIP) and choose which assets to import. New copies are created in your organization. Imported assets automatically get a default Mocking Service environment.

This is different from the public spec download (e.g. from the Agentic Asset Library), which only includes the API surface (tools/resources/prompts schemas) and not mock data or full design.

Where to find it

In the app sidebar, open Import / Export. The page has two main areas:

1. Export design spec – Select which MCP Servers, Agent Cards, and REST APIs to include, then click Download design spec.
2. Upload design spec – Drag and drop or choose a .json or .zip file, then select which assets to import in the modal.

Export

1. Go to Import / Export in the sidebar.
2. In the Export design spec card, use Select all / Deselect all or tick individual MCP Servers, Agent Cards, and REST APIs.
3. Click Download design spec (enabled only when at least one asset is selected).
4. A single JSON file is downloaded (e.g. design-spec-YYYY-MM-DD.json).

Import from URL

Connect to existing HTTP-Streamable MCP endpoints:

• A manifest (list of asset names and types).
• Full MCP Server data: server config, tools (with mock_scenarios), resources (with mock_content), prompts (with mock_template), and OpenAPI specs.
• Full Agent Card data: card metadata, skills, and a2a_mock_scenarios.
• Full REST API data: API config, endpoints (with method, path, parameters, request body, and mock_scenarios).
• Paste the endpoint URL
• Introspect tools, resources, and prompts
• Import into your organization with one click
• Extend or customize after import

Note: This mirrors the flow in MCP Servers when creating a server via URL import.

1. Go to Import / Export.
2. In the Upload design spec card:
   • Drag and drop a .json or .zip file onto the drop zone, or
   • Click Choose file and select a design spec JSON or a ZIP that contains such a JSON.
3. After the file is parsed, a modal opens listing all assets in the file (MCP Servers, Agent Cards, and REST APIs).
4. For each asset you can:
   • Edit the name in the text field (this is the name used when creating or updating the asset).
   • If an asset with the same name already exists in your organization, you’ll see Override and New copy: choose Override to replace the existing asset, or New copy to create a new one (you can change the name to avoid duplicates).
5. Use Select all / Deselect all or tick the assets you want to import.
6. Click Import selected.

Import from OpenAPI

Convert REST APIs to MCP servers:

• Upload or paste OpenAPI 3.x specifications

• Endpoints map to MCP tools

• Request/response schemas preserved

• Create multiple servers from multiple specs

• JSON – A design spec export file (single JSON with version, manifest, mcpServers, agentCards, and restApis).

• ZIP – An archive containing at least one JSON file that is a valid design spec export. The first valid design spec found inside the ZIP is used.

Export

Export your assets for:

• Backup and version control
• Sharing with other organizations
• Migration between environments

Next Steps

• MCP Servers — Create and manage servers
• Creating Your First MCP Server — Step-by-step guide

Import/Export keeps your assets portable and reusable.