Talk to your Plone website instead of clicking through it. Plone MCP lets AI assistants like Claude create and edit pages, publish content, search the site, and manage translations on your behalf, in...
概览
Talk to your Plone website instead of clicking through it. Plone MCP lets AI assistants like Claude create and edit pages, publish content, search the site, and manage translations on your behalf, in plain language - no coding required to use it, and nothing to change on your Plone site to enable it. It's built on the Model Context Protocol (MCP), an open standard that lets AI assistants safely connect to external tools and data. Plone MCP exposes Plone's REST API as a set of MCP tools, so any MCP-compatible client - Claude Desktop, Claude Code, and others - can drive your site, and developers can script, automate, or build on top of the same tools. Requires Node.js 22+. Add this to Claude Desktop's config file, then restart Claude Desktop: - macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - Windows: %APPDATA%\Claude\claude_desktop_config.json Now ask Claude to connect to your Plone site, e.g. "Connect to https://demo.plone.org as admin/admin".
README
以下为原文 README 节选,完整内容请查看原文。
Plone MCP Server
Talk to your Plone website instead of clicking through it. Plone MCP lets AI assistants like Claude create and edit pages, publish content, search the site, and manage translations on your behalf, in plain language - no coding required to use it, and nothing to change on your Plone site to enable it.
It’s built on the Model Context Protocol (MCP), an open standard that lets AI assistants safely connect to external tools and data. Plone MCP exposes Plone’s REST API as a set of MCP tools, so any MCP-compatible client - Claude Desktop, Claude Code, and others - can drive your site, and developers can script, automate, or build on top of the same tools.
Quickstart
Requires Node.js 22+. Add this to Claude Desktop’s config file, then restart Claude Desktop:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"plone": {
"command": "npx",
"args": ["-y", "@plone/mcp"]
}
}
}
Now ask Claude to connect to your Plone site, e.g. “Connect to https://demo.plone.org as admin/admin”.
Prerequisites
-
Node.js 22+ - Required to run the server (
^20.19.0 || >=22.12.0; install:brew install nodeon macOS or from nodejs.org) -
Plone 6.0+ site with REST API - The CMS you’ll be connecting to
pnpmis only needed if you want to clone the repo and develop locally (see Local Development). The recommended setup below usesnpxand doesn’t require cloning anything.
Transports
The server ships two entry points:
- STDIO (
plone-mcpbin /dist/stdio-server.js) - for local MCP clients such as Claude Desktop. - HTTP (
dist/http-server.js) - a streamable-HTTP server with per-session state, listening onPORT(default3001) at/mcp. Start it withmake start.
Quick Start using Claude Desktop as an example
The @plone/mcp package is published on npm, so there’s nothing to install or build - npx fetches and runs it on demand.
- Configure Claude Desktop
Add to Claude’s configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
With environment variables (optional):
{
"mcpServers": {
"plone": {
"command": "npx",
"args": ["-y", "@plone/mcp"],
"env": {
"PLONE_BASE_URL": "https://demo.plone.org",
"PLONE_USERNAME": "admin",
"PLONE_PASSWORD": "admin"
}
}
}
}
Without environment variables (useful if you connect to different Plone sites and prefer to pass credentials per session via plone_configure):
{
"mcpServers": {
"plone": {
"command": "npx",
"args": ["-y", "@plone/mcp"]
}
}
}
- Restart Claude Desktop
安装
npx -y @plone/mcp配置
{
"mcpServers": {
"plone": {
"command": "npx",
"args": ["-y", "@plone/mcp"]
}
}
}