# Beheer je WP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/beheerjewp/beheerjewp-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/beheer-je-wp

## Description
Manage a WordPress site from your AI assistant: read, search, propose edits, Search Console data.

## Tools
Capabilities this server exposes over MCP:

- **get_connection_status** — Which site is linked, plan and site summary.
- **list_posts** — Search posts and pages, read content.
- **propose_post_update** — Prepare an edit for approval in wp-admin.
- **get_search_performance** — Search Console clicks, impressions, CTR, position; pages to improve.
- **get_brand_guidance** — Brand notes, plan features, SEO help request.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "beheer-je-wp": {
    "url": "https://beheerjewp.nl/mcp"
  }
}
```

## Documentation

## What Beheer je WP does

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.

## How it works

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.

## Setup and configuration

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:

```bash
claude mcp add --transport http beheerjewp https://beheerjewp.nl/mcp
```

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.

## Tools and capabilities

Available functions cover these areas:

- Connection status or site overview, including the linked site, plan, and summary.
- Post and page search, plus content retrieval.
- Proposed post updates that wait for wp-admin approval.
- Search Console performance data and SEO opportunity discovery on the SEO Pro plan.
- Brand guidance, product or plan capability information, and preparation of an SEO service request.

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.

## Limitations and notes

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.

_Full upstream README: https://allmcps.com/mcp/beheer-je-wp/readme_