Configure for FastEdge
To work exclusively with FastEdge tools, set theGCORE_TOOLS environment variable to filter the toolset. This reduces tool count and helps clients load faster when managing edge applications.
Available tools
FastEdge tools cover applications, binaries, key-value stores, secrets, templates, and statistics:| Resource | Operations | Description |
|---|---|---|
apps | list, create, get, update, delete | Edge applications |
binaries | list, upload, get, delete | WebAssembly binaries |
kv_stores | list, create, get, delete | Key-value stores |
secrets | list, create, get, delete | Application secrets |
templates | list, get | Application templates |
statistics | get | Usage statistics |
Application management
Asking the assistant to “list all my FastEdge applications” returns each application with its ID, status, public URL, and recent request counts. The assistant presents this information in a readable format, showing which applications are active and their traffic levels over the past 24 hours. Creating applications works through natural language—“create a FastEdge application named api-cache” provisions a new application and returns its generated URL. The application starts in pending status until a WebAssembly binary is deployed.Binary deployment
After creating an application, deploy WebAssembly binaries by asking the assistant to upload from a local path—“upload binary from ./dist/app.wasm to application api-cache” triggers the upload and deployment process. The assistant reports the binary ID, size, and deployment status. Edge deployments typically complete within 30 seconds. To check available binaries before deployment, ask the assistant to list binaries for a specific application. This shows all uploaded versions with their IDs and upload timestamps.Secrets and configuration
Application secrets store sensitive values such as API keys and configuration parameters. Asking “add a secret named API_KEY with value sk-xxx to application api-cache” creates the secret and makes it available as an environment variable within the application code. The assistant confirms creation without echoing the secret value back. To review configured secrets, ask the assistant to list secrets for an application. Secret values are not returned in listings for security reasons—the assistant shows secret names and creation timestamps.Key-value stores
FastEdge applications can use key-value stores for session data, caching, and counters. Creating a store—“create a KV store named session-cache for application auth-middleware”—provisions the store and associates it with the application. The KV API becomes available in the application runtime for read and write operations. To view all stores across applications, ask the assistant to list KV stores. The response shows store names, IDs, and associated applications.Statistics and monitoring
Request statistics show traffic patterns, latency, and error rates. Asking “show statistics for all FastEdge applications over the last 7 days” returns a summary with request counts, average latency, and error percentages per application. This helps identify performance trends and inactive applications that may need attention. For detailed latency analysis, request percentile breakdowns—“show request latency percentiles for edge-router over the last 24 hours” returns p50, p90, p95, and p99 latency values.Templates
FastEdge provides starter templates for common use cases including HTTP handlers, image resizing, JWT validation, and geolocation. Asking “show available FastEdge templates” lists templates with their descriptions and supported languages (Rust or JavaScript). To create an application from a template, specify the template name—“create an application from the auth-jwt template” scaffolds the application with the template code.Multi-step workflows
The assistant handles multi-step workflows in a single conversation. To deploy a rate-limiting edge function, describe the full setup—“create a FastEdge application named rate-limiter, create a KV store for counters, and add secrets RATE_LIMIT=100 and WINDOW_SECONDS=60.” The assistant executes each step in sequence and reports the results. When updating existing applications, deploying a new binary version works the same way as the initial deployment. The assistant uploads the binary and initiates a rolling update. Previous versions remain available for rollback if needed. To find applications across environments, filter by name patterns—“list applications with staging in the name” shows matching applications. This helps manage development, staging, and production deployments through a single conversation.InfoTool names follow the pattern
fastedge.[resource].[operation], such as fastedge.apps.list or fastedge.secrets.create. The MCP Inspector displays all available tools with their parameters and expected inputs.GCORE_TOOLS environment variable.