Import and Export Configuration

If you have already maintained MCP configurations in other AI applications, the import feature is usually the fastest way to migrate to MCP2Skill.

Currently Supported Import Methods

The current version of MCP2Skill supports:

• Import from clipboard
• Import from local file
• Import from Claude Desktop
• Import from Cursor
• Import from Claude Code
• Import from Gemini CLI
• Import from Codex

The import interface automatically displays the application sources that can be detected in the current environment.

When to Use Clipboard or File Import

These two methods are suitable when:

• You already have a snippet of MCP JSON configuration
• You copied configuration content from a colleague or another machine
• Your source is not in the auto-detection list

It is recommended to use the preview feature to confirm the recognition result before actually importing.

General Flow for Importing from an Application

1. Open the MCP page
2. Click Import
3. Select an application source
4. Wait for MCP2Skill to read the configuration and generate a preview
5. Check the services you want to import
6. Run the import

If the source application is not detected, it will usually show directly that no configuration file was detected.

What the Import Preview Does for You

Before anything is actually written, the preview tells you:

• How many services were recognized
• Which services already exist
• Which services are prepared for import by default

This step helps you avoid the confusion caused by duplicate imports and naming conflicts.

Recommended Checks Right After Importing

A completed import does not guarantee everything is usable. It is recommended to do three things immediately:

1. Open the service list and confirm the entries have appeared
2. Check whether key services start correctly
3. Check whether the tool lists load successfully

If you only imported the configuration but the corresponding environment variables, command dependencies, or remote authorization requirements are not met, the services may still be unusable.

What Exports Are Used For

The current version mainly offers two types of export:

Export Raw Configuration

Suitable for:

• Backing up your current MCP service configuration
• Transferring to another machine
• Exchanging configurations with tools that support compatible formats

Export Gateway Endpoint Configuration

Suitable for:

• Exporting all services enabled in MCP2Skill as a configuration that can be plugged in directly
• Quick onboarding for external clients such as Claude Code

This type of export is not the raw upstream connection configuration, but rather a client configuration for "accessing through the MCP2Skill gateway."

Notes on Exporting

• Only services that are currently meaningful are worth exporting; it is recommended to clean up unused services first
• If an API Key is enabled, confirm the security of the target environment before copying it to an external client
• Gateway configurations are suited for external calls, while raw configurations are suited for migration or backup

When to Prefer Import vs. Manual Creation

• You already maintained configurations in another tool: prefer import
• You are only adding a few new services: manual creation is more direct
• The configuration content is incomplete or the source is complicated: manually create a minimal working version first, then expand

Related Chapters

• Managing services after import: see MCP Service Management
• Connecting external clients after export: see Connect External AI Clients
• Import recognition failures: see FAQ and Troubleshooting