> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mcp-1.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing existing servers

> Bulk-register the remote MCP servers already configured in Claude Code or Codex.

If you already have MCP servers configured in Claude Code (`~/.claude.json`) or Codex (`~/.codex/config.toml`), you can bulk-register the **remote** ones instead of adding them one at a time.

## From the dashboard

On the **Backend Servers** page, click **Import existing servers**. It generates a ready-to-run command with a short-lived token, so you don't need to enter a password.

## From the command line

```bash theme={null}
MCP1_EMAIL=you@example.com MCP1_PASSWORD=... \
  node backend/scripts/import-mcp-servers.mjs --dry-run
```

Run with `--dry-run` first to see what would be imported. Drop the flag to actually create the backend servers. Set `MCP1_API` if the API isn't at `http://localhost:4000/api`.

## What gets imported

<Warning>
  Only `http` and `sse` servers can be imported. **`stdio`/command servers are skipped** — mcp1 is a hosted gateway that dials outbound HTTP and can neither store nor reach a local subprocess. To bring a local `stdio` server in, use the [bridge](/guides/bridge) instead.
</Warning>

Auth headers aren't carried over during import either. A remote server that needs an `Authorization` header imports successfully but won't discover any tools until you connect it (for example, via OAuth) from the dashboard.