@frontmcp/skills 1.0.4 → 1.1.0-beta.1

package/catalog/frontmcp-config/references/configure-deployment-targets.md

@@ -0,0 +1,214 @@
+---
+name: configure-deployment-targets
+description: Configure multi-target builds with frontmcp.config.ts for node, distributed, vercel, lambda, cloudflare, browser, cli, and sdk targets
+---
+
+# Configure Deployment Targets
+
+FrontMCP's configuration file defines one or more deployment targets, each with independent server settings, security headers, and HA configuration. Use `defineConfig()` for full TypeScript autocomplete.
+
+## When to Use This Skill
+
+### Must Use
+
+- Deploying to multiple platforms (e.g., node + vercel + distributed) from the same codebase
+- Configuring per-target server settings (port, CSP, CORS, HA)
+- Setting up security headers for production deployment
+
+### Recommended
+
+- Any project that benefits from typed configuration with IDE autocomplete
+- Multi-environment setups (dev vs staging vs production targets)
+
+### Skip When
+
+- Single-target projects using CLI flags only (`frontmcp build --target node`)
+- You only need to configure auth modes or sessions (see `configure-auth-modes`, `configure-session`)
+
+> **Decision:** Use this skill when you need a configuration file with multi-target or per-target server settings. Skip for simple single-target CLI builds.
+
+## Prerequisites
+
+- `@frontmcp/cli` installed
+- A working FrontMCP server (see `frontmcp-development`)
+
+## Step 1: Create Configuration File
+
+```typescript
+// frontmcp.config.ts
+import { defineConfig } from '@frontmcp/cli';
+
+export default defineConfig({
+  name: 'my-server',
+  version: '1.0.0',
+  deployments: [{ target: 'node' }],
+});
+```
+
+## Step 2: Add Deployment Targets
+
+```typescript
+export default defineConfig({
+  name: 'my-server',
+  deployments: [
+    { target: 'node', server: { http: { port: 3000 } } },
+    {
+      target: 'distributed',
+      ha: { heartbeatIntervalMs: 5000, heartbeatTtlMs: 15000 },
+    },
+    { target: 'vercel' },
+  ],
+});
+```
+
+## Step 3: Configure Server Settings
+
+```typescript
+export default defineConfig({
+  name: 'my-server',
+  deployments: [
+    {
+      target: 'node',
+      server: {
+        http: { port: 3000, cors: { origin: 'https://app.example.com' } },
+        csp: {
+          enabled: true,
+          directives: "default-src 'self'; upgrade-insecure-requests",
+        },
+        headers: {
+          hsts: 'max-age=31536000; includeSubDomains',
+          contentTypeOptions: 'nosniff',
+          frameOptions: 'DENY',
+        },
+      },
+    },
+  ],
+});
+```
+
+## Step 4: Build for Each Target
+
+```bash
+frontmcp build --target node
+frontmcp build --target distributed
+frontmcp build --target vercel
+```
+
+## Configuration Reference
+
+### Top-Level Fields
+
+| Field         | Type   | Required | Description                    |
+| ------------- | ------ | -------- | ------------------------------ |
+| `name`        | string | Yes      | Server name (kebab-case)       |
+| `version`     | string | No       | Server version                 |
+| `entry`       | string | No       | Custom entry file path         |
+| `deployments` | array  | Yes      | One or more deployment targets |
+
+### Available Targets
+
+| Target        | Transport        | Storage               | Use Case                |
+| ------------- | ---------------- | --------------------- | ----------------------- |
+| `node`        | HTTP, SSE, stdio | Redis, SQLite, memory | VPS, Docker, bare metal |
+| `distributed` | HTTP             | Redis (required)      | Multi-pod with HA       |
+| `vercel`      | HTTP             | Vercel KV             | Serverless with Vercel  |
+| `lambda`      | HTTP             | DynamoDB, ElastiCache | AWS serverless          |
+| `cloudflare`  | HTTP             | KV, Durable Objects   | Edge computing          |
+| `browser`     | In-memory        | Memory                | Web browser             |
+| `cli`         | stdio            | SQLite, memory        | Standalone binary       |
+| `sdk`         | Direct           | Configurable          | Library embedding       |
+
+### Server HTTP Options
+
+| Field         | Type             | Default | Description                  |
+| ------------- | ---------------- | ------- | ---------------------------- |
+| `port`        | number           | 3000    | Listen port                  |
+| `socketPath`  | string           | ---     | Unix socket (overrides port) |
+| `entryPath`   | string           | `/`     | Base path                    |
+| `cors.origin` | string           | ---     | CORS allowed origin          |
+| `portRange`   | [number, number] | ---     | Auto-find available port     |
+
+### CSP Options
+
+| Field        | Type    | Default | Description                    |
+| ------------ | ------- | ------- | ------------------------------ |
+| `enabled`    | boolean | false   | Enable CSP headers             |
+| `directives` | string  | ---     | Semicolon-separated directives |
+| `reportUri`  | string  | ---     | Violation report URI           |
+| `reportOnly` | boolean | false   | Report-only mode               |
+
+### Security Headers
+
+| Field                | Default   | Header                      |
+| -------------------- | --------- | --------------------------- |
+| `hsts`               | ---       | `Strict-Transport-Security` |
+| `contentTypeOptions` | `nosniff` | `X-Content-Type-Options`    |
+| `frameOptions`       | `DENY`    | `X-Frame-Options`           |
+
+### HA Configuration (distributed target only)
+
+| Field                   | Type   | Default   | Description                  |
+| ----------------------- | ------ | --------- | ---------------------------- |
+| `heartbeatIntervalMs`   | number | 10000     | Heartbeat write interval     |
+| `heartbeatTtlMs`        | number | 30000     | Heartbeat TTL                |
+| `takeoverGracePeriodMs` | number | 5000      | Grace period before takeover |
+| `redisKeyPrefix`        | string | `mcp:ha:` | Redis key prefix             |
+
+## File Resolution Order
+
+1. `frontmcp.config.ts`
+2. `frontmcp.config.js`
+3. `frontmcp.config.json`
+4. `frontmcp.config.mjs`
+5. `frontmcp.config.cjs`
+6. Fallback: `package.json` (derives name, default node target)
+
+## JSON Schema for IDE Support
+
+For JSON configs, add `$schema` for autocomplete:
+
+```json
+{
+  "$schema": "./node_modules/@frontmcp/cli/frontmcp.schema.json",
+  "name": "my-server",
+  "deployments": [{ "target": "node" }]
+}
+```
+
+## Common Patterns
+
+| Pattern        | Correct                      | Incorrect                    | Why                           |
+| -------------- | ---------------------------- | ---------------------------- | ----------------------------- |
+| Config helper  | `defineConfig({...})`        | Plain object export          | Loses IDE autocomplete        |
+| HA config      | Only on `distributed` target | On `node` or `vercel` target | HA requires Redis + multi-pod |
+| CSP directives | Semicolon-separated string   | Object or array              | Schema expects a string       |
+
+## Verification Checklist
+
+### Configuration
+
+- [ ] `frontmcp.config.ts` exists in project root
+- [ ] `name` is kebab-case with no spaces
+- [ ] At least one deployment target defined
+- [ ] HA config only on `distributed` target
+
+### Runtime
+
+- [ ] `frontmcp build --target <target>` succeeds for each target
+- [ ] Security headers visible in response (`curl -I http://localhost:3000/healthz`)
+- [ ] CSP header present when `csp.enabled: true`
+
+## Examples
+
+| Example                                                                                                | Level        | Description                                                                                                                      |
+| ------------------------------------------------------------------------------------------------------ | ------------ | -------------------------------------------------------------------------------------------------------------------------------- |
+| [`multi-target-with-security`](../examples/configure-deployment-targets/multi-target-with-security.md) | Intermediate | Configure a FrontMCP project with node + distributed targets, CSP headers, and HSTS                                              |
+| [`distributed-ha-config`](../examples/configure-deployment-targets/distributed-ha-config.md)           | Advanced     | Configure a distributed deployment target with HA settings for heartbeat, session takeover, and Redis-backed session persistence |
+| [`json-schema-ide-support`](../examples/configure-deployment-targets/json-schema-ide-support.md)       | Basic        | Use frontmcp.config.json with JSON Schema for VS Code and WebStorm autocomplete                                                  |
+
+> See all examples in [`examples/configure-deployment-targets/`](../examples/configure-deployment-targets/)
+
+## Reference
+
+- [Documentation](https://docs.agentfront.dev/frontmcp/deployment/frontmcp-config)
+- Related skills: `frontmcp-deployment`, `distributed-ha`, `deploy-to-node`, `deploy-to-vercel`

package/catalog/frontmcp-config/references/configure-elicitation.md

@@ -72,8 +72,7 @@ interface ElicitationOptionsInput {
 When elicitation is enabled, tools can request user input via the MCP elicitation protocol:
 
 ```typescript
-import { Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'delete_records',

package/catalog/frontmcp-config/references/configure-security-headers.md

@@ -0,0 +1,198 @@
+---
+name: configure-security-headers
+description: Configure CSP, HSTS, X-Frame-Options, and X-Content-Type-Options via frontmcp.config server settings
+---
+
+# Configure Security Headers
+
+Set Content Security Policy (CSP), HSTS, and other security headers on every HTTP response. Configure them in `frontmcp.config` per deployment target — the build adapter injects them as environment variables that the built-in middleware reads at runtime.
+
+## When to Use This Skill
+
+### Must Use
+
+- Deploying to production and need CSP headers to prevent XSS
+- Required to send HSTS headers for HTTPS enforcement
+- Compliance requires specific X-Frame-Options or X-Content-Type-Options values
+
+### Recommended
+
+- Any production deployment behind HTTPS
+- Testing CSP policies in report-only mode before enforcement
+
+### Skip When
+
+- Local development only (security headers are unnecessary on localhost)
+- Browser target (no HTTP server to set headers on)
+- You manage headers via NGINX/CDN instead of the application
+
+> **Decision:** Use this skill when the FrontMCP server must emit its own security headers. Skip if a reverse proxy handles them.
+
+## Prerequisites
+
+- `@frontmcp/cli` installed
+- A `frontmcp.config.ts` or `.json` file (see `configure-deployment-targets`)
+
+## Step 1: Add CSP to Your Config
+
+CSP directives are specified as a record (object) mapping directive names to values:
+
+```typescript
+// frontmcp.config.ts
+import { defineConfig } from '@frontmcp/cli';
+
+export default defineConfig({
+  name: 'my-server',
+  deployments: [
+    {
+      target: 'node',
+      server: {
+        csp: {
+          enabled: true,
+          directives: {
+            'default-src': "'self'",
+            'script-src': "'self' https://cdn.example.com",
+            'style-src': "'self' 'unsafe-inline'",
+            'img-src': '* data:',
+            'upgrade-insecure-requests': '', // value-less directive
+          },
+        },
+      },
+    },
+  ],
+});
+```
+
+## Step 2: Add Security Headers
+
+```typescript
+server: {
+  headers: {
+    hsts: 'max-age=31536000; includeSubDomains; preload',
+    contentTypeOptions: 'nosniff',  // default, can omit
+    frameOptions: 'DENY',           // default, can omit
+  },
+}
+```
+
+## Step 3: Build and Verify
+
+```bash
+frontmcp build --target node
+node dist/node/main.js
+
+# Verify headers
+curl -I http://localhost:3000/healthz
+# Content-Security-Policy: default-src 'self'; script-src 'self' https://cdn.example.com; ...
+# Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
+# X-Content-Type-Options: nosniff
+# X-Frame-Options: DENY
+```
+
+## Configuration Reference
+
+### CSP Options (`server.csp`)
+
+| Field        | Type                                 | Default | Description                               |
+| ------------ | ------------------------------------ | ------- | ----------------------------------------- |
+| `enabled`    | boolean                              | false   | Enable CSP headers                        |
+| `directives` | `Record<string, string \| string[]>` | ---     | Directive-to-value map                    |
+| `reportUri`  | string                               | ---     | URI for violation reports                 |
+| `reportOnly` | boolean                              | false   | Use `Content-Security-Policy-Report-Only` |
+
+### Security Headers (`server.headers`)
+
+| Field                | Type                    | Default   | Header                      |
+| -------------------- | ----------------------- | --------- | --------------------------- |
+| `hsts`               | `string \| false`       | ---       | `Strict-Transport-Security` |
+| `contentTypeOptions` | `string \| false`       | `nosniff` | `X-Content-Type-Options`    |
+| `frameOptions`       | `string \| false`       | `DENY`    | `X-Frame-Options`           |
+| `custom`             | `Record<string,string>` | ---       | Any custom headers          |
+
+Set any of the first three fields to `false` to explicitly disable that header.
+
+### Value-Less CSP Directives
+
+Directives like `upgrade-insecure-requests` and `block-all-mixed-content` have no value. Set them with an empty string:
+
+```typescript
+directives: {
+  'upgrade-insecure-requests': '',
+  'block-all-mixed-content': '',
+}
+```
+
+### Report-Only Mode
+
+Test CSP rules without blocking content:
+
+```typescript
+csp: {
+  enabled: true,
+  directives: { 'default-src': "'self'" },
+  reportUri: 'https://report.example.com/csp',
+  reportOnly: true,  // violations reported, not blocked
+}
+```
+
+### Environment Variables
+
+The build adapter converts config to these env vars (can also be overridden at runtime):
+
+| Variable                        | Config Path                          |
+| ------------------------------- | ------------------------------------ |
+| `FRONTMCP_CSP_ENABLED`          | `server.csp.enabled`                 |
+| `FRONTMCP_CSP_DIRECTIVES`       | `server.csp.directives` (serialized) |
+| `FRONTMCP_CSP_REPORT_URI`       | `server.csp.reportUri`               |
+| `FRONTMCP_CSP_REPORT_ONLY`      | `server.csp.reportOnly`              |
+| `FRONTMCP_HSTS`                 | `server.headers.hsts`                |
+| `FRONTMCP_CONTENT_TYPE_OPTIONS` | `server.headers.contentTypeOptions`  |
+| `FRONTMCP_FRAME_OPTIONS`        | `server.headers.frameOptions`        |
+
+## Common Patterns
+
+| Pattern               | Correct                           | Incorrect                       | Why                                                  |
+| --------------------- | --------------------------------- | ------------------------------- | ---------------------------------------------------- |
+| CSP directives format | `{ 'default-src': "'self'" }`     | `"default-src 'self'"` (string) | Config schema expects a record, not a string         |
+| Value-less directives | `'upgrade-insecure-requests': ''` | Omitting them                   | Empty string preserves the directive in output       |
+| Testing CSP           | Start with `reportOnly: true`     | Enforce immediately             | Report-only lets you fix violations without blocking |
+| HSTS in dev           | Omit `hsts` in dev config         | `max-age=31536000` in dev       | HSTS persists in browser cache, hard to undo locally |
+
+## Verification Checklist
+
+### Configuration
+
+- [ ] `csp.enabled: true` in production deployment
+- [ ] `directives` covers at least `default-src`
+- [ ] `reportUri` set for CSP violation monitoring
+- [ ] `hsts` set with appropriate `max-age` for production
+
+### Runtime
+
+- [ ] `curl -I` shows `Content-Security-Policy` header
+- [ ] `X-Content-Type-Options: nosniff` present
+- [ ] `X-Frame-Options: DENY` present (or `SAMEORIGIN` if iframes needed)
+- [ ] Report-only mode tested before enforcement
+
+## Troubleshooting
+
+| Problem                               | Cause                                         | Solution                                                |
+| ------------------------------------- | --------------------------------------------- | ------------------------------------------------------- |
+| CSP header missing                    | `csp.enabled` not set or build not rebuilt    | Set `enabled: true` and rebuild                         |
+| Assets blocked by CSP                 | Missing directive for CDN/external source     | Add the source to the appropriate directive             |
+| Browser forced to HTTPS unexpectedly  | HSTS set before HTTPS configured              | Clear browser HSTS cache or use `max-age=0` temporarily |
+| `Invalid frontmcp.config: directives` | Using string instead of record for directives | Change to `{ 'directive-name': 'value' }` object format |
+
+## Examples
+
+| Example                                                                                        | Level        | Description                                                                                                            |
+| ---------------------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------- |
+| [`csp-report-only`](../examples/configure-security-headers/csp-report-only.md)                 | Basic        | Test CSP policies in report-only mode to identify violations before enforcement                                        |
+| [`full-production-headers`](../examples/configure-security-headers/full-production-headers.md) | Intermediate | Complete security headers configuration for production with CSP enforcement, HSTS preload, and clickjacking protection |
+
+> See all examples in [`examples/configure-security-headers/`](../examples/configure-security-headers/)
+
+## Reference
+
+- [Documentation](https://docs.agentfront.dev/frontmcp/deployment/security-headers)
+- Related skills: `configure-deployment-targets`, `configure-http`, `frontmcp-deployment`

package/catalog/frontmcp-deployment/SKILL.md

@@ -64,6 +64,7 @@ Entry point for deploying and building FrontMCP servers. This skill helps you ch
 | Embed MCP into an existing Node.js application    | `build-for-sdk`             | Library build for programmatic usage without standalone server          |
 | Write a Dockerfile for Node.js deployment         | `deploy-to-node-dockerfile` | Dockerfile configuration for Node.js deployment                         |
 | Configure Vercel-specific settings (vercel.json)  | `deploy-to-vercel-config`   | Vercel-specific configuration (vercel.json)                             |
+| Connect MCP clients (Claude, Cursor, VS Code)     | `mcp-client-integration`    | Configure .mcp.json for stdio, HTTP, or Unix socket transport           |
 
 ### CLI Commands for Deployment and Operations
 

package/catalog/frontmcp-deployment/examples/build-for-cli/cli-binary-build.md

@@ -18,8 +18,7 @@ Build a FrontMCP server as a standalone binary using Node.js Single Executable A
 
 ```typescript
 // src/main.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'greet',

package/catalog/frontmcp-deployment/examples/build-for-cli/unix-socket-daemon.md

@@ -18,8 +18,7 @@ Run a FrontMCP server as a local daemon accessible via Unix socket for IDE exten
 
 ```typescript
 // src/main.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'lookup',

package/catalog/frontmcp-deployment/examples/build-for-mcpb/mcpb-bundle-build.md

@@ -0,0 +1,117 @@
+---
+name: mcpb-bundle-build
+reference: build-for-mcpb
+level: basic
+description: 'Produce a .mcpb archive for Claude Desktop with metadata, tools, and install-time user_config.'
+tags: [deployment, mcpb, bundle, claude-desktop, user-config]
+features:
+  - 'Using `frontmcp build --target mcpb` to produce a single `.mcpb` archive'
+  - 'Translating `setup.steps` into MCPB `user_config` + `${user_config.KEY}` env bindings'
+  - 'Validating the archive round-trip with `frontmcp mcpb validate`'
+---
+
+# MCPB Bundle Build
+
+Produce a .mcpb archive for Claude Desktop with metadata, tools, and install-time user_config.
+
+## Code
+
+```typescript
+// src/main.ts
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
+
+@Tool({
+  name: 'greet',
+  description: 'Greet a user by name',
+  inputSchema: { name: z.string() },
+})
+class GreetTool extends ToolContext<{ name: string }> {
+  async execute(input: { name: string }) {
+    const apiBase = process.env.API_BASE ?? 'https://api.example.com';
+    return {
+      content: [{ type: 'text' as const, text: `Hello, ${input.name}! (via ${apiBase})` }],
+    };
+  }
+}
+
+@App({ name: 'GreeterApp', tools: [GreetTool] })
+class GreeterApp {}
+
+@FrontMcp({
+  info: { name: 'greeter-mcpb', version: '1.0.0' },
+  apps: [GreeterApp],
+})
+export default class GreeterServer {}
+```
+
+```js
+// frontmcp.config.js
+const { z } = require('zod');
+
+module.exports = {
+  name: 'greeter-mcpb',
+  version: '1.0.0',
+  entry: './src/main.ts',
+  nodeVersion: '>=22.0.0',
+  deployments: [
+    {
+      target: 'mcpb',
+      displayName: 'Greeter',
+      longDescription: '# Greeter\n\nSays hi to the configured API.',
+      author: { name: 'Acme', email: 'hello@acme.dev' },
+      license: 'Apache-2.0',
+      homepage: 'https://acme.dev/greeter',
+      repository: 'https://github.com/acme/greeter',
+      icon: 'assets/icon.png',
+      keywords: ['greeting', 'demo'],
+      compatibility: {
+        claude_desktop: '>=1.0.0',
+        platforms: ['darwin', 'linux', 'win32'],
+        runtimes: { node: '>=22.0.0' },
+      },
+      sea: { enabled: true },
+    },
+  ],
+  // Install-time questions — each step becomes a user_config entry + env var.
+  setup: {
+    steps: [
+      {
+        id: 'api-base',
+        prompt: 'API Base URL',
+        description: 'Endpoint the greeter should call',
+        env: 'API_BASE',
+        schema: z.string().url().default('https://api.example.com'),
+      },
+      {
+        id: 'api-token',
+        prompt: 'API Token',
+        description: 'Personal access token for the API',
+        env: 'API_TOKEN',
+        sensitive: true,
+        schema: z.string().min(1),
+      },
+    ],
+  },
+};
+```
+
+```bash
+# Build — produces dist/mcpb/greeter-mcpb-1.0.0.mcpb
+frontmcp build --target mcpb
+
+# Validate the archive
+frontmcp mcpb validate dist/mcpb/greeter-mcpb-1.0.0.mcpb
+
+# Open in Claude Desktop to install
+open dist/mcpb/greeter-mcpb-1.0.0.mcpb
+```
+
+## What This Demonstrates
+
+- Using `frontmcp build --target mcpb` to produce a single `.mcpb` archive
+- Translating `setup.steps` into MCPB `user_config` + `${user_config.KEY}` env bindings
+- Validating the archive round-trip with `frontmcp mcpb validate`
+
+## Related
+
+- See `build-for-mcpb` for the full manifest reference, user_config type resolution, SEA binary packaging, and cross-platform `--merge-from` workflow.

package/catalog/frontmcp-deployment/examples/build-for-sdk/connect-openai.md

@@ -18,9 +18,7 @@ Use `connectOpenAI()` to get tools formatted for OpenAI's function-calling API.
 
 ```typescript
 // src/openai-integration.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { connectOpenAI } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, connectOpenAI, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'search_docs',

package/catalog/frontmcp-deployment/examples/build-for-sdk/create-flat-config.md

@@ -18,8 +18,7 @@ Spin up an in-memory FrontMCP server from a flat config object using `create()`.
 
 ```typescript
 // src/embedded-server.ts
-import { create, tool } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { create, tool, z } from '@frontmcp/sdk';
 
 async function main() {
   const server = await create({

package/catalog/frontmcp-deployment/examples/build-for-sdk/multi-platform-connect.md

@@ -18,8 +18,7 @@ Connect the same FrontMCP server to multiple LLM platforms using platform-specif
 
 ```typescript
 // src/server.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'translate',
@@ -49,7 +48,8 @@ export default TranslateSDK;
 
 ```typescript
 // src/connect-all-platforms.ts
-import { connectOpenAI, connectClaude, connectLangChain, connectVercelAI } from '@frontmcp/sdk';
+import { connectClaude, connectLangChain, connectOpenAI, connectVercelAI } from '@frontmcp/sdk';
+
 import TranslateSDK from './server';
 
 async function main() {

package/catalog/frontmcp-deployment/examples/deploy-to-cloudflare/basic-worker-deploy.md

@@ -18,8 +18,7 @@ Deploy a FrontMCP server to Cloudflare Workers with a minimal configuration.
 
 ```typescript
 // src/server.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'echo',

package/catalog/frontmcp-deployment/examples/deploy-to-cloudflare/worker-custom-domain.md

@@ -24,8 +24,7 @@ cd my-app
 
 ```typescript
 // src/server.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'translate',

package/catalog/frontmcp-deployment/examples/deploy-to-cloudflare/worker-with-kv-storage.md

@@ -18,8 +18,7 @@ Deploy a FrontMCP server to Cloudflare Workers with KV namespace for session and
 
 ```typescript
 // src/server.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'store_value',

package/catalog/frontmcp-deployment/examples/deploy-to-lambda/lambda-handler-with-cors.md

@@ -19,8 +19,7 @@ Create a custom Lambda handler with an explicit API Gateway definition for CORS
 ```typescript
 // src/lambda.ts
 import { createLambdaHandler } from '@frontmcp/adapters/lambda';
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'analyze',

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

@@ -18,8 +18,7 @@ Deploy a FrontMCP server to Vercel serverless functions with Vercel KV for sessi
 
 ```typescript
 // src/server.ts
-import { FrontMcp, App, Tool, ToolContext } from '@frontmcp/sdk';
-import { z } from 'zod';
+import { App, FrontMcp, Tool, ToolContext, z } from '@frontmcp/sdk';
 
 @Tool({
   name: 'greet',