@frontmcp/skills 1.0.0-beta.9 → 1.0.0

package/catalog/frontmcp-deployment/examples/deploy-to-node-dockerfile/secure-nonroot-dockerfile.md

@@ -0,0 +1,89 @@
+---
+name: secure-nonroot-dockerfile
+reference: deploy-to-node-dockerfile
+level: advanced
+description: 'A production Dockerfile with a non-root user, proper ownership, and security hardening.'
+tags: [deployment, dockerfile, docker, security, node, secure]
+features:
+  - 'Creating a dedicated non-root user (`frontmcp`) and switching to it with `USER`'
+  - 'Setting file ownership before switching users so the process can read its own files'
+  - 'Combining the Dockerfile with runtime resource limits (`--memory`, `--cpus`)'
+---
+
+# Secure Non-Root Dockerfile
+
+A production Dockerfile with a non-root user, proper ownership, and security hardening.
+
+## Code
+
+```dockerfile
+# Dockerfile
+
+# ---- Build Stage ----
+FROM node:24-alpine AS builder
+WORKDIR /app
+COPY package.json yarn.lock ./
+RUN yarn install --frozen-lockfile
+COPY . .
+RUN yarn frontmcp build --target node
+
+# ---- Production Stage ----
+FROM node:24-alpine AS production
+WORKDIR /app
+
+# Create non-root user for security
+RUN addgroup -S frontmcp && adduser -S frontmcp -G frontmcp
+
+# Copy only production artifacts
+COPY --from=builder /app/dist ./dist
+COPY --from=builder /app/package.json ./
+COPY --from=builder /app/yarn.lock ./
+
+# Install production dependencies only
+RUN yarn install --frozen-lockfile --production && \
+    yarn cache clean
+
+# Set ownership to non-root user
+RUN chown -R frontmcp:frontmcp /app
+
+USER frontmcp
+
+# Environment defaults
+ENV NODE_ENV=production
+ENV PORT=3000
+
+EXPOSE 3000
+
+HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
+    CMD wget --no-verbose --tries=1 --spider http://localhost:3000/health || exit 1
+
+CMD ["node", "dist/main.js"]
+```
+
+```bash
+# Build
+docker build -t my-frontmcp-server:secure .
+
+# Run with resource limits
+docker run -p 3000:3000 \
+  --memory=512m \
+  --cpus=1.0 \
+  -e NODE_ENV=production \
+  -e REDIS_URL=redis://redis:6379 \
+  my-frontmcp-server:secure
+
+# Verify the process runs as non-root
+docker exec $(docker ps -q -f ancestor=my-frontmcp-server:secure) whoami
+# frontmcp
+```
+
+## What This Demonstrates
+
+- Creating a dedicated non-root user (`frontmcp`) and switching to it with `USER`
+- Setting file ownership before switching users so the process can read its own files
+- Combining the Dockerfile with runtime resource limits (`--memory`, `--cpus`)
+
+## Related
+
+- See `deploy-to-node-dockerfile` for the complete reference Dockerfile
+- See `deploy-to-node` for Docker Compose, PM2, and NGINX deployment patterns

package/catalog/frontmcp-deployment/examples/deploy-to-vercel/vercel-mcp-endpoint-test.md

@@ -0,0 +1,69 @@
+---
+name: vercel-mcp-endpoint-test
+reference: deploy-to-vercel
+level: advanced
+description: 'Verify a Vercel-deployed FrontMCP server by testing health, tool listing, and tool invocation.'
+tags: [deployment, json-rpc, vercel, mcp, endpoint]
+features:
+  - 'Testing the health endpoint and MCP JSON-RPC API of a deployed Vercel function'
+  - 'Using preview deployments to validate changes before promoting to production'
+  - 'Setting `maxDuration` according to your Vercel plan (Hobby: 10s, Pro: 60s, Enterprise: 900s)'
+---
+
+# Testing a Vercel MCP Endpoint
+
+Verify a Vercel-deployed FrontMCP server by testing health, tool listing, and tool invocation.
+
+## Code
+
+```bash
+# Health check
+curl https://your-project.vercel.app/health
+# {"status":"ok"}
+
+# List tools via JSON-RPC
+curl -X POST https://your-project.vercel.app/mcp \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
+
+# Call a tool via JSON-RPC
+curl -X POST https://your-project.vercel.app/mcp \
+  -H "Content-Type: application/json" \
+  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"greet","arguments":{"name":"World"}},"id":2}'
+```
+
+```bash
+# Preview deployment for PR testing
+vercel
+# Creates a unique preview URL: https://my-project-abc123.vercel.app
+
+# Test the preview before promoting to production
+curl https://my-project-abc123.vercel.app/health
+
+# Promote to production
+vercel --prod
+```
+
+```json
+// vercel.json - with maxDuration matching your plan
+{
+  "rewrites": [{ "source": "/(.*)", "destination": "/api/frontmcp" }],
+  "functions": {
+    "api/frontmcp.ts": {
+      "memory": 1024,
+      "maxDuration": 10
+    }
+  },
+  "regions": ["iad1"]
+}
+```
+
+## What This Demonstrates
+
+- Testing the health endpoint and MCP JSON-RPC API of a deployed Vercel function
+- Using preview deployments to validate changes before promoting to production
+- Setting `maxDuration` according to your Vercel plan (Hobby: 10s, Pro: 60s, Enterprise: 900s)
+
+## Related
+
+- See `deploy-to-vercel` for the full deployment, KV storage, and cold start optimization guide

package/catalog/frontmcp-deployment/examples/deploy-to-vercel/vercel-with-kv.md

@@ -0,0 +1,82 @@
+---
+name: vercel-with-kv
+reference: deploy-to-vercel
+level: basic
+description: 'Deploy a FrontMCP server to Vercel serverless functions with Vercel KV for session persistence.'
+tags: [deployment, vercel-kv, vercel, session, performance, serverless]
+features:
+  - "Configuring `{ provider: 'vercel-kv' }` for automatic Vercel KV session storage"
+  - 'The `vercel.json` catch-all rewrite that routes all requests to the single FrontMCP handler'
+  - 'Setting function memory to 1024 MB for faster cold starts'
+---
+
+# Deploy to Vercel with KV Storage
+
+Deploy a FrontMCP server to Vercel serverless functions with Vercel KV for session persistence.
+
+## Code
+
+```typescript
+// src/server.ts
+import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
+import { z } from 'zod';
+
+@Tool({
+  name: 'greet',
+  description: 'Greet a user',
+  inputSchema: { name: z.string() },
+})
+class GreetTool extends ToolContext<{ name: string }> {
+  async execute(input: { name: string }) {
+    return { content: [{ type: 'text' as const, text: `Hello, ${input.name}!` }] };
+  }
+}
+
+@App({ name: 'MyApp', tools: [GreetTool] })
+class MyApp {}
+
+@FrontMcp({
+  info: { name: 'my-server', version: '1.0.0' },
+  apps: [MyApp],
+  redis: { provider: 'vercel-kv' },
+})
+class MyServer {}
+```
+
+```json
+// vercel.json
+{
+  "rewrites": [{ "source": "/(.*)", "destination": "/api/frontmcp" }],
+  "functions": {
+    "api/frontmcp.ts": {
+      "memory": 1024,
+      "maxDuration": 60
+    }
+  },
+  "regions": ["iad1"]
+}
+```
+
+```bash
+# Build for Vercel
+frontmcp build --target vercel
+
+# Preview deployment
+vercel
+
+# Production deployment
+vercel --prod
+
+# Verify
+curl https://your-project.vercel.app/health
+```
+
+## What This Demonstrates
+
+- Configuring `{ provider: 'vercel-kv' }` for automatic Vercel KV session storage
+- The `vercel.json` catch-all rewrite that routes all requests to the single FrontMCP handler
+- Setting function memory to 1024 MB for faster cold starts
+
+## Related
+
+- See `deploy-to-vercel` for KV provisioning, environment variables, and cold start optimization

package/catalog/frontmcp-deployment/examples/deploy-to-vercel/vercel-with-skills-cache.md

@@ -0,0 +1,90 @@
+---
+name: vercel-with-skills-cache
+reference: deploy-to-vercel
+level: intermediate
+description: 'Deploy a FrontMCP server to Vercel with skills enabled and KV-backed skill caching.'
+tags: [deployment, vercel-kv, vercel, cache, security, skills]
+features:
+  - 'Enabling skills cache backed by Vercel KV with a 60-second TTL'
+  - 'Setting environment variables via `vercel env add` instead of hardcoding in source'
+  - 'Adding security headers (`X-Content-Type-Options`, `X-Frame-Options`) in `vercel.json`'
+---
+
+# Vercel Deployment with Skills Cache
+
+Deploy a FrontMCP server to Vercel with skills enabled and KV-backed skill caching.
+
+## Code
+
+```typescript
+// src/server.ts
+import { FrontMcp, App } from '@frontmcp/sdk';
+
+@App({ name: 'MyApp' })
+class MyApp {}
+
+@FrontMcp({
+  info: { name: 'my-server', version: '1.0.0' },
+  apps: [MyApp],
+  redis: { provider: 'vercel-kv' },
+  skillsConfig: {
+    enabled: true,
+    cache: {
+      enabled: true,
+      redis: { provider: 'vercel-kv' },
+      ttlMs: 60000,
+    },
+  },
+})
+class MyServer {}
+```
+
+```bash
+# Set environment variables via Vercel CLI
+vercel env add KV_REST_API_URL "https://your-kv-store.kv.vercel-storage.com"
+vercel env add KV_REST_API_TOKEN "your-token"
+vercel env add NODE_ENV production
+vercel env add LOG_LEVEL info
+```
+
+```json
+// vercel.json
+{
+  "rewrites": [{ "source": "/(.*)", "destination": "/api/frontmcp" }],
+  "functions": {
+    "api/frontmcp.ts": {
+      "memory": 1024,
+      "maxDuration": 60
+    }
+  },
+  "regions": ["iad1"],
+  "headers": [
+    {
+      "source": "/(.*)",
+      "headers": [
+        { "key": "X-Content-Type-Options", "value": "nosniff" },
+        { "key": "X-Frame-Options", "value": "DENY" }
+      ]
+    }
+  ]
+}
+```
+
+```bash
+# Deploy to production
+frontmcp build --target vercel
+vercel --prod
+
+# Add a custom domain
+vercel domains add mcp.example.com
+```
+
+## What This Demonstrates
+
+- Enabling skills cache backed by Vercel KV with a 60-second TTL
+- Setting environment variables via `vercel env add` instead of hardcoding in source
+- Adding security headers (`X-Content-Type-Options`, `X-Frame-Options`) in `vercel.json`
+
+## Related
+
+- See `deploy-to-vercel` for the full deployment guide including cold start notes and execution limits

package/catalog/frontmcp-deployment/examples/deploy-to-vercel-config/minimal-vercel-config.md

@@ -0,0 +1,49 @@
+---
+name: minimal-vercel-config
+reference: deploy-to-vercel-config
+level: basic
+description: 'The minimum `vercel.json` needed to deploy a FrontMCP server to Vercel.'
+tags: [deployment, vercel, serverless, config, minimal]
+features:
+  - 'The catch-all rewrite (`/(.*) -> /api/frontmcp`) routes all requests to the single FrontMCP handler'
+  - 'Setting `buildCommand` and `outputDirectory` so Vercel uses the FrontMCP build pipeline'
+  - 'Configuring function memory (512 MB) and max duration (30s) for the serverless function'
+---
+
+# Minimal vercel.json Configuration
+
+The minimum `vercel.json` needed to deploy a FrontMCP server to Vercel.
+
+## Code
+
+```json
+// vercel.json
+{
+  "$schema": "https://openapi.vercel.sh/vercel.json",
+  "buildCommand": "frontmcp build --target vercel",
+  "outputDirectory": "dist",
+  "rewrites": [
+    {
+      "source": "/(.*)",
+      "destination": "/api/frontmcp"
+    }
+  ],
+  "functions": {
+    "api/frontmcp.js": {
+      "memory": 512,
+      "maxDuration": 30
+    }
+  },
+  "regions": ["iad1"]
+}
+```
+
+## What This Demonstrates
+
+- The catch-all rewrite (`/(.*) -> /api/frontmcp`) routes all requests to the single FrontMCP handler
+- Setting `buildCommand` and `outputDirectory` so Vercel uses the FrontMCP build pipeline
+- Configuring function memory (512 MB) and max duration (30s) for the serverless function
+
+## Related
+
+- See `deploy-to-vercel-config` for the full reference configuration with security headers

package/catalog/frontmcp-deployment/examples/deploy-to-vercel-config/vercel-config-with-security-headers.md

@@ -0,0 +1,92 @@
+---
+name: vercel-config-with-security-headers
+reference: deploy-to-vercel-config
+level: intermediate
+description: 'A complete `vercel.json` with per-route security headers for health, MCP, and all other endpoints.'
+tags: [deployment, vercel, cache, security, config, headers]
+features:
+  - 'Per-route header configuration: `/health` and `/mcp` get `Cache-Control: no-store` to prevent caching'
+  - 'Global security headers (`X-Frame-Options`, `X-Content-Type-Options`, `Referrer-Policy`) applied to all routes'
+  - 'Setting `framework: null` to tell Vercel this is not a framework project'
+---
+
+# vercel.json with Security Headers
+
+A complete `vercel.json` with per-route security headers for health, MCP, and all other endpoints.
+
+## Code
+
+```json
+// vercel.json
+{
+  "$schema": "https://openapi.vercel.sh/vercel.json",
+  "framework": null,
+  "buildCommand": "frontmcp build --target vercel",
+  "outputDirectory": "dist",
+  "rewrites": [
+    {
+      "source": "/(.*)",
+      "destination": "/api/frontmcp"
+    }
+  ],
+  "functions": {
+    "api/frontmcp.js": {
+      "memory": 512,
+      "maxDuration": 30
+    }
+  },
+  "regions": ["iad1"],
+  "headers": [
+    {
+      "source": "/health",
+      "headers": [
+        {
+          "key": "Cache-Control",
+          "value": "no-store"
+        }
+      ]
+    },
+    {
+      "source": "/mcp",
+      "headers": [
+        {
+          "key": "Cache-Control",
+          "value": "no-store"
+        },
+        {
+          "key": "X-Content-Type-Options",
+          "value": "nosniff"
+        }
+      ]
+    },
+    {
+      "source": "/(.*)",
+      "headers": [
+        {
+          "key": "X-Frame-Options",
+          "value": "DENY"
+        },
+        {
+          "key": "X-Content-Type-Options",
+          "value": "nosniff"
+        },
+        {
+          "key": "Referrer-Policy",
+          "value": "strict-origin-when-cross-origin"
+        }
+      ]
+    }
+  ]
+}
+```
+
+## What This Demonstrates
+
+- Per-route header configuration: `/health` and `/mcp` get `Cache-Control: no-store` to prevent caching
+- Global security headers (`X-Frame-Options`, `X-Content-Type-Options`, `Referrer-Policy`) applied to all routes
+- Setting `framework: null` to tell Vercel this is not a framework project
+
+## Related
+
+- See `deploy-to-vercel-config` for the full reference configuration
+- See `deploy-to-vercel` for the complete deployment guide

package/catalog/frontmcp-deployment/references/build-for-browser.md

@@ -1,3 +1,8 @@
+---
+name: build-for-browser
+description: Build a FrontMCP server or client for browser environments and frontend frameworks
+---
+
 # Building for Browser
 
 Build your FrontMCP server or client for browser environments.
@@ -132,6 +137,16 @@ ls dist/browser/
 | Bundle too large            | All server-side code included             | Use `--target browser` and a dedicated client entry file         |
 | `@frontmcp/utils` fs throws | File system ops called in browser         | Remove fs calls; use API endpoints or in-memory alternatives     |
 
+## Examples
+
+| Example                                                                                               | Level        | Description                                                                                           |
+| ----------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------- |
+| [`browser-build-with-custom-entry`](../examples/build-for-browser/browser-build-with-custom-entry.md) | Intermediate | Build a browser bundle using a dedicated client entry file that avoids Node.js-only imports.          |
+| [`browser-crypto-and-storage`](../examples/build-for-browser/browser-crypto-and-storage.md)           | Advanced     | Use `@frontmcp/utils` crypto functions (WebCrypto API) and in-memory storage in browser environments. |
+| [`react-provider-setup`](../examples/build-for-browser/react-provider-setup.md)                       | Basic        | Connect a React application to a remote FrontMCP server using `@frontmcp/react`.                      |
+
+> See all examples in [`examples/build-for-browser/`](../examples/build-for-browser/)
+
 ## Reference
 
 - **Docs:** <https://docs.agentfront.dev/frontmcp/deployment/browser-compatibility>

package/catalog/frontmcp-deployment/references/build-for-cli.md

@@ -1,3 +1,8 @@
+---
+name: build-for-cli
+description: Build a FrontMCP server as a standalone CLI binary using Node.js SEA or bundled JS
+---
+
 # Building a CLI Binary
 
 Build your FrontMCP server as a distributable CLI binary using Node.js Single Executable Applications (SEA) or as a bundled JS file.
@@ -52,7 +57,7 @@ frontmcp build --target cli --js               # JS bundle only (no SEA)
 
 ## Requirements
 
-- **Node.js 22+** required for SEA support
+- **Node.js 24+** required for SEA support
 - The entry file must export or instantiate a `@FrontMcp` decorated class
 - SEA binaries are platform-specific (build on macOS for macOS, Linux for Linux)
 
@@ -92,11 +97,59 @@ frontmcp build --target cli
 node dist/my-server.cjs.js
 ```
 
+## Unix Socket Daemon Mode
+
+Run your MCP server as a local daemon accessible via Unix socket:
+
+```bash
+# Start daemon in foreground
+frontmcp socket ./src/main.ts -s ~/.frontmcp/sockets/my-app.sock
+
+# Start daemon in background
+frontmcp socket ./src/main.ts -b --db ~/.my-tool/data.db
+
+# Default socket path: ~/.frontmcp/sockets/{app-name}.sock
+```
+
+The daemon accepts JSON-RPC requests over HTTP via the Unix socket, making it ideal for local MCP clients (Claude Code, IDE extensions) that need persistent tool access without a TCP port.
+
+## Process Management
+
+Manage long-running MCP server processes with built-in supervisor commands:
+
+```bash
+# Start a named server (auto-restarts on crash)
+frontmcp start my-server -e ./src/main.ts --max-restarts 5
+
+# Monitor
+frontmcp status my-server    # Detailed status for one server
+frontmcp status              # Table of all managed servers
+frontmcp list                # List all managed processes
+frontmcp logs my-server -F   # Tail logs (follow mode)
+
+# Control
+frontmcp restart my-server
+frontmcp stop my-server      # Graceful shutdown (SIGTERM)
+frontmcp stop my-server -f   # Force kill (SIGKILL)
+```
+
+## System Service Installation
+
+Install your MCP server as a system service for automatic startup:
+
+```bash
+# Install as systemd service (Linux) or launchd service (macOS)
+frontmcp service install my-server
+
+# Uninstall service
+frontmcp service uninstall my-server
+```
+
 ## Common Patterns
 
 | Pattern               | Correct                                             | Incorrect                        | Why                                                         |
 | --------------------- | --------------------------------------------------- | -------------------------------- | ----------------------------------------------------------- |
-| Node.js version       | Node.js 22+ for SEA builds                          | Node.js 18 or 20                 | SEA support requires Node.js 22+                            |
+| Node.js version       | Node.js 24+ for SEA builds                          | Node.js 18 or 20                 | SEA support requires Node.js 24+                            |
 | Entry file            | Export or instantiate a `@FrontMcp` decorated class | Export a plain function          | The build expects a FrontMcp entry point                    |
 | Transport for CLI     | `socketPath` or stdin/stdout                        | TCP port binding                 | CLI tools run locally; ports may conflict                   |
 | Cross-platform binary | Build on each target OS separately                  | Build on macOS and ship to Linux | SEA binaries are platform-specific                          |
@@ -126,12 +179,21 @@ node dist/my-server.cjs.js
 
 | Problem                      | Cause                                       | Solution                                                    |
 | ---------------------------- | ------------------------------------------- | ----------------------------------------------------------- |
-| SEA build fails              | Node.js version below 22                    | Upgrade to Node.js 22+                                      |
+| SEA build fails              | Node.js version below 24                    | Upgrade to Node.js 24+                                      |
 | Binary crashes on startup    | Missing `@FrontMcp` decorated entry         | Ensure entry file exports or instantiates a decorated class |
 | Binary too large             | All dependencies bundled including dev deps | Review dependencies and remove unused packages from bundle  |
 | Permission denied on binary  | Missing execute permission                  | Run `chmod +x dist/my-server`                               |
 | Binary fails on different OS | SEA binaries are platform-specific          | Build on the target OS or use CI matrix builds              |
 
+## Examples
+
+| Example                                                                 | Level        | Description                                                                                                  |
+| ----------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------ |
+| [`cli-binary-build`](../examples/build-for-cli/cli-binary-build.md)     | Basic        | Build a FrontMCP server as a standalone binary using Node.js Single Executable Applications (SEA).           |
+| [`unix-socket-daemon`](../examples/build-for-cli/unix-socket-daemon.md) | Intermediate | Run a FrontMCP server as a local daemon accessible via Unix socket for IDE extensions and local MCP clients. |
+
+> See all examples in [`examples/build-for-cli/`](../examples/build-for-cli/)
+
 ## Reference
 
 - **Docs:** <https://docs.agentfront.dev/frontmcp/deployment/production-build>

package/catalog/frontmcp-deployment/references/build-for-sdk.md

@@ -1,3 +1,8 @@
+---
+name: build-for-sdk
+description: Build a FrontMCP server as an embeddable library with create() and connect() APIs
+---
+
 # Building as an SDK Library
 
 Build your FrontMCP server as an embeddable library that runs without an HTTP server. Use `create()` for flat-config setup or `connect()` for platform-specific tool formatting (OpenAI, Claude, LangChain, Vercel AI).
@@ -253,6 +258,16 @@ node -e "const { create } = require('./dist/my-sdk.cjs.js'); ..."
 | `connectOpenAI()` format wrong  | Using raw `listTools()` instead of platform client | Use `connectOpenAI()` which formats tools for OpenAI automatically  |
 | Bundle includes `@frontmcp/*`   | Build config missing externals                     | Verify `--target sdk` is set; it marks `@frontmcp/*` as external    |
 
+## Examples
+
+| Example                                                                         | Level        | Description                                                                                                |
+| ------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------- |
+| [`connect-openai`](../examples/build-for-sdk/connect-openai.md)                 | Intermediate | Use `connectOpenAI()` to get tools formatted for OpenAI's function-calling API.                            |
+| [`create-flat-config`](../examples/build-for-sdk/create-flat-config.md)         | Basic        | Spin up an in-memory FrontMCP server from a flat config object using `create()`.                           |
+| [`multi-platform-connect`](../examples/build-for-sdk/multi-platform-connect.md) | Advanced     | Connect the same FrontMCP server to multiple LLM platforms using platform-specific `connect*()` functions. |
+
+> See all examples in [`examples/build-for-sdk/`](../examples/build-for-sdk/)
+
 ## Reference
 
 - **Docs:** <https://docs.agentfront.dev/frontmcp/deployment/direct-client>

package/catalog/frontmcp-deployment/references/deploy-to-cloudflare.md

@@ -1,3 +1,8 @@
+---
+name: deploy-to-cloudflare
+description: Deploy a FrontMCP server to Cloudflare Workers with KV, D1, and Durable Objects
+---
+
 # Deploy a FrontMCP Server to Cloudflare Workers
 
 This skill guides you through deploying a FrontMCP server to Cloudflare Workers.
@@ -207,6 +212,16 @@ curl -X POST https://frontmcp-worker.your-subdomain.workers.dev/mcp \
 - [ ] SSE streaming works end-to-end (if using SSE transport)
 - [ ] Custom domain resolves correctly (if configured)
 
+## Examples
+
+| Example                                                                                | Level        | Description                                                                                             |
+| -------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------- |
+| [`basic-worker-deploy`](../examples/deploy-to-cloudflare/basic-worker-deploy.md)       | Basic        | Deploy a FrontMCP server to Cloudflare Workers with a minimal configuration.                            |
+| [`worker-custom-domain`](../examples/deploy-to-cloudflare/worker-custom-domain.md)     | Advanced     | Scaffold a FrontMCP project targeting Cloudflare, configure a custom domain, and verify the deployment. |
+| [`worker-with-kv-storage`](../examples/deploy-to-cloudflare/worker-with-kv-storage.md) | Intermediate | Deploy a FrontMCP server to Cloudflare Workers with KV namespace for session and state storage.         |
+
+> See all examples in [`examples/deploy-to-cloudflare/`](../examples/deploy-to-cloudflare/)
+
 ## Reference
 
 - **Docs:** <https://docs.agentfront.dev/frontmcp/deployment/serverless>