Beheer je WP connects an AI assistant to WordPress for site reading, proposed edits, and Search Console analysis.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Beheer je WP.
get_connection_statusWhich site is linked, plan and site summary.
list_postsSearch posts and pages, read content.
propose_post_updatePrepare an edit for approval in wp-admin.
get_search_performanceSearch Console clicks, impressions, CTR, position; pages to improve.
get_brand_guidanceBrand notes, plan features, SEO help request.
Beheer je WP connects an AI client to one WordPress site that the user authorizes. Beheer je WP MCP server can report which site is connected, identify the active plan, and provide a site summary. It can also search posts and pages and retrieve their content for tasks such as finding related articles or summarizing existing material.
Content changes follow an approval workflow. Instead of writing directly to WordPress, the assistant creates a proposed post update. A WordPress administrator then reviews the proposal in wp-admin and accepts or rejects it. The assistant cannot approve its own proposal, so the supplied material does not describe autonomous publishing.
On the SEO Pro plan, the server reads Google Search Console information for the connected site. This includes clicks, impressions, click-through rate, and average position, along with pages that receive impressions but relatively few clicks. Search Console access is read-only.
The hosted endpoint is https://beheerjewp.nl/mcp and uses Streamable HTTP. Authentication uses OAuth with PKCE using S256, dynamic client registration, and client ID metadata documents. These mechanisms allow supported MCP clients to connect without manually creating client credentials.
The connection is scoped to the WordPress site authorized through the service. A Beheer je WP account and the Beheer je WP plugin installed on that site are required. For a developer evaluating Beheer je WP MCP server, this means there is no local package to build or run: the repository provides the public listing and connection instructions, while the MCP service is hosted by the publisher.
Add the server URL to an MCP client that supports the documented HTTP configuration. Claude Desktop can use a custom connector with the URL. Claude Code can register it with:
For Cursor, VS Code, Cline, Windsurf, and similar clients, add an HTTP server entry to the clientβs MCP configuration. Cline uses the streamableHttp type rather than the http type shown in the general example. Then complete the OAuth flow and authorize the WordPress site.
Available functions cover these areas:
Beheer je WP is suited to prompts about recent click changes, locating posts on a topic, summarizing content, or rewriting a draft title for review. The documented tools do not indicate unrestricted WordPress administration, direct publishing, or write access to Search Console.
Beheer je WP MCP server works with one authorized WordPress site per connection context. A WordPress administrator must make the final decision on proposed edits. Search Console features depend on the SEO Pro plan and remain read-only. The material does not specify environment variables, local installation steps, or a software license for the hosted server.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/beheer-je-wp)<a href="https://allmcps.com/mcp/beheer-je-wp"><img src="https://allmcps.com/api/badge/beheer-je-wp?style=directory" alt="Beheer je WP on AllMCPs" /></a>