Forge
A self-compounding factory for MCP servers and Claude skills.
A repeatable production line for MCP servers and skills: a new integration ships in hours, and every server inherits the same architecture and security baseline by default.
Forge is a meta-tooling system that turns one-off automation into a repeatable production line. Instead of hand-building each MCP server and Claude skill from scratch, the patterns are codified into a library of generator skills plus a custom Cloudflare Workers MCP that deploys, configures, versions, and rolls back Workers programmatically from inside a Claude conversation. A new integration ships in hours instead of days, and every server inherits the same production architecture and security baseline by default rather than by remembering to add it. Each tool built makes the next one faster: the work compounds instead of piling up as disconnected scripts.
Each tool built makes the next one faster. That is the whole point: the work compounds instead of piling up as disconnected scripts.
- 01A new, production-grade integration ships in minutes instead of days
- 02Every server inherits the same architecture and security baseline by default
- 03Seven-dimension audit (A--F) gates every server before it ships
- 04Agent accuracy from ~31% at 50 tools to ~89% at 8: the tool discipline Forge enforces
01. Pattern-codified MCP builds
- Six-tool pattern (search/get/list/create/update/delete) with rich optional params, not one tool per endpoint
- The discipline that takes agent accuracy from roughly 31% at 50 tools to 89% at 8
- Schema-first Zod contracts with a .describe() on every parameter; structured output where it helps
- snake_case service-prefixed names and all four annotation hints set on every tool
- Recoverable errors: isError with explicit what-went-wrong and what-to-try-next guidance
02. Custom Cloudflare deploy loop
- deploy_worker, update_worker_code, rollback_worker, list_versions, list_deployments from the conversation
- Configuration as tool calls: set_worker_secrets, set_cron_triggers, attach_custom_domain, create_route
- Two-MCP routing: the custom MCP owns the Worker lifecycle, the CF Developer Platform MCP owns storage and docs
03. KV-backed secrets (the deploy-safe pattern)
- Standard Worker secret bindings get wiped on every deploy and break update_worker_code
- Secrets live in a KV namespace read at runtime, so deploys, code updates, and rollbacks never touch credentials
- Placed once, out of band; this is what makes Claude-managed deploys actually viable
04. Built-in quality gate
- Seven-dimension audit, A--F: tool design, error handling, security, context efficiency, docs, reliability, maintenance
- Weighted toward what matters most: tool design 25%, error handling and security 20% each
- Context-budget discipline: a clean six-tool server lands around 1,000 to 2,000 tokens total
05. Security baseline by default
- OAuth 2.1 with PKCE, Resource Indicators, short-lived access tokens, Dynamic Client Registration
- Three-layer input validation: schema constraints, context-aware sanitization, output sanitization
- Audit logging with PII redaction and retention notes for SOC 2, HIPAA, and SOX
- Tool-poisoning defense: descriptions hashed on first connect with change alerts; per-user rate limiting
06. What it has produced
- MCP Fleet: Dropbox Sign, NetSuite, Celigo, HubSpot (+ Conversations), Stagger, plus the cf-workers-mcp control plane
- Skills Library: sponsor-onboarder, celigo-flow-ops, cf-devops, mcp-ops, linear-issue-creator, and more
- See the MCP Fleet and Skills Library entries in the work index for the full inventory
+-----------------------------------------------------------+
| FORGE (the factory) |
+----------------------------+------------------------------+
| Generator skills | Custom CF Workers MCP |
| mcp-ops / cf-devops | deploy / update / rollback |
| skill-creator | secrets / crons / domains |
| github-repo-creator | (KV-backed, deploy-safe) |
+----------------------------+------------------------------+
| emit spec ^
v | new patterns
+-----------------------------------------------------------+
| Quality gate: 7-dimension audit (A--F) |
| context budget ~1-2k tokens + security baseline |
| (OAuth 2.1 + PKCE, 3-layer input validation) |
+-----------------------------------------------------------+
| passing
+---------------+--+------------+
v v v
+-------------+ +-------------+ +-------------+
| New MCP | | New skill | | New repo |
| -> fleet | | -> library | | (GitHub) |
+-------------+ +-------------+ +-------------+
|
+--> patterns fold back up (the compounding loop)Passing servers fold their patterns back into the generators; the next build starts further ahead than the last.