Select one or more tags, then press “Search Plugins”

Find Plugin with any / all of the selected criteria
Search Plugin

GripMCP – MCP Server Plugin for Wordpress: Connect Claude & AI Assistants - Rating, Reviews, Demo & Download

GripMCP – MCP Server Plugin for Wordpress: Connect Claude & AI Assistants - Rating, Reviews, Demo & Download
No ratings yet
Free
Follow for free plugins, new theme releases and theme news

Plugin Description

GripMCP turns your WordPress site into a Model Context Protocol (MCP) server. Paste one address into your AI assistant, approve the connection, and you can manage your site’s content with AI in plain language: write and edit posts, upload images, organise categories and menus, moderate comments, look into errors, and more. Paid plans add more tools for developers, agencies and stores.

The assistant never gets more power than the person who connected it. Every action is checked against that WordPress user’s real role and capabilities, deletions wait for your approval unless you choose otherwise, and the endpoint stays off until you switch it on.

Connect in a minute

  • One address. Your site answers at its own address followed by /mcp.
  • One-click connect. In Claude, add a custom connector, paste the address, sign in to WordPress and approve. No tokens or config files. This uses the standard MCP authorization flow (OAuth 2.1 with PKCE and dynamic client registration), so other MCP clients that support it connect the same way.
  • Access tokens for config-file clients such as Claude Desktop or mcp-remote. Make as many as you need: tokens are stored hashed, expire after 90 days unless you choose otherwise, work only at the GripMCP endpoint, and can be revoked at any time. WordPress Application Passwords work too.
  • You choose who can connect. Administrators always can; other roles only when you allow them.

What your assistant can do with the free plugin

  • Content: list, read, create, update, edit in place and delete posts, pages and custom post types; categories, tags and custom taxonomies; menus; comments; custom fields; reading WordPress’s settings (changing them stays with you, in Settings); revisions and restore.
  • Media: upload from a link or a file in the chat, place images into a post or set them as the featured image. On assistants that support in-chat panels, you can drag images onto an upload panel right in the conversation, or open an upload page when the chat cannot reach your site.
  • Users: list users and their roles.
  • Safety: deletions held for your approval, with a check of what they would break; revisions to undo an edit.
  • Site health: site health checks, the PHP error log, a record of recent crashes, cron events, cache flushing (including Elementor and page-cache plugins such as LiteSpeed Cache and WP Rocket), and a check of how any page renders.
  • Plugin abilities: on WordPress 6.9 and later, discover and run the read-only actions other plugins publish for AI clients through the WordPress Abilities API, such as looking up orders, products or form entries. Actions that change something stay on the plugin’s own screens.
  • Progress cards: for requests that take several steps, one live card in the chat with each step and the outcome.

With a paid plan

GripMCP Creator, Operator and Fleet are a separate plugin with more tools for developers, agencies and stores, sold at gripmcp.com and not hosted on WordPress.org. Each plan includes the ones before it; the pricing page compares them.

The Abilities tools appear on WordPress 6.9 and later. If tools are added after you connect, for example by a WordPress update, reconnect GripMCP in your AI app to load them; GripMCP tells the assistant.

Safe by default

  • The endpoint is off until you switch it on, and it requires HTTPS.
  • Every tool checks the connected user’s WordPress capabilities. GripMCP never grants a capability the user does not already have.
  • The assistant writes content, not code: a change that would add code such as a script, an embedded frame, an event handler, a javascript: link or a block’s custom CSS to a post or custom field is refused with the reason, even for an administrator. Code already on your pages is kept as it is, and you can add code yourself in the WordPress editor.
  • Access keys work only on the GripMCP endpoint, not on the rest of the WordPress API.
  • Destructive actions (deleting posts, pages, media, comments, categories, tags and menus, replacing a menu’s items, and removing a page-builder layout) are set to “Ask me first” on a new install: each one waits for you to approve it on a page in your own WordPress admin. Requests waiting for you are also listed on the Approvals tab of the GripMCP screen, with a count on its menu item, so a lost link never strands one. There is no way for an assistant to approve its own request. Under Permissions you can switch them off entirely, or allow them without asking.
  • Before a destructive action is put up for approval, GripMCP checks what it would break: a page that is your homepage or in a menu, an image used as the logo, site icon or a featured image, a category that is the default one or still in use. You see the findings with the request; high-risk ones recommend trying it on a staging copy first and ask you to confirm before it runs.
  • Credentials are protected: secret-looking options are refused, and passwords and API keys inside other plugins’ settings (a payment gateway’s secret key, an SMTP password) are shown to the assistant as “[redacted]”.
  • A per-user rate limit, an activity log of your assistant’s tool calls, and a connection diagnostics log for when a connector stops working.

In-chat progress cards

For requests that take several steps, assistants that support in-chat panels (the MCP Apps standard) show one live card with each step and its result, then the outcome. An assistant that declares the extensions it supports when it connects, and leaves panels out of them, is not sent the card tools at all. Developers can switch off the upload panel with the gripmcp/in_chat_uploads filter, and the cards with the gripmcp/progress_cards filter.

External services

GripMCP contacts other servers only in these cases:

  • Freemius (freemius.com), which sells and licenses the paid plans and, if you opt in, collects usage data for GripMCP. After activation GripMCP asks whether you want to opt in; skipping it sends nothing. If you opt in, Freemius receives your name and email, your site’s address, title and language, your WordPress, PHP and GripMCP versions, whether GripMCP is active or uninstalled, and the list of your plugins and themes (you can untick this one on the opt-in screen), and GripMCP checks in with Freemius once a day while you stay opted in. Freemius is also contacted when you open the Upgrade page (it loads prices and the checkout, with no details about your site), buy a plan or activate a licence, or send the optional feedback form when you deactivate (anonymous by default). The Upgrade page also loads Google’s analytics script (privacy), which records nothing because GripMCP offers no trial. See GripMCP’s privacy policy and terms.
  • WordPress.org (api.wordpress.org): Site Health’s update check, the same request WordPress itself sends. Privacy policy.
  • A web address you or your assistant give, to download a file into the Media Library.
  • Your own site, to load a page for the page-render check.

Screenshots

No screenshots provided


Reviews & Comments