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

# Migrating from other tools

Step Code can reuse Claude Code / Codex workflows: import MCP configuration on first launch, use the Claude Code plugin layout, and load existing `CLAUDE.md` instructions. Login credentials must be configured again.

## Migration scope

On first launch, Step Code shows an import screen if it detects Claude Code or Codex MCP configuration. After confirmation, supported servers are written to `[mcp_servers]` in `~/.stepcode/config.toml`.

* Sources include `~/.claude.json` and `~/.codex/config.toml`.
* Source files are read-only: they are not moved, deleted, or overwritten.
* Step Code prompts once for each source, and duplicate content is not imported again.
* Same-name servers with different configurations receive `-claude` / `-codex` suffixes.
* Environment references retain variable names rather than expanding their values into configuration.
* Untranslatable fields generate warnings; review the imported result.

Supported transports are stdio and Streamable HTTP. SSE, WebSocket, and IDE-injected servers are not imported automatically. Configure Claude Code project-level `mcpServers` manually.

## Automatic MCP import

```text theme={"theme":{"light":"light-plus","dark":"dark-plus"}}
step mcp list
step mcp get <server-name>
```

Use `/mcp` to inspect connection status and tool counts. Commands, environment variables, and remote permissions must be valid in the environment running Step Code.

Both tools can coexist. After import, the two configurations are maintained independently and are not synchronized automatically.

See [MCP](https://platform.stepfun.ai/docs/en/step-code/customization/mcp.md) for server management and authentication.

## Using Claude Code plugins

Step Code reads `.claude-plugin/plugin.json`, plus `.mcp.json`, `skills`, `commands`, and `agents` inside the plugin. Marketplace manifests are compatible with `.claude-plugin/marketplace.json`.

After installation, check the Skills and MCP capabilities you need. See [Plugins and packages](https://platform.stepfun.ai/docs/en/step-code/customization/plugins.md).

## Reuse existing Skills

User directories add `~/.claude/skills` and `~/.stepcode/skills`; project directories add `.claude/skills` within the trusted scan scope. Claude directories are discovered automatically and do not need to be repeated in the `skills` array; non-default directories such as `~/.codex/skills` still require explicit configuration.

## Project instruction files

Existing `CLAUDE.md` files can remain in place. Check that commands, tool names, and paths apply to Step Code. See [Project instructions](https://platform.stepfun.ai/docs/en/step-code/customization/project-instructions.md) for setup, discovery, and precedence. Run `/reload` or restart after changes.

## Items excluded from migration

| Content | Action |
| - | - |
| Provider credentials | Run `/login` for Step accounts; configure other providers through [Authentication and models](https://platform.stepfun.ai/docs/en/step-code/configuration/models.md) |
| MCP OAuth authorization | Run `step mcp login <name>` |
| Source tool's project-level MCP configuration | Add it manually as needed |

Do not copy credential files in unknown formats or commit configurations containing keys.

See [Quickstart](https://platform.stepfun.ai/docs/en/step-code/quickstart.md) for installation and login steps.

## Verify the migration

1. Complete a model conversation with the selected account and model.
2. Check imported servers in `/mcp` and verify the tool calls you need.
3. Review instruction and resource paths, and confirm that the original tool configuration remains intact.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.