Skip to main content
Install the plugin manually, set an API token, or connect an MCP client that has no plugin. The usual path is the setup prompt.

​
Install the plugin

Claude Code and Codex use the same Gcore marketplace repository. Cursor uses the FastEdge plugin repository.
Run these in a shell. /plugin is handled inside Claude Code and fails as a shell command.After installation, run /reload-plugins in Claude Code. The plugin is not active in the session that installed it. To pick up new versions later, run /plugin marketplace update gcore-marketplace in Claude Code.

​
Set an API token

The plugin starts the FastEdge MCP server in Docker when a skill needs it. No separate mcp add command or manual server registration is required. Browser approval from the setup prompt is the usual sign-in. For CI pipelines and machines where a browser cannot be opened, set an API token as GCORE_API_KEY. When GCORE_API_KEY is set, it takes priority over the browser session.
Export the key in the shell that starts Claude Code:
To keep the key in the project instead, add a .env file in the working directory. Claude Code loads that file. Do not commit it.
An env block in .claude/settings.local.json is a further alternative. Keep that file out of Git. A copy of the project can carry the key with it.
Values in the env block are literal strings, not interpolated. A value wrapped as a shell variable is sent as that text, not as the variable’s value. To source the value from the shell instead, export a variable named GCORE_API_KEY or GCORE_API_BASE and omit the env block.
To test against preprod instead of production, set GCORE_API_BASE=https://api.preprod.world alongside GCORE_API_KEY.

​
Docker and local fallback

If Docker is not used, the plugin falls back to local tools (fastedge-build, cargo, asc) and calls api.gcore.com directly. It warns that toolchain versions are no longer managed automatically. MCP clients without the plugin require Docker.

​
Connect other MCP clients

Other MCP clients can connect directly to the FastEdge MCP server. For VS Code, create .vscode/mcp.json in the workspace, with the top-level key servers. Some clients use mcpServers in their own file instead. The FastEdge extension can write this file from the Command Palette.
-e GCORE_API_KEY forwards a key already set in the environment of the process that starts Docker. Do not write the key into this file. Without a key, the server signs in through the Customer Portal. VS Code opened from a desktop shortcut or the Dock may not see a variable exported only in a terminal. Start VS Code from that terminal, or set the variable for the graphical session. When the MCP client starts the server, Docker pulls the image if needed and launches the container. Confirm that fastedge-assistant appears in the client’s MCP server list.