Reference
AI assistants (MCP)
Let Claude Code, Gemini CLI, Codex and other MCP clients use BlazeSCP.
BlazeSCP runs a small MCP server on your computer, so AI assistants can work with it for you: “add my staging server”, “what’s in /var/www on prod?”, “are my uploads done?”.
What assistants can do
| Tool | What it does |
|---|---|
list_servers, get_server, list_groups |
Read your saved servers, and whether each is connected |
create_server, update_server, delete_server |
Add, edit and remove servers |
list_connections, list_directory |
Browse servers that are connected in BlazeSCP |
list_transfers |
See the transfer queue and its progress |
Assistants can also read the server list as resources: blazescp://servers and blazescp://servers/{id}.
Passwords are write-only: an assistant can set one for a server you ask it to add (it goes straight to your keychain), but can never read one back. Browsing only works on servers you’ve connected to in BlazeSCP.
Turning it on
The server is on by default. In Settings → MCP server:
- Let AI assistants use BlazeSCP turns it on or off.
- Allow changes: when it’s off, assistants can look but not add, edit or remove servers.
- New token: clients set up by URL stop working until they’re given the new token.
BlazeSCP must be running for assistants to reach it.
Connecting a client
In Settings → MCP server, choose your client under Set up and click Copy command (or Copy config). The copied text already contains the right path to BlazeSCP on your computer. For reference:
| Client | Setup |
|---|---|
| Claude Code | claude mcp add --scope user blazescp -- "<app>" mcp |
| Gemini CLI | gemini mcp add --scope user blazescp "<app>" mcp |
| Codex CLI (OpenAI) | codex mcp add blazescp -- "<app>" mcp |
| Claude Desktop, Cursor, Windsurf, LM Studio and other apps | {"mcpServers": {"blazescp": {"command": "<app>", "args": ["mcp"]}}} |
<app> is BlazeSCP’s executable, for example /Applications/BlazeSCP.app/Contents/MacOS/blazescp on a Mac or C:\Program Files\BlazeSCP\blazescp.exe on Windows. Started this way (blazescp mcp), it opens no window: it relays the client to the running app and finds it by itself, so the config holds no token and keeps working after a new port or token.
Clients that connect by URL use Streamable HTTP at http://127.0.0.1:20020/mcp (the first free port of 20020–20029) with an Authorization: Bearer <token> header. Any client by URL in Settings copies that config, token included: keep it private.
ChatGPT
ChatGPT’s connectors run on OpenAI’s servers and can only reach public internet servers, so they can’t connect to an app on your computer (and BlazeSCP’s MCP server is deliberately not reachable from outside). To use OpenAI models with BlazeSCP, use Codex CLI.
Security
- The server listens only on
127.0.0.1, on your own computer. - Every request needs the access token, which is kept in BlazeSCP’s data folder, readable only by you.
- Requests from web pages (any with a browser
Origin) are refused, so a website you visit can’t reach it. - Anything an assistant does goes through the same code as the app itself: added servers appear in the sidebar right away.