deploy-docusaurus-mcp-netlify

Deploy to Netlify

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 Netlify account, and either the Netlify CLI (npx netlify) or access to the Netlify 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}

netlify/functions/mcp.mjs

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

const handler = createWebRequestHandler({ artifacts: bundle });

export default (request) => handler(request);

export const config = { path: '/mcp' };

config.path serves the function at /mcp instead of the default /.netlify/functions/mcp. The import goes up two directories, from netlify/functions/ to the site root.

Check: netlify/functions/mcp.mjs exists, imports ../../build/mcp/bundle.json, and exports config with path: '/mcp'.

If the check fails: see Troubleshooting.

2. Add netlify.toml {#netlify-toml}

netlify.toml

[build]
  command = "npm run build"
  publish = "build"

[functions]
  node_bundler = "esbuild"