Connect Claude Desktop to a Plone site#
This guide shows you how to let Claude Desktop read and change a Plone site. You install plone-client in a terminal, tell Claude Desktop where to find it, and restart the application.
Claude Desktop starts the plone-client MCP server by itself, each time it opens, so you never start the server by hand.
You need the following.
uv, which installs plone-client.
The address of a Plone site, with a username and a password. To try this on a local site, follow Run a Plone site for testing first.
Install plone-client#
In a terminal, install plone-client with the MCP server and Markdown support.
uv tool install --python 3.13 "plone-client[mcp,markdown]"
Check that it works.
plone-client --version
If the terminal answers that it cannot find plone-client, run uv tool update-shell, then open a new terminal.
Add your site as a profile#
A profile stores the site’s address and your username. The password goes into your keyring, so Claude never sees it.
plone-client profile add blog --url https://example.org --username editor
Replace blog, the address, and editor with your own.
When asked, type the password.
To let Claude read the site but not change it, add --read-only to that command.
This is the safest way to start on a real site; Protect a site from an agent explains your other options.
Check that the profile can log in.
plone-client profile test blog
Find the full path of plone-client#
Claude Desktop does not start from your terminal, so it may not find a program by its name alone. Give it the full path.
which plone-client
where plone-client
Copy the line that this prints. You need it in the next step.
Add the server to the configuration file#
Open the configuration file.
Open the Settings window from the Claude menu in your system’s menu bar, not from inside the conversation window.
Select Developer in the sidebar.
Select Edit Config.
Claude Desktop creates the file if it does not exist, and shows it to you. Open it in a text editor. If you cannot find the button, open the file directly.
System |
File |
|---|---|
macOS |
|
Windows |
|
Linux |
|
Add the server.
In command, write the full path that you copied.
In args, write the name of your profile in place of blog.
{
"mcpServers": {
"plone-blog": {
"command": "/Users/you/.local/bin/plone-client",
"args": ["mcp", "--profile", "blog"]
}
}
}
Write each backslash in the path twice.
{
"mcpServers": {
"plone-blog": {
"command": "C:\\Users\\you\\.local\\bin\\plone-client.exe",
"args": ["mcp", "--profile", "blog"]
}
}
}
If the file is empty, paste this as its whole content.
If it already has content, keep that content.
Add mcpServers next to the other top-level keys, with a comma between them.
If mcpServers is already there, add plone-blog inside it, next to the other servers.
Save the file.
Restart Claude Desktop#
Quit Claude Desktop completely, then open it again. Closing the window is not enough, because the application keeps running and does not read the file again.
On macOS, select .
On Windows, right-click the Claude icon in the notification area, and quit from there.
Check the connection#
Select the + button below the chat box.
Select Connectors.
Look for
plone-blogin the list.
Then ask Claude for this.
Use the site_info tool of plone-blog, and tell me which site and user you see.
Claude asks for your approval before it uses a tool. It answers with the address of your site, your username, and whether the site is read-only.
Your site is connected. Before you give Claude real work, read Protect a site from an agent.
If the server does not appear#
Run the same command that Claude Desktop runs, with your full path, in a terminal.
/Users/you/.local/bin/plone-client mcp --profile blog
If it is working, it prints nothing and waits; press Control+C to stop it. If it prints an error, the error says what is wrong.
If that works, read the logs of Claude Desktop.
The file mcp.log reports connections, and mcp-server-plone-blog.log holds what the server printed.
System |
Folder |
|---|---|
macOS |
|
Windows |
|
Linux |
|
What you see |
What to do |
|---|---|
|
The file has a JSON error, such as a missing comma, or Claude Desktop did not restart. Check the commas and quit the application again. |
|
|
|
Reinstall with the |
The tools that change the site are missing |
The profile is read-only, or the server runs with |
An error about a missing secret or the keyring |
See Manage profiles for other ways to keep the password. |
After you edit the configuration file, restart Claude Desktop again. Troubleshoot covers the errors that come from the site.