Docs
← Back to site

Connecting Claude to Your Docs (MCP)Beta

15 min readUpdated November 21, 2026
Beta

Connecting Claude is new in 1.0.13 and labelled Beta while it gets real-world use. If something doesn’t work, run Test connection on the settings card and send us the report.

WP Super Docs has a built-in MCP server. MCP (Model Context Protocol) is the standard way AI apps connect to outside tools. Once it’s on, you connect Claude by pasting one address, logging in to your site and clicking Approve. There are no passwords to copy and no files to edit.

What Claude can do#

Once connected, Claude can:

  • Search docs and read any doc, including its images and any screenshot placeholders.
  • List your products, categories and docs, so it knows where a new doc belongs, and find docs that have no product or no category yet.
  • Create new docs, written in Markdown. They’re drafts unless you turn on publishing (see below).
  • Update existing docs: rewrite them, make small exact edits, or add a section. Claude can also change every setting of a doc: its product, category, tags, version, version group, address (slug), order, excerpt, status badge, Internal only, whether it’s in the sitemap, its AI summary and its review status.
  • Check a doc before saving it: missing images, videos and snippets, links to docs that don’t exist or aren’t published, code blocks without a language, skipped heading levels and leftover placeholders.
  • Fill in each doc’s SEO title and description, in whichever SEO plugin your site uses.
  • Translate docs on WPML and Polylang sites, linked to the original.
  • Create and edit categories and products: name, description, SEO, icon, sidebar position and Internal only, a product’s image and its group on the docs homepage, and a category’s OpenAPI spec. Read and change a product’s sidebar order.
  • Set share images for the docs homepage, products, categories and the other pages WP Super Docs creates.
  • Write product changelog entries (release notes), and list what changed since the last release before you write them.
  • Manage the roadmap: add items, change their status, write the team response, link the changelog entry and docs that cover an item, and merge duplicate feature requests.
  • Use reusable snippets in docs, and create new ones.
  • Manage your downloads (with Downloads turned on): add and change them, host a file on your site, put downloads in a doc, and see how often each was downloaded and where it’s shown. See Downloads.
  • Share a draft: create a preview link so someone without a login can read a doc for 7, 30 or 90 days, and turn the link off again.
  • Read and change the announcement bar above every docs page.
  • Keep the Third-Party Services registry up to date.
  • Create docs from a category’s OpenAPI spec, with OpenAPI support turned on.
  • Put Bunny Stream videos in a doc, with Nahnu Video for Bunny Stream active.
  • Ask for an outdated doc to be retired. A person approves or keeps it.
  • Report what needs attention: searches that found nothing, docs readers rated unhelpful, stale docs and broken links.
  • Upload images from a web address, a file on your computer, or SVG diagram code, up to 25 at once.
  • Place an image into a doc, replacing a placeholder or after a heading, and set a doc’s featured image.
  • Keep screenshots current: an image uploaded with a screenshot key can be replaced later, and every doc that uses it updates.
  • Take screenshots of your site’s front end, logged out or as a member, if you turn on Screenshots of your site.
  • Set up the docs home (/docs/) of a site with more than one product: its layout, search, start steps and help box, each product’s card, and the product groups and card order.
  • Delete images that nothing uses anymore, such as replaced screenshots, if you turn on Let Claude delete images that nothing uses, like old screenshots. Claude asks you first.

See Writing and Illustrating Docs with Claude for how these work in practice.

Claude works as you#

Claude works as the WordPress account that approved the connection, and can only do what that account can do in wp-admin:

  • An Author can create docs, edit their own and upload images.
  • An Editor can edit anyone’s docs.
  • A Contributor can create drafts but can’t upload images, so the image tools aren’t offered.
  • Accounts that can’t edit docs, such as Subscribers, can’t connect.
  • Only Administrators can see what visitors searched for and their feedback comments, the same as on the Search Analytics and Feedback screens.
  • Only Editors and Administrators can work with the roadmap, the same as on the Roadmap screen.
  • Only Administrators can create categories and products, edit their settings, change the sidebar order, set share images, change the announcement bar, create docs from an OpenAPI spec and create screenshot links, the same as on those admin screens.
  • Uploading a file for a download needs an account that can upload files, as in the Media Library.

Everything Claude does is recorded under that account like any other edit. Whatever the account’s role, content from Claude is filtered the way WordPress filters an Author’s posts: scripts, embedded frames and event handlers are removed. Claude can be influenced by text it reads, so it never gets to add code to your pages, even when connected as an Administrator.

Turning it on#

The Connect Claude (MCP) card with the server turned on, the publishing options and the 3 connection steps.

Go to WP Super Docs → Settings → Discoverability → Integrations and find Connect Claude (MCP) at the top.

  1. Turn on Turn on the MCP server.
  2. Choose what happens when Claude changes a published doc: Save it as a proposed update for someone to review (the default), so the live doc doesn’t change until a person publishes the update, or Publish the change right away, with WordPress keeping the previous version as a revision so it can be restored.
  3. Under Publishing, choose whether to Let Claude publish docs and changelog entries when you ask it to. It’s off by default: Claude saves new docs and changelog entries as drafts, and a person publishes them. When it’s on, Claude can also publish drafts and proposed updates, but only if its WordPress account is allowed to publish. A Contributor still can’t.
  4. Click Save.

The publishing choices also cover the other things Claude can change that visitors already see: published roadmap items, snippets, downloads and services, the announcement bar, the sidebar order, category and product settings, and docs made from an OpenAPI spec that are already published. Claude can change those only when Let Claude publish is on, or when changes to published docs go live right away. Otherwise Claude says it can’t and leaves them as they are.

The card also has Screenshots of your site, which lets Claude take screenshots of your front end, logged out or as a member. See Screenshots of Your Site with Claude.

See Writing and Illustrating Docs with Claude for how proposed updates are reviewed.

Connecting Claude in 3 steps#

The approval screen: Claude wants to connect, which account it works as, what it can do, and the Approve and Cancel buttons.

Once the server is on, the card shows Connect Claude in 3 steps with your server address.

  1. Click Copy next to the address.
  2. In Claude, open Customize → Connectors, click +, then Add custom connector. Give it a name, such as your site’s name, paste the address and click Add.
  3. Click Connect. Your site opens in the browser. Log in if asked, check the details, and click Approve.

The approval screen shows which app is connecting, which account it will work as, what it will be able to do, and where your browser goes next. Only approve a connection you started yourself.

This works in Claude on the web, desktop and mobile apps. On Team and Enterprise plans, an Owner adds the connector once under Organization settings → Connectors, and then each person clicks Connect and approves with their own WordPress account.

Claude Code: run the command shown on the card, then type /mcp in Claude Code and choose the server to sign in:

claude mcp add --transport http wp-super-docs https://example.com/wp-json/wpsd/v1/mcp

Before you connect#

  • Your site must be on HTTPS and reachable from the internet. Claude connects from Anthropic’s servers, so a site on your own computer or behind a password can’t be reached. Use the application password method below for those.
  • Permalinks can’t be set to Plain. Connecting needs clean web addresses. Choose any other option under Settings → Permalinks. The card warns you if this is the problem.
  • Using Bunny.net with Nahnu Cache Connector? Nothing to set up. While the MCP server is on, WP Super Docs asks the connector to let Claude’s connection skip Bunny Shield’s challenge, its WAF and the CDN cache. Only the connection’s own addresses are covered (the MCP server, its sign-in pages, upload links and sign-in discovery), and each of those checks its own sign-in. The card shows when the Bunny rules are live; the connector sends them within about 5 minutes, or click Update Bunny now.

Connected apps#

The Connected apps list with Claude, the account it works as, when it connected and a Disconnect button.

The card lists every connected app with the account it works as, when it connected and when it was last used. Click Disconnect to end a connection immediately. Administrators see everyone’s connections. Other users see their own on their Profile page, under Apps connected to your docs.

A connection also ends automatically when the account’s password changes, when the account is deleted, or when the MCP server is turned off (turning it back on doesn’t bring old connections back). If a connection isn’t used for 60 days, it has to be approved again.

Setting up the docs home with Claude#

On a site with more than one product, Claude can set up the whole /docs/ page for you, the same settings as Settings → Display → Docs home. Ask it, for example, to group your products by who they are for and give each card a short line. Claude puts the products in groups, fills in each product’s card (a short line about who it is for, a color, an icon and the doc its button opens), then sets the layout, search, start steps and help box. Changes go live at once, so Claude only does this when Let Claude publish is on. If Screenshots of your site is on, Claude can also look at the result. See Setting Up the Docs Home.

Cleaning up old images#

When you replace screenshots, the old files stay in the Media Library. Under Images on the card, turn on Let Claude delete images that nothing uses, like old screenshots and click Save. It’s off by default.

  • Claude can only delete an image that nothing shows anymore: no doc, page or post, featured image, product or category, docs home, share image, logo or other setting.
  • Claude first lists what it would delete and asks you. Only after you agree does it delete, up to 25 images at a time. An image that is still in use is kept, and Claude tells you where it’s used.
  • Only images can be deleted, and only by an account that is allowed to delete them in the Media Library.
  • Deleting is permanent: the file is removed from the Media Library.

How the MCP server protects your site#

The MCP server’s addresses are public, so bots find and try them. WP Super Docs guards them without an allow list of IP addresses, so Claude keeps working wherever it connects from:

  • Off means gone. While the MCP server is off, its addresses don’t exist. They answer “not found” before the rest of WordPress loads and aren’t listed in the REST API index.
  • Failed sign-ins. An address with 10 failed sign-ins within 15 minutes is blocked for an hour. This counts wrong access tokens, wrong application passwords, wrong sign-in codes, wrong refresh tokens and wrong upload links.
  • Floods. More than 60 requests a minute from one address without sign-in blocks that address for 15 minutes. A connected account can send up to 240 requests a minute.
  • Refused early. Requests from a blocked address, with the wrong method or larger than allowed are refused before the rest of WordPress loads, so they cost your server almost nothing.
  • Claude is never locked out. Anthropic’s own addresses are never blocked. Failures from them are only logged.
  • The real address behind a CDN. Behind Cloudflare or Bunny.net, the visitor’s real address is used. Forwarded addresses are only trusted when the request really comes from the CDN, so an attacker can’t fake one.
The Protection panel: failed sign-ins and blocked addresses in the last 7 days, and recent events with shortened addresses.

Administrators see this under Protection on the card: failed sign-ins and blocked addresses in the last 7 days, and the recent events. Addresses are shortened, and blocks end on their own.

On Bunny.net you keep the WAF on: with Nahnu Cache Connector, only the connection’s own addresses skip it, and each of those still checks its own sign-in.

Advanced: connect with an application password#

For a local or password-protected site that Claude can’t reach, or for an MCP client without sign-in support, open Advanced: connect with an application password on the card.

  1. Open Users → Profile for the account Claude should use, scroll to Application Passwords, give it a name such as “Claude”, and click Add New Application Password. Copy the password: it’s only shown once.
  2. Encode username:application-password in base64, for example in a terminal: echo -n "editor:abcd efgh ijkl mnop qrst uvwx" | base64
  3. Use the Claude Code or Claude Desktop snippet from the card, with your encoded value in place of BASE64_OF_USERNAME:APPLICATION_PASSWORD. Claude Desktop reaches the server through the small mcp-remote helper, which needs Node.js installed on your computer. Restart Claude Desktop after saving its config.

Also available as WordPress abilities#

On WordPress 6.9 and later, the same tools are also registered with WordPress’s own Abilities API, under the “WP Super Docs” category. If you already use WordPress’s official MCP Adapter plugin, it can expose them too. You don’t need it to use the built-in server.

Troubleshooting#

Test connection results: three /.well-known/ addresses refused by the web server, with the cause, the fix and the nginx lines.

Start with Test connection on the card (administrators). It tests every address Claude uses twice: over the internet, through any CDN or firewall in front of your site, and directly on your own web server. Answers from WP Super Docs carry a marker, so the test knows for certain whether WordPress answered or something in front of it did, and comparing the two shows who refuses an address. Each problem comes with its cause and fix. Open Details for the status, timing and headers of each request, and Copy report for support for a text version to send to your host or to us; it contains no passwords, tokens or keys.

The This site section of the result names your host when WP Super Docs recognizes it (for example RunCloud, Kinsta, WP Engine, SiteGround or SpinupWP), along with your web server and versions. Include it when you contact your host or us. For how WP Super Docs works with your host’s cache, see Page Caching and Hosting.

Common results:

  • “Your web server itself refuses this address” on the /.well-known/ rows: a server rule or security plugin setting that hides files starting with a dot also blocks the addresses sign-in needs. The result shows the fix for your kind of server, below.
  • On nginx servers, including RunCloud, the result also shows an nginx fix: three lines that rename only WP Super Docs’ own sign-in addresses to ones without a dot, which WP Super Docs also answers. Every other hidden file stays blocked, and other MCP servers on the same site keep their own sign-in addresses. On RunCloud: open the web app, then NGINX Config, then Add a New Config. Choose the type location.main-before, name it wpsd-sign-in, paste the lines, save, and run Test connection again. On other nginx servers the lines go in the site’s server block, before its location blocks; your host can add them.
  • On Apache or LiteSpeed servers, the result shows an Apache / LiteSpeed fix instead: the same renames as .htaccess lines. Put them at the very top of the .htaccess file in your site’s root folder (use your host’s file manager or FTP), above any security rules, and run Test connection again. If a security plugin’s “block hidden files” option still refuses the addresses, turn that option off or exempt /.well-known/ in it.
  • On a managed host that runs the web server for you, like Kinsta, WP Engine, GoDaddy, Pantheon or Pressable, you can’t change these rules yourself. The result says so: copy the report with Copy report for support and ask your host’s support to make the change.
  • “The CDN or firewall in front of it is refusing this address”: your server is fine; add an exception in the CDN or firewall. Its blocked-request log names the rule.
  • “The Authorization header never reached it”: your web server, host or CDN removes the header that carries Claude’s sign-in token. The result tells you which fix applies. On Apache or LiteSpeed, go to Settings → Permalinks and click Save Changes, so WordPress rewrites its .htaccess rules, which pass this header on; if that isn’t enough, add this line at the top of .htaccess: SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1. On nginx, the site’s PHP settings need fastcgi_param HTTP_AUTHORIZATION $http_authorization;, which your host can add. On a managed host, send their support the copied report.
  • “Couldn’t register with … sign-in service”: Claude couldn’t reach the sign-in service. Usually a firewall or CDN in front of the site blocked Claude’s request; Test connection shows whether the answer came from WordPress or from something in front of it. Check the firewall’s blocked-request log for addresses starting with /wp-json/wpsd/v1/ or /.well-known/. On Bunny.net with Nahnu Cache Connector, make sure the card says the Bunny rules are live.
  • Claude says it couldn’t reach the server: check that the site is on HTTPS and publicly reachable, and that the server is turned on. Firewalls or security plugins that block unknown visitors can also stop Claude.
  • Connected, but every request fails: a plugin that adds JWT or token login to the WordPress REST API may reject tokens it doesn’t recognize. Check its settings for a way to ignore requests to /wp-json/wpsd/v1/mcp.
  • The approval screen says the app couldn’t be identified: start the connection again from Claude rather than reusing an old link.
  • “Your WordPress account can’t edit docs”: you’re logged in as an account without editing rights. Use Log in with another account on that screen.
  • Connected, but a tool is missing: the account doesn’t have the permission it needs, for example a Contributor can’t upload images.
  • Application password method gets a 401 error: the username or password is wrong, or your host strips the Authorization header before WordPress sees it. Your host can confirm and fix this.
  • Another MCP server on the same site stopped connecting after you added the nginx fix: you have the lines from before 1.0.14. Replace them with the new ones (see below).

The nginx fix lines#

nginx fix lines shown by Test connection

For a standard WordPress install, the lines look like this. Copy yours from Test connection, since they follow your site’s addresses.

# WP Super Docs: let Claude's sign-in discovery reach WordPress (only WP Super Docs' own addresses).
rewrite ^/\.well-known/(oauth-protected-resource)(/wp-json/wpsd/v1/mcp)/?$ /wpsd-well-known/$1$2 last;
rewrite ^/\.well-known/(oauth-authorization-server|openid-configuration)(/wp-json/wpsd/v1/oauth)/?$ /wpsd-well-known/$1$2 last;
rewrite ^(/wp-json/wpsd/v1/oauth)/\.well-known/(openid-configuration|oauth-authorization-server)$ /wpsd-well-known/$2$1 last;

Added the lines before version 1.0.14? Replace them with the new ones from Test connection. On RunCloud, edit the wpsd-sign-in config, replace its contents and save. The earlier lines also caught other plugins’ sign-in addresses, so other MCP servers on the same site couldn’t connect.

The Apache and LiteSpeed fix lines#

For a standard WordPress install, the .htaccess lines look like this. Copy yours from Test connection, since they follow your site’s addresses.

# BEGIN WP Super Docs sign-in (only WP Super Docs' own addresses)
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^\.well-known/(oauth-protected-resource)/(wp-json/wpsd/v1/mcp)/?$ /wpsd-well-known/$1/$2 [L]
RewriteRule ^\.well-known/(oauth-authorization-server|openid-configuration)/(wp-json/wpsd/v1/oauth)/?$ /wpsd-well-known/$1/$2 [L]
RewriteRule ^(wp-json/wpsd/v1/oauth)/\.well-known/(openid-configuration|oauth-authorization-server)$ /wpsd-well-known/$2/$1 [L]
</IfModule>
# END WP Super Docs sign-in

Was this helpful?

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only