Linux 软件免费装
Banner图

GripMCP – MCP Server for WordPress: Connect Claude & AI Assistants

开发者 akshay89
更新时间 2026年11月16日 18:34
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

assistant ai claude mcp model context protocol

下载

1.0.0 1.0.1

详情介绍:

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 What your assistant can do with the free plugin 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 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:

安装:

  1. Upload the gripmcp folder to /wp-content/plugins/, or go to Plugins → Add New → Upload Plugin and choose the zip.
  2. Activate GripMCP.
  3. Open GripMCP in the admin menu and switch the endpoint on with the switch at the top right. It saves as soon as you change it.
  4. Copy the endpoint address from the Setup tab.
  5. Connect your assistant:
  6. Claude (web, desktop or mobile): Settings → Connectors → Add custom connector, paste the address, then sign in to WordPress and approve.
  7. Config-file clients: create a token under Access and use it as Authorization: Bearer <token>.
  8. Choose what the assistant may do under Permissions.
The short /mcp address needs pretty permalinks (Settings → Permalinks set to anything but "Plain"). Without them the Setup tab shows the longer REST address instead, ending in ?rest_route=/gripmcp/v1/rpc, which works with any permalink setting.

升级注意事项:

1.0.1 Security release: fixes the upload page's file name check and two access token issues. Please update.

常见问题:

Which assistants work with GripMCP?

Any MCP client that supports the Streamable HTTP transport. Claude connects with one click through a custom connector. Clients that read a config file connect with an access token.

Is it safe?

Every tool call runs as a WordPress user and is checked against that user's capabilities, exactly as wp-admin would check them. For the tightest control, connect as a dedicated user with a limited role, and keep "Destructive actions" on "Ask me first" (the default) or set it to "Off".

Does it send my data anywhere?

Only if you choose to. Usage data goes to Freemius only if you opt in after activation, and Freemius is otherwise contacted only when you open the Upgrade page, buy a plan or send deactivation feedback. The other services listed under "External services" are contacted only when your assistant asks for that action.

What is in the free plugin, and what do the paid plans add?

The free plugin (the Explorer plan) covers everyday site care: content, media, categories, menus, comments, custom fields, the list of users, reading WordPress's settings, revisions, approvals for deletes, the debug log, site health and read-only plugin abilities. No plan limits access tokens or connected apps. The paid plans are a separate plugin with more tools for developers, agencies and stores, sold at gripmcp.com, where the pricing page compares them. Each paid licence covers a set number of sites.

How do I move from a paid plan back to the free plugin?

You don't have to: when a licence ends, the paid version keeps running with the free plugin's features. To switch to this free plugin, for its updates from WordPress.org, install and activate it first (if WordPress offers to replace the copy you have, accept), and only then delete the paid copy if it is still listed. Your settings, connected apps and activity log carry over. Deleting GripMCP while no other copy is installed removes all of them, and your assistant then has to connect again; your site's content is never touched.

What does it store on my site?

Its settings, hashed access tokens, OAuth clients and tokens, an activity log of tool calls (time, tool, user, result, duration and IP address: kept 3 days on the free plan, 7 on Creator and 90 on Operator and Fleet, and up to 30 days longer after a licence lapses), a connection log, page-builder restore points, approval requests while they wait, the progress cards' steps (kept 7 days), images uploaded through the chat until they are added (2 hours at most), and a short list of recent PHP fatal errors. Deleting the plugin from the Plugins screen removes all of it.

Does it require HTTPS?

Yes, by default. On a site that is not served over HTTPS, the Setup tab shows a "Require HTTPS" switch you can turn off for testing, but tokens sent over plain HTTP can be intercepted.

One-click connect does not work. What should I check?

Open GripMCP → Activity → Connection diagnostics. It lists every token issued and every refused request with the reason. One-click connect needs HTTPS and a site at the root of its domain, because the discovery documents must sit at /.well-known/. If a security plugin blocks .well-known paths, allow them. Sites in a subdirectory can connect with an access token instead.

My host strips the Authorization header.

Some Apache and LiteSpeed setups drop it before PHP sees it, and then every app is refused. When you open the GripMCP screen, your browser sends the site a test request with the header, the way WordPress's own Site Health checks it, and the Setup tab warns you if it does not get through. To fix it, add this to the very top of .htaccess: RewriteEngine On RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]

My site already uses the /mcp address.

Change GripMCP's short address by adding define( 'GRIPMCP_SHORT_PATH', 'ai' ); to wp-config.php (any single word works), or set it to an empty string to turn the short address off and use the longer REST address. Then copy the new address from the Setup tab into your assistant.

How do I report a problem?

Open GripMCP → Activity → Report a problem and describe what you were trying to do and what happened. GripMCP writes a post around your description and adds what is needed to look into it: your WordPress, PHP and plugin versions, your GripMCP settings, what it noticed in its own logs, and the error lines from your site's PHP error logs. With the free plugin, support is on the GripMCP forum here on WordPress.org: click Copy post, then Open the forum, and paste it into a new topic with the title shown above it. Forum posts are public, so read it first and remove anything you would rather keep private; GripMCP leaves your site address out of it. On a paid plan, GripMCP writes an email instead: click Copy email, paste it into a new email to support@gripmcp.com with the subject shown above it, and send it, or download it as a file and attach it. Settings that stop every app from connecting, such as a switched-off endpoint, are shown on the GripMCP screen next to their fix, so you may not need to write in at all. The report is written to leave out passwords, tokens, email and IP addresses, phone numbers, server folder names and your content, but read it before you send it. The plugin never sends it: only you do.

Which versions of WordPress and PHP does it support?

WordPress 6.2 or later, tested up to 7.1. PHP 7.4 or later, tested up to 8.5.

更新日志:

1.0.1 1.0.0