Plugin layers
The plugin contains skills, reference documentation, and blueprint templates. It selects the template and determines which development steps to run. The FastEdge MCP server does the work. It is a Docker container with the Rust, Node, and WebAssembly toolchains plus a Gcore API client. It compiles the binary, uploads it, and calls the FastEdge API, so a local Rust, Node, orwasm32 target is not required for that path.
Command prefixes
The skill names stay the same across clients. Only the prefix changes.
Skills
Square brackets in the Command column are placeholders for required values, not optional arguments.
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 use the MCP server by default and stop with an explanation instead of claiming success if the account is not signed in.
Example requests
All three clients accept the same natural-language requests. The plugin resolves them 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