mcp
MCP server from nlvcodes/mcp-server
claude mcp add --transport stdio nlvcodes-mcp-server node server.js \ --env PORT="3000" \ --env NODE_ENV="development" \ --env PayloadConfig="path/to/payload/config (adjust as needed)"
How to use
This MCP server exposes the Payload CMS-based website template as a configurable service. It allows you to manage content for posts, pages, and media through a unified admin interface, while leveraging Payload's built-in access control, layout builder blocks, draft and live previews, and on-demand revalidation. Use the provided admin routes to authenticate, manage collections, and configure globals like header and footer data. The server powers the front-end website by serving API endpoints for content delivery, draft previews, and revalidation hooks, enabling a smooth content workflow from creation to deployment.
How to install
Prerequisites:
- Node.js (14+ or recommended LTS) installed on your system
- npm or pnpm/yarn for package management
Steps:
- Clone the repository locally or navigate to your MCP server directory.
- Install dependencies:
- npm: npm install
- or pnpm: pnpm install
- or yarn: yarn install
- Copy environment variables from a template if provided, e.g., cp .env.example .env and customize values such as database and auth settings.
- Start the MCP server:
- npm run dev (for development) or npm start (for production) depending on your setup
- Open http://localhost:3000 (or the port you configured) to access the admin dashboard and the website frontend.
Note: Ensure any required database (e.g., MongoDB, PostgreSQL) services are running and accessible with the credentials configured in your environment file.
Additional notes
Tips and common considerations:
- Update environment variables to point to your database and any external services Payload requires.
- If you enable draft or live previews, ensure your front-end build and revalidation hooks are correctly wired to your hosting environment (Next.js or similar).
- Check logs for any authentication or access-control issues when deploying to production.
- For local development, use PORT 3000 unless you have a conflicting service running.
- The Payload CMS template supports hot-reload during development; changes to content schemas or collections may require a server restart in some setups.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud