Skip to main content
The gcore-fastedge plugin adds FastEdge-specific skills to Claude Code, Codex, and Cursor. A request like “scaffold a new HTTP app called my-api” or “deploy this app to FastEdge” scaffolds the project, builds the Wasm binary, and calls the FastEdge API directly, without switching to a terminal or looking up SDK syntax.
Docker and a FastEdge API token are required to build, deploy, or manage applications through the plugin.

​
Two-layer architecture

The plugin splits work across two layers. The intelligence layer — skills, bundled reference docs, and blueprint templates — lives in the plugin itself and decides what to do: which template fits a request, when to scaffold versus deploy, how to wire test fixtures. The execution layer is the FastEdge MCP server, a Docker container that ships the Rust, Node, and WebAssembly toolchains plus a FastEdge API client. It runs the steps the plugin decides on — compiling a binary, uploading it, calling the FastEdge API — so no local Rust, Node, or wasm32 target installation is required. Declining Docker falls back to a local toolchain (fastedge-build, cargo, asc) and direct REST calls to api.gcore.com instead, with a session warning that toolchain versions are no longer managed automatically.

​
Available skills

All three clients share the same skill set, but the invocation prefix is client-specific: The skill names below stay the same across clients — only the prefix changes:
The Docs skill works from the plugin’s bundled reference docs even without the MCP server configured. Scaffold, Deploy, Manage, Test, Debug, and Live-test all call the MCP server and stop with an explanation instead of claiming success if Docker or the API token is unavailable.

​
Install the plugin

Installing the plugin makes the skills above available. Claude Code and Codex use the same Gcore marketplace repository; Cursor installs from the plugin repository directly:
The installation persists across sessions. Run /plugin marketplace update gcore-marketplace later to pick up new plugin versions.

​
Set up the MCP server

Installing the plugin loads its bundled MCP configuration automatically, which starts the FastEdge MCP server in Docker on demand — no separate mcp add command or manual server registration is needed.
Claude Code auto-loads .env files from the working directory. Create one in the project directory:
To pin credentials to a specific project instead, add an env block to .claude/settings.local.json:
Values in the env block are literal strings, not interpolated — writing "GCORE_API_KEY": "${MY_SECRET}" sends the literal string ${MY_SECRET}, not the value of a shell variable named MY_SECRET. 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.

​
Example prompts

All three clients accept the same natural-language requests, resolved by the plugin’s skills without a fixed command syntax:
  • “Scaffold a new HTTP app called my-api” — creates a TypeScript project from an SDK blueprint
  • “Deploy this app to FastEdge” — builds the Wasm binary and deploys it to the edge
  • “List my FastEdge apps” — shows deployed apps with status and URLs
  • “How does the FastEdge KV store work?” — pulls up SDK reference docs inline

​
Connect other AI clients

Claude Code, Codex, and Cursor are not the only supported clients. The FastEdge MCP server also runs standalone for MCP clients without plugin support, including Claude Desktop and VS Code. Create .vscode/mcp.json in the workspace:
Opening the workspace pulls the Docker image and starts the server automatically — no repository clone required.