Connection methods
Legacy SSE transport is not supported. Plugins can also declare MCP servers; see Plugins and packages.
See Migrating from other tools for importing configuration from other tools.
Add an MCP server
- Confirm the local command, arguments, and dependencies, or the remote URL and authentication requirements.
- Add a declaration under
[mcp_servers.<name>]in~/.stepcode/config.toml. See Configuration below for fields, and preserve other server declarations. - Complete authentication, restart Step Code, and check the connection with
/mcp.
Authentication
Read Bearer tokens from the environment running Step Code:~/.stepcode/.credentials.json with 0600 permissions. Model-platform login and MCP authorization use separate credentials.
Viewing servers interactively
Use/mcp for server status and loaded tool counts. States include connecting, connected, and failed. Servers with enabled = false do not appear in the list.
If connection fails, check the command, environment variables, endpoint reachability, and authorization.
Then request a low-risk tool call and inspect its result. Connection status checks the server connection; a tool result checks the capability you intend to use.
Tool names and filtering
Names use<server>__<tool>, with invalid characters converted to underscores. enabled_tools and disabled_tools filter tools before registration. When an allowlist is set, other tools are unavailable to the model.
Configuration
Declare servers under[mcp_servers.<name>] in global ~/.stepcode/config.toml. Project-level MCP servers are overlaid from installed plugins’ mcpServers manifests.
See Configuration files for global configuration details.
Command-line management
--url and a local command are mutually exclusive. --bearer-token-env-var is HTTP-only. --env sets stdio subprocess variables, not HTTP headers.

