mcp-deploy-mcp
Integrates with GitHub to check repository compatibility for deployment via the mcp-deploy platform, using the GitHub API (requires optional token for higher rate limits).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-deploy-mcpscaffold my new MCP server for a time tracking tool"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Deploy Assistant (mcp-deploy-mcp)
A remote MCP server that helps Claude design, scaffold, and validate MCP servers compatible with the mcp-deploy platform — and is itself deployed by it.
Tools
Tool | Purpose |
| Platform overview + topic guides (worker format, manifest, tool design, testing/release, auth, gotchas) |
| Generate a complete, working repo for a new MCP (13 files, pre-validated) |
| JSON Schema + naming rules + reserved keys for |
| Validate a drafted manifest, with optional |
| Verify a GitHub repo's release carries deployable assets and a valid manifest |
| Minimal scaffolded repo + the production paper-search manifest |
Related MCP server: MCP Server Generator
How it stays fresh
All servable knowledge lives in content/. It's bundled into the worker at build time as a fallback, but at runtime the worker fetches the latest content/ from this repo's main branch (cached ~6h in the Durable Object's SQLite). Editing content/ and pushing to main updates every deployed instance — no release or redeploy needed. Code changes (validation rules, new tools) ship via tagged releases like any mcp-deploy MCP.
Tool responses tag where content came from: live, cached, or bundled@<version>.
Development
npm install
npm run dev # wrangler dev — http://localhost:8787 (health at /, MCP at /mcp)
npm test # vitest (network-dependent tests skip gracefully when rate-limited)
npm run typecheck
npm run build # produces dist/worker.mjsReleasing
# bump "version" in mcp-deploy.json, package.json, and src/content.ts (VERSION), then:
git tag v0.1.0
git push origin main v0.1.0CI attaches worker.mjs + mcp-deploy.json to the GitHub Release — the two assets the platform deploys from.
Secrets
None required. Optional GITHUB_TOKEN raises GitHub API rate limits for check_repo_compatibility (Workers share egress IPs, so the unauthenticated 60/hr pool is sometimes exhausted).
This server cannot be deployed
Maintenance
Related MCP Connectors
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloudflare Workers MCP server: claude-skill-validator
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseCqualityDmaintenanceAn MCP server that enables persistent memory, structured thinking sessions, and project-based knowledge management for Claude. It includes specialized coding tools for package discovery and reinvention prevention by validating code against existing libraries and APIs.173MIT
- FlicenseNot gradedqualityFmaintenanceCreates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.11-
- AlicenseCqualityCmaintenanceA comprehensive MCP server that enables Claude to read, create, edit, and generate code from Figma designs. Supports design tokens, code generation to multiple frameworks, and accessibility checks.1004MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude to deploy full-stack web apps to Cloudflare, including databases, authentication, and file storage, directly through natural language.-