deploy-docusaurus-mcp-vercel

Deploy to Vercel

Done when

curl https://<your-domain>/mcp returns the status JSON with "initialized": true, a docCount above 0, and baseUrl on your production domain.

Before you start

• The plugin is set up: npm run build writes build/mcp/bundle.json. If not, follow Getting started first.
• A Vercel account, and either the Vercel CLI (npx vercel) or access to the Vercel dashboard.

How to use this guide

• Do the steps in order. Run them yourself, or walk the user through them one at a time if they'd rather do it themselves or you can't run them.
• After each step, run its check. Don't move on until it passes.
• If a check fails, look for the matching symptom under Troubleshooting. If none matches, stop and tell the user what you saw.
• A step marked Needs the user needs a person. Tell the user what to do and wait for them to confirm it's done.
• Ask the user before running a step marked Confirm first.
• Don't ask the user to paste passwords, tokens, or keys into the chat. When a step needs one, tell the user where to put it.

Steps

1. Add the function {#function}

Create api/mcp.mjs in your site's root, next to docusaurus.config.js:

api/mcp.mjs

import { createWebRequestHandler } from 'docusaurus-plugin-mcp-server/adapters';
import bundle from '../build/mcp/bundle.json' with { type: 'json' };

export default {
  fetch: createWebRequestHandler({ artifacts: bundle }),
};

Vercel's Node.js runtime runs a default export with a fetch method as a web-standard handler. Vercel builds the function after your build command, so build/mcp/bundle.json exists when the function is bundled, and its file tracing includes the bundle in the function.

Check: api/mcp.mjs is next to docusaurus.config.js and imports ../build/mcp/bundle.json.

If the check fails: see Troubleshooting.

2. Add vercel.json {#vercel-json}