DocuMCP v1.0.0
This is the first stable release of DocuMCP — an intelligent MCP server for documentation deployment. It introduces pluggable deploy-target adapters, first-class Vercel support, and the live documentation site at https://documcp.dev.
⚠ Breaking Changes
- `deploy_pages` is now a deprecated alias for `deploy_site` (target=github-pages). Replace usages with `deploy_site`. The alias will be removed in v1.1.0.
🚀 Features
- deploy: implement Vercel deploy-target adapter (ADR-018 D1) — `deploy_site` tool with `target=vercel` generates `vercel.json` + GitHub Actions workflow (#127)
- deploy: add `deploy_site` as primary deployment tool; `deploy_pages` kept as back-compat shim (#130)
- deploy-targets: pluggable `DeployTargetAdapter` interface and adapter registry (`src/deploy-targets/`)
- deploy: each adapter emits a target-specific workflow filename (`deploy-github-pages.yml`, `deploy-vercel.yml`) — eliminates filename collisions when multiple adapters ship
- deploy: Vercel adapter generates `VERCEL_SETUP.md` — an inline numbered setup checklist committed to the user's repo
- deploy: `deploy_site` nextSteps leads with a `vercel link` step when `target=vercel`
- deploy: `deploy_site` warns when a competing deploy workflow from another target already exists
- docs: DocuMCP documentation site live at https://documcp.dev (deployed via Vercel)
- contributing: add `docs/contributing/adding-deploy-targets.md` — 7-step guide for adding new deployment platforms
- community: post implementation-step guides on issues #128 (Netlify) and #129 (Cloudflare Pages)
📚 Documentation
- add `docs/how-to/deploy-to-vercel.md` how-to guide
- fix all broken internal links and anchors across documentation site
- publish `LLM_CONTEXT.md` to repository and restore GitHub blob links in reference docs
- remove stale static `docs/sitemap.xml` — Docusaurus auto-generates the sitemap at build time
- switch primary documentation domain to https://documcp.dev
🐛 Bug Fixes
- deploy: add `docs/.vercelignore` to exclude TypeDoc `api/` output that caused Vercel path conflicts
- deploy: correct Vercel framework slug from `docusaurus2` to `docusaurus-2`
- deploy: run `npm run build` locally before `vercel deploy --archive=tgz` to avoid Vercel build conflicts
- ci: add `fail-fast: false` to test matrix so all jobs run to completion on failure
- ci: fix Jest JSON field names (`name`/`assertionResults`) for auto-issue creation
- tests: update `deployPages` test assertion for refactored `generatedFiles` response shape
🔄 CI/CD
- auto-create and auto-close GitHub issues for failing tests
- add CI gate guard for releases
Installation
```bash
npm install -g documcp@1.0.0
```
System Requirements
- Node.js 20.x or higher
- npm 9.x or higher
Quick Start
```bash
npm install -g documcp
Deploy your docs to Vercel
In Claude Desktop / Cursor with DocuMCP configured:
deploy_site({ projectPath: "./my-project", target: "vercel" })
```
Documentation
Full documentation at https://documcp.dev