What is the Plate Playground Template?
Plate Playground Template is a Next.js 16 starter with the Plate rich-text editor, AI plugins and shadcn/ui components. It is a template, not an MCP server, but it includes a project MCP file that runs the shadcn CLI server, so an AI coding agent can browse and install Plate registry items.
It is a Next.js template that bundles the Plate editor with AI, plugins and components. The README lists Next.js 16, Plate, shadcn/ui and an MCP link to the Plate docs. You can install it with a shadcn command or use it as a GitHub template.
It is not an MCP server of its own. The repository includes a .mcp.json that starts the shadcn CLI's MCP server over stdio. That gives an AI coding agent registry access the moment you open the project.
What changes in your agent's output
- The agent starts from a working editor route, so it edits real code instead of scaffolding one.
- Registry items are searched and installed through the shadcn server rather than written from memory.
- The project already carries agent folders and a lockfile for skills, so the agent has local conventions to follow.
- Editor, AI and upload settings are in the README, so the agent can tell which environment values the project needs.
How the setup works
- Run the shadcn add command for the AI editor, or create a repository from the template.
- Install dependencies with bun and copy the example environment file.
- Start the dev server and open the editor page, then let your agent use the MCP entry in the project.
Who the Plate Playground Template is for
Best for
- Builders who want a running rich-text editor with AI features to modify, not a blank project.
- Teams using the Plate MCP setup who want a project where that config is already in place.
- Agent workflows that rely on the shadcn MCP server for installing components.
Not for
- Anyone wanting a standalone MCP server to plug into another project. Use the Plate MCP setup for that.
- Production use without review. The README says to replace the upload development check with real session and permission checks and add per-user limits.
- Non-React stacks, since the template is Next.js.
Use it with UiChemy
The template produces a React editor for an app you host. For a WordPress site, UiChemy builds there: AI to WordPress imports an existing AI build, and Composer edits it inside Elementor or Gutenberg. Click Get Started on uichemy.com.
Connect Plate Playground Template: Next.js Editor Starter With MCP Config to your AI client
npx shadcn@latest add @plate/editor-aiPick an install route
Run
npx shadcn@latest add @plate/editor-ai, or use the repository as a GitHub template and runbun install. Node.js 20 or newer and bun are required.Set the environment
Copy
.env.exampleto.env.localand setUPLOADTHING_TOKEN. AI works when you enter your own AI Gateway key in the editor settings.Start the app
Run
bun devand openhttp://localhost:3000/editor.Use the MCP file
The
.mcp.jsonin the repository runsnpx -y shadcn@latest mcpover stdio. Most clients pick up a project-level file, or copy the entry into your client config. Claude reads a project.mcp.jsondirectly.
Client configuration
{
"mcpServers": {
"plate": {
"command": "npx",
"args": ["-y", "shadcn@latest", "mcp"],
"type": "stdio"
}
}
}Endpoints and ports
http://localhost:3000/editorDev server route from the READMEhttps://github.com/udecode/plate-playground-templateThe .mcp.json in the repository rootnpx -y shadcn@latest mcpstdio serverWhat you can do with it
- Next.js 16 starterA working app with the Plate editor, plugins and components, ready to run on a dev server.
- AI in the editorThe template installs the AI editor through the shadcn registry. You supply your own AI Gateway key in the editor settings.
- MCP file includedA project
.mcp.jsonpoints the agent at the shadcn CLI server, the same one the Plate docs use. - Agent folders presentThe repository includes agent configuration folders and a skills lockfile alongside the app code.
- Upload setupUploadThing handles file uploads, and the README warns to replace the dev-only check before production.
- Two install routesUse the shadcn CLI command or generate a repository from the template.
Tools it exposes
get_project_registries
Returns the registry names set in components.json.
list_items_in_registries
Lists items from one or more registries.
search_items_in_registries
Fuzzy search across registries by query.
view_items_in_registries
Shows item details including file contents.
get_item_examples_from_registries
Finds usage examples and demos with source code.
get_add_command_for_items
Returns the CLI command that installs the given items.
get_audit_checklist
Returns a checklist for checking added components.
Frequently asked questions
Is Plate Playground Template an MCP server?
No. It is a Next.js starter. It includes a project MCP file that runs the shadcn CLI's MCP server, which is the server the Plate docs use. The tools listed on this page come from that server, not from the template.
How do I install it?
Run npx shadcn@latest add @plate/editor-ai, or use the repository as a GitHub template and run bun install. Then copy .env.example to .env.local, set the UploadThing token and run bun dev. Node.js 20 or newer is needed.
What does the MCP file do?
It registers a server named plate that runs npx -y shadcn@latest mcp over stdio. With a Plate registry configured in your project, an agent can search, view and install Plate items through the shadcn tools.
How is it different from the Plate MCP setup?
The Plate MCP page explains how to add the Plate registry to an existing shadcn project. This template is a finished starter app that already has that wiring, so it suits new projects.
How does AI work in it?
The README says to enter your own AI Gateway key in the editor settings, and that the example API routes use the caller's key. If you use a shared server credential, authorize each request and enforce per-user limits before calling the provider.
Is it production ready?
Treat it as a starting point. The README says uploads work in local development, and that you must replace the development check in the upload file with your own session and permission checks and add per-user upload limits before enabling production uploads.
What license does it use?
The repository is MIT licensed, and GitHub detects MIT. The main Plate repository has its own license notes, including per-package licenses, so check that repository too before you depend on a specific Plate package in production.



