Gcore FastEdge Plugins

Build, deploy, and manage serverless WebAssembly applications on Gcore FastEdge from Claude Code, Codex, or Cursor.

FastEdge runs Wasm workloads on 210+ global edge Points of Presence with sub-millisecond cold starts. The plugins in this repository let AI coding agents scaffold projects, deploy apps, and manage edge infrastructure through natural language.

Claude Code Installation

Option 1: Install from GitHub (recommended)

From inside Claude Code, add the Gcore marketplace and install the plugin:

/plugin marketplace add G-Core/gcore-marketplace
/plugin install gcore-fastedge@gcore-marketplace

This persists across sessions. To pick up new versions later, run /plugin marketplace update gcore-marketplace.

Option 2: Install from a local clone (for development or air-gapped use)

Clone the repo first:

git clone https://github.com/G-Core/fastedge-plugin.git

Then either install persistently from the local path:

/plugin marketplace add /path/to/fastedge-plugin
/plugin install gcore-fastedge@gcore-fastedge-marketplace

Or load it for a single session by restarting Claude Code:

claude --plugin-dir /path/to/fastedge-plugin

Codex Installation

Option 1: Install from GitHub (recommended)

codex plugin marketplace add G-Core/gcore-marketplace
codex plugin add gcore-fastedge@gcore-marketplace

Option 2: Install from a local clone (for development or air-gapped use)

Clone the repo (the same repository hosts all runtime targets):

git clone https://github.com/G-Core/fastedge-plugin.git

Add the Codex marketplace and install:

codex plugin marketplace add /path/to/fastedge-plugin
codex plugin add gcore-fastedge@gcore-fastedge-codex-marketplace

See docs/codex-quickstart.md for full Codex setup details.

Cursor Installation

Add this repository as a personal Cursor marketplace:

agent plugin marketplace add https://github.com/G-Core/fastedge-plugin.git

Then run agent, enter /plugin, open the Marketplace tab, and install Gcore FastEdge at user or project scope. Cursor currently performs plugin installation interactively; the CLI command above registers the marketplace.

To refresh or remove the marketplace later:

agent plugin marketplace update gcore-fastedge-marketplace
agent plugin marketplace remove gcore-fastedge-marketplace

See docs/cursor-quickstart.md for credential setup, team marketplace installation, and troubleshooting.

Setup

Prerequisites

The plugins run build, deploy, and management operations through the FastEdge MCP server — a Docker image that ships the toolchains (Rust, Node, wasm targets) and FastEdge API client. Installing a plugin auto-loads its bundled MCP configuration, which launches the server on demand.

You need:

Docker running locally — required to start the MCP server.
Gcore API key — set as GCORE_API_KEY (see below).

Local-only mode (no Docker, no MCP) is available as an explicit opt-out for developers who prefer their own toolchain. See Running without the MCP server below.

Get a Gcore API key

Go to the Gcore Portal
Navigate to Profile → API Keys (or visit portal.gcore.com/api-keys directly)
Click Create API Key, give it a name, and copy the generated key
Set the environment variable:

export GCORE_API_KEY="your-api-key"

Or create a .env file in your project directory:

GCORE_API_KEY=your-api-key

Claude Code automatically loads .env files from the working directory.

Per-project credentials via `.claude/settings.local.json`

If you'd rather not rely on shell exports or .env files, you can pin credentials to a specific project by adding an env block to .claude/settings.local.json in the project root. Claude Code injects these into its own process environment, which the bundled .mcp.json forwards to the MCP server container via Docker's -e passthrough.

.claude/settings.local.json is local-only and not committed, which makes it a safe place for keys.

{
  "env": {
    "GCORE_API_BASE": "https://api.gcore.com",
    "GCORE_API_KEY": "your-api-key"
  }
}

String literals only — no variable interpolation.

Values in this env block are passed through verbatim. Writing "GCORE_API_KEY": "${MY_SECRET}" will send the literal seven-character string ${MY_SECRET} to the MCP server, not the value of MY_SECRET. The same applies to forms like $MY_SECRET or ~.

If you want the value to come from a shell variable rather than be written into the file, the shell variable must already be named GCORE_API_KEY or GCORE_API_BASE — and in that case, omit the env block entirely. The plugin's .mcp.json already passes GCORE_API_KEY and GCORE_API_BASE from the parent shell environment into the container, so an export is sufficient on its own.

The same pattern works in ~/.claude/settings.json if you want a personal default that applies to every project.

Credentials for Codex (host environment, not config)

Codex does not auto-load .env files, and — unlike Claude Code — you cannot pin credentials in .codex/config.toml for a plugin-provided MCP server. The bundled .mcp.json owns how the server launches (its transport), and Codex's config schema only lets user/project config set policy for a plugin server (e.g. enabled, startup_timeout_sec, tool toggles), not transport keys like env. Adding an env block under [plugins."…".mcp_servers.fastedge-assistant] is rejected with Additional properties are not allowed ('env' was unexpected) and silently ignored.

Instead, credentials reach the server through the host environment. The bundled .mcp.json declares env_vars = ["GCORE_API_KEY", "GCORE_API_BASE"], which tells Codex to forward those host variables into the server container. So set them in the shell you launch codex from:

export GCORE_API_KEY="your-api-key"
export GCORE_API_BASE="https://api.gcore.com"   # optional; defaults to https://api.gcore.com
codex

An export in your shell rc gives you a personal default across all projects.

Whatever value is in the shell when you launch codex is the value forwarded to the server. If a stale GCORE_API_KEY is exported in your rc, it will shadow everything else — unset or fix it there.

Credentials for Cursor on macOS

Cursor CLI inherits GCORE_API_KEY from the shell that launches it. The macOS GUI does not normally inherit variables exported from .zshrc, so set the key in the GUI session and restart Cursor:

launchctl setenv GCORE_API_KEY "your-api-key"
launchctl setenv GCORE_API_BASE "https://api.gcore.com"

The Cursor plugin forwards these variables by name to the MCP Docker container; the key is not stored in the plugin or marketplace manifest.

Optional: preprod testing

Set GCORE_API_BASE (via any of the methods above) to override the API host (default: https://api.gcore.com; preprod: https://api.preprod.world). The MCP server appends /fastedge/v1 itself.

Running without the MCP server

If you decline to run Docker, the deploy and manage skills can fall back to your local toolchain (fastedge-build, cargo, asc) and direct REST calls to api.gcore.com. This path is supported but not the default — you'll get a warning each session and you're responsible for keeping toolchains current.

Available Skills

The three plugins share the same skill set but use different invocation styles:

CLI	Prefix	Example
Claude Code	`/gcore-fastedge:`	`/gcore-fastedge:deploy`
Codex	`$gcore-fastedge:`	`$gcore-fastedge:deploy`
Cursor	`/`	`/deploy`

Skill	Claude Code command	Description
Scaffold	`/gcore-fastedge:scaffold [http\|cdn] [name] [description]`	Blueprint-driven project creation from SDK examples (HTTP and CDN)
Deploy	`/gcore-fastedge:deploy [app-name]`	Build, test, and deploy a Wasm app to FastEdge via the MCP server
Manage	`/gcore-fastedge:manage [list\|get\|update\|delete\|secrets\|sync-env] [app-id]`	Inspect apps, manage secrets, and sync `.env` files to deployed apps
Test	`/gcore-fastedge:test`	Generate and run test suites using `@gcoredev/fastedge-test` (CI-friendly)
Debug	`/gcore-fastedge:debug`	Generate scenario fixtures for the visual debugger
Live-test	`/gcore-fastedge:live-test`	Build, deploy, and run scenario fixtures against the live edge
Docs	Auto-invoked	FastEdge platform docs, SDK reference, and best practices

Replace /gcore-fastedge: with $gcore-fastedge: for Codex. In Cursor, invoke the corresponding skill as /scaffold, /deploy, /manage, /test, /debug, or /live-test, or ask the agent naturally.

Example Usage

Ask your coding agent naturally:

"Scaffold a new HTTP app called my-api" — creates a TypeScript project from SDK blueprints
"Deploy this app to FastEdge" — builds the Wasm binary and deploys it to the edge
"List my FastEdge apps" — shows all your deployed apps with status and URLs
"How does the FastEdge KV store work?" — pulls up SDK reference docs inline

Plugin Structure

fastedge-plugin/
├── .claude-plugin/
│   ├── marketplace.json              # Claude Code marketplace descriptor
│   └── plugin.json
├── .cursor-plugin/
│   └── marketplace.json              # Cursor marketplace descriptor
└── plugins/
    ├── gcore-fastedge/               # Claude Code plugin
    │   ├── .claude-plugin/plugin.json
    │   ├── .mcp.json                 # Launches the FastEdge MCP server (Docker)
    │   ├── CLAUDE.md                 # Shared knowledge base (API, SDK, auth, builds)
    │   ├── docs-index.json           # Pre-built docs search index
    │   └── skills/
    │       ├── scaffold/             # Blueprint-driven project scaffolding
    │       │   └── reference/        # http/ + cdn/ blueprints, build/init CLI guides
    │       ├── deploy/               # Build → upload binary → create/update app
    │       ├── manage/               # List/get/update/delete + secrets + sync-env
    │       ├── test/                 # Generate & run tests (@gcoredev/fastedge-test)
    │       ├── debug/                # Generate visual-debugger fixtures
    │       ├── live-test/            # Verify against the deployed edge
    │       └── fastedge-docs/        # Auto-invoked SDK / platform docs
    │           └── reference/        # http/, cdn/, platform/ + SDK references
    ├── gcore-fastedge-codex/         # Codex plugin (shares the same MCP server)
    │   ├── .codex-plugin/
    │   ├── .mcp.json
    │   ├── docs-index.json
    │   └── skills/
    └── gcore-fastedge-cursor/        # Cursor plugin
        ├── .cursor-plugin/plugin.json
        ├── mcp.json
        ├── docs-index.json
        ├── rules/
        └── skills/

Name		Name	Last commit message	Last commit date
Latest commit History 25 Commits
.agents/plugins		.agents/plugins
.claude-plugin		.claude-plugin
.claude/commands		.claude/commands
.cursor-plugin		.cursor-plugin
.github		.github
agent-intent-skills		agent-intent-skills
context		context
docs		docs
plugins		plugins
scripts		scripts
.gitignore		.gitignore
AGENTS.md		AGENTS.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.md		README.md
sources.json		sources.json

Navigation Menu

Uh oh!

Repository files navigation

Gcore FastEdge Plugins

Claude Code Installation

Codex Installation

Cursor Installation

Setup

Prerequisites

Get a Gcore API key

Per-project credentials via `.claude/settings.local.json`

Credentials for Codex (host environment, not config)

Credentials for Cursor on macOS

Optional: preprod testing

Running without the MCP server

Available Skills

Example Usage

Plugin Structure

Links

About

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Folders and files

Latest commit

History

Repository files navigation

Gcore FastEdge Plugins

Claude Code Installation

Codex Installation

Cursor Installation

Setup

Prerequisites

Get a Gcore API key

Per-project credentials via .claude/settings.local.json

Credentials for Codex (host environment, not config)

Credentials for Cursor on macOS

Optional: preprod testing

Running without the MCP server

Available Skills

Example Usage

Plugin Structure

Links

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Per-project credentials via `.claude/settings.local.json`