Skip to content Skip to navigation

Connect AI assistants to your WordPress site with the SEOPress MCP server

Since version 10.3, SEOPress includes a built-in MCP server. MCP (Model Context Protocol) is the open standard AI assistants use to talk to external tools. Once your site is connected, Claude, ChatGPT, Cursor or any other MCP client can read and manage your SEO data directly from a conversation: titles, meta descriptions, robots directives, social metadata, content analysis, redirections, structured data and more. Since SEOPress 10.4, this also covers your taxonomy terms: categories, tags, product categories and custom taxonomies.

The MCP server ships in SEOPress Free. SEOPress PRO adds its own tools on top. There is no extra plugin to install, no third-party service in the middle, and no API key to pay for: the AI client talks directly to your site.

What you can do with it

A few prompts you can type in your AI client once the site is connected:

  • “List the pages that have no meta description and write one for each of them.”
  • “Which posts are set to noindex? Tell me if any of them looks like a mistake.”
  • “Run the content analysis on post 123 for the keyword ‘wordpress seo’ and tell me what to fix.”
  • “Rewrite the SEO titles of my 10 latest posts so they stay under 60 characters.”
  • “List the product categories that have no meta description and write one for each of them.” (SEOPress 10.4)
  • “Create a 301 redirection from /old-page/ to /new-page/.” (SEOPress PRO)
  • “Run the technical audit of the site and summarize the issues by priority.” (SEOPress PRO)

The assistant picks the right tools by itself. You stay in control of what it is allowed to do, as explained below.

Requirements

  • SEOPress 10.3 or later (SEOPress PRO 10.3 or later for the PRO tools). The taxonomy term tools need SEOPress 10.4, and the AI suggestions for terms SEOPress PRO 10.4.
  • WordPress 6.9 or later. The MCP server is built on the WordPress Abilities API, which ships with WordPress 6.9.
  • A site served over HTTPS. Clients that run in the cloud (claude.ai, chatgpt.com) need a public HTTPS address to reach your site.
  • A WordPress user account with the capabilities matching what you want the assistant to do.

Local sites (localhost, 127.0.0.1, *.localhost) work without HTTPS with the clients that run on your own machine: Claude Code, the Claude desktop app and Cursor. claude.ai and chatgpt.com run on their own servers and cannot see a local site.

Step 1: enable the MCP server

The MCP server is off by default. Nothing is exposed until you turn it on.

  1. Go to SEO > Advanced, Advanced tab.
  2. In the Abilities API section, turn on Expose abilities to AI agents and external tools.
  3. Click Save changes.
  4. Open the MCP tab of the same page.

The MCP tab shows everything you need: the state of the connection, the readiness checks, the MCP server URL, the instructions for each client, a troubleshooting section, the connected clients and the list of tools.

Since SEOPress 10.4, you can also open it from the SEO dashboard (SEO > Dashboard). In the SEO modules section, the Technical group has an MCP Server card: “Manage your SEO from your AI assistant: Claude, ChatGPT, Cursor or any MCP client.” Its Settings link opens the MCP tab. Unlike most modules, this card has no on/off toggle: the server is switched on and off by the Expose abilities to AI agents and external tools setting above.

Your MCP server URL looks like this:

https://example.com/wp-json/seopress/mcp/v1

If your permalinks are set to Plain, the URL uses the query string form (https://example.com/?rest_route=/seopress/mcp/v1). It works too: copy it exactly as the MCP tab shows it.

Step 2: connect your AI client

In the Connection section of the MCP tab, choose your client: Claude, ChatGPT or Cursor. Each one is set up differently, so only the instructions for the one you choose are shown. Since SEOPress 10.4, each client also has a How it signs in: line that says what it needs from your site.

When your site can run OAuth, every client signs in that way. You paste the URL, your browser opens your own site, you log in to WordPress and approve the connection. There is no password or API key to create or to copy. If your site cannot run OAuth, the Claude and Cursor tabs switch to an Application Password by themselves: see When your site cannot use OAuth below.

Claude (claude.ai, desktop app, Claude Code)

Claude comes as a chat app, on claude.ai or installed on your computer, and as Claude Code in a terminal. Since SEOPress 10.4, the Claude tab has one block for each: follow the one for the app you use. claude.ai and the desktop app’s Connectors screen connect from Anthropic’s servers, so your site needs a public HTTPS address for them. Claude Code signs in from your own machine.

claude.ai and the Claude desktop app

  1. Open Settings > Connectors, then Add custom connector.
  2. Paste your MCP server URL. Leave every other field empty: your site registers the client by itself and tells it where to sign in.
  3. Your browser is sent to your site. Log in to WordPress if needed, then approve the connection.

Claude Code (terminal)

Run the command shown in the MCP tab in a terminal. It looks like this:

claude mcp add --transport http --scope user SEOPress "https://example.com/wp-json/seopress/mcp/v1"

Then start Claude Code, type /mcp, choose SEOPress and sign in to your site in the browser window it opens.

ChatGPT

ChatGPT signs in over OAuth only: an Application Password cannot be used. chatgpt.com connects from OpenAI’s servers, so it needs your site on a public HTTPS address. Since SEOPress 10.4, the ChatGPT tab gives separate steps for the desktop app and for chatgpt.com.

The ChatGPT desktop app

  1. Open Settings, then Plugins under Integrations. Click Add and choose Add MCP server.
  2. Give it a name, choose the Streamable HTTP type, paste your MCP server URL and save. Leave the bearer token and header fields empty: your site signs the connection in over OAuth by itself.
  3. Click Authenticate next to the server, log in to your site and approve the connection.

chatgpt.com

  1. Custom MCP servers only show up in developer mode. Open Settings and turn on Developer mode in the security and login section.
  2. From the Plugins page, open the form that creates a custom plugin: depending on your account, a + button, or Browse directory then Add.
  3. Fill it in with a name and your MCP server URL as the server URL, keep OAuth as the authentication, confirm the risk notice, and create it.
  4. Log in to your site when your browser is sent there, and approve the connection.

Cursor

Cursor reads its MCP servers from a JSON file you edit yourself. It signs you in over OAuth the first time it uses the server, so there is nothing to create beforehand.

  1. Open or create .cursor/mcp.json (this project only) or ~/.cursor/mcp.json (every project).
  2. Add the SEOPress server below. If the file already has an mcpServers object, add the SEOPress entry inside it instead of replacing the file.
{
    "mcpServers": {
        "SEOPress": {
            "type": "http",
            "url": "https://example.com/wp-json/seopress/mcp/v1"
        }
    }
}

Then restart Cursor, open Settings > Customize > MCPs, click Authenticate next to SEOPress and approve the connection.

When your site cannot use OAuth

OAuth cannot run when the site is not served over HTTPS (local sites excepted), when the OAuth server is switched off, or when your host answers the /.well-known/ discovery addresses itself instead of passing them to WordPress. Since SEOPress 10.4, the MCP tab takes the result of the readiness checks into account and adapts the client tabs:

  • ChatGPT, claude.ai and the Connectors screen of the Claude desktop app cannot connect. Their tab says which part is missing and what to fix.
  • Claude Code, the Claude desktop app and Cursor still work: they run on your own machine and send a WordPress Application Password instead. The Claude and Cursor tabs then show the configurations for this method.

Create the Application Password

In the Claude or Cursor tab, give the password a Name (SEOPress MCP by default, the name it is listed under on your profile) and click Create an Application Password. WordPress creates it for your account, and the configurations of the tab fill themselves in with it: nothing is left to replace. The password is shown once and SEOPress never stores it: copy what you need before you reload the page.

Already created an Application Password from your profile? Until you create one in the tab, the configurations carry the placeholder BASE64_OF_USERNAME_COLON_APPLICATION_PASSWORD. The tab gives a command that asks for your password and prints the Base64 to paste in its place. On macOS or Linux, run it in a terminal (the tab writes your own user name in place of USERNAME):

read -rsp 'Application password: ' SEOPRESS_PW && printf '%s' "USERNAME:$SEOPRESS_PW" | base64 && unset SEOPRESS_PW

On Windows, run this one in PowerShell instead:

$pw = Read-Host 'Application password' -AsSecureString; [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('USERNAME:' + [Net.NetworkCredential]::new('', $pw).Password)); Remove-Variable pw

Claude desktop app

The desktop app’s configuration file only starts servers on your own machine, so it reaches your site through mcp-remote, a small bridge that needs Node.js.

  1. Install Node.js (the LTS version from nodejs.org) if your computer does not have it yet. The bridge runs with npx, which comes with it.
  2. In the desktop app, open Settings, then Developer, and click Edit Config. On macOS, Settings is in the Claude menu; on Windows, in the menu at the top left of the window, under File. It shows you claude_desktop_config.json: open it in a text editor. The file is in ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows and ~/.config/Claude/ on Linux.
  3. Paste the configuration from the MCP tab into it. If the file already has an mcpServers object, add the SEOPress entry inside it instead of replacing the file.
  4. Quit the app completely, then open it again: closing its window leaves it running. On macOS, choose Quit Claude in the Claude menu. On Windows, right-click the Claude icon in the system tray, next to the clock, and choose Quit.
  5. Open Settings > Developer again: SEOPress should be listed as running. If it shows an error instead, its log, opened from there, says why.

The configuration looks like this:

{
    "mcpServers": {
        "SEOPress": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://example.com/wp-json/seopress/mcp/v1",
                "--header",
                "Authorization:${AUTH_HEADER}"
            ],
            "env": {
                "AUTH_HEADER": "Basic BASE64_OF_USERNAME_COLON_APPLICATION_PASSWORD"
            }
        }
    }
}

Claude Code (terminal)

Claude Code sends the Application Password itself, so it needs no bridge. Run the command shown in the MCP tab:

claude mcp add --transport http --scope user SEOPress "https://example.com/wp-json/seopress/mcp/v1" --header "Authorization: Basic BASE64_OF_USERNAME_COLON_APPLICATION_PASSWORD"

Then start Claude Code and type /mcp: SEOPress should be listed as connected.

Cursor

Paste the configuration from the Cursor tab into .cursor/mcp.json or ~/.cursor/mcp.json, as above. It carries the password in a header:

{
    "mcpServers": {
        "SEOPress": {
            "type": "http",
            "url": "https://example.com/wp-json/seopress/mcp/v1",
            "headers": {
                "Authorization": "Basic BASE64_OF_USERNAME_COLON_APPLICATION_PASSWORD"
            }
        }
    }
}

Restart Cursor and open Settings > Customize > MCPs: SEOPress should be listed with its tools.

Other MCP clients

Any client that supports the Streamable HTTP transport can connect. If it supports OAuth, give it the MCP server URL and it will find the sign-in page by itself.

If it does not, you can authenticate with a WordPress Application Password sent in a Basic Authorization header, as in the Cursor configuration above:

{
    "mcpServers": {
        "SEOPress": {
            "type": "http",
            "url": "https://example.com/wp-json/seopress/mcp/v1",
            "headers": {
                "Authorization": "Basic BASE64_OF_USERNAME_COLON_APPLICATION_PASSWORD"
            }
        }
    }
}

The header carries Basic, a space, then the Base64 of your user name, a colon and the Application Password. The Base64 commands above print that value for you.

The approval screen: read only, or read and change

When a client connects over OAuth, your site displays an approval screen. It shows which client is asking, which WordPress account it will act as, and the list of tools it will get. You then choose what the connection may do:

  • Read and change: every tool is available.
  • Read only: only the tools that read data are served. The tools that change data are not shown to this connection, and are refused if the client asks for one by name.

Click Allow this connection to finish, or Refuse to cancel.

The client chooses its own name when it registers, and nothing can verify it. Only approve a connection you have just started yourself.

Step 3: check that it works

Ask your assistant which tools it has. It should list the tools shown in the Exposed tools section of the MCP tab.

If nothing appears, open the Diagnostics panel at the top of the MCP tab and click Run the readiness checks. Every amber or red line says what to change on your site. Since SEOPress 10.4, a blue line means the result is expected for the way your site is set up, and there is nothing to fix.

Available tools

Tool names are prefixed with seopress__. For instance, the ability seopress/get-post-title-description is served as the tool seopress__get-post-title-description.

SEOPress Free

Tool What it does Access Who can use it
get-post-title-description Reads the custom SEO title and meta description of a post Reads only Users who can edit the post
update-post-title-description Sets or clears the SEO title and meta description of a post Can change data Users who can edit the post, if their role is not blocked from the SEO metaboxes
get-post-robots-settings Reads the robots directives of a post (noindex, nofollow, canonical URL, primary category…) Reads only Users who can edit the post
update-post-robots-settings Updates the robots directives of a post Can change data Users who can edit the post, if their role is not blocked from the SEO metaboxes
get-post-social-settings Reads the Facebook/Open Graph and X/Twitter metadata of a post Reads only Users who can edit the post
update-post-social-settings Updates the Facebook/Open Graph and X/Twitter metadata of a post Can change data Users who can edit the post, if their role is not blocked from the SEO metaboxes
analyze-post-content Runs the content analysis on a post and returns the score, checks and recommendations Reads only Users who can edit the post
list-posts-missing-metadata Lists the posts with no custom SEO title and/or meta description Reads only Users who can edit posts
list-posts-by-content-score Lists posts with the verdict of their last content analysis Reads only Users who can edit posts
list-posts-noindexed Lists the posts carrying an explicit noindex directive Reads only Users who can edit posts
get-term-title-description Reads the custom SEO title and meta description of a taxonomy term (category, tag, product category…). Since 10.4 Reads only Users who can edit the term
update-term-title-description Sets or clears the SEO title and meta description of a taxonomy term. Since 10.4 Can change data Users who can edit the term, if their role is not blocked from the SEO metaboxes
get-term-robots-settings Reads the robots directives of a taxonomy term (noindex, nofollow, nosnippet, noimageindex, canonical URL). Since 10.4 Reads only Users who can edit the term
update-term-robots-settings Updates the robots directives of a taxonomy term. A directive forced on by the global settings is not written. Since 10.4 Can change data Users who can edit the term, if their role is not blocked from the SEO metaboxes
get-term-social-settings Reads the Facebook/Open Graph and X/Twitter title, description and image of a taxonomy term. Since 10.4 Reads only Users who can edit the term
update-term-social-settings Updates the Facebook/Open Graph and X/Twitter title, description and image of a taxonomy term. Since 10.4 Can change data Users who can edit the term, if their role is not blocked from the SEO metaboxes
list-terms-missing-metadata Lists the taxonomy terms with no custom SEO title and/or meta description. Since 10.4 Reads only Users who can edit the terms of a taxonomy (only those taxonomies are listed)
get-global-titles-settings Reads the site-wide title and meta description templates Reads only Users who can manage the Titles & Metas settings
get-sitemap-settings Reads the XML and HTML sitemap configuration Reads only Users who can manage the XML / HTML Sitemap settings
get-instant-indexing-settings Reads the Instant Indexing configuration and submission log. API keys are never returned Reads only Users who can manage the Instant Indexing settings
get-global-social-settings Reads the Knowledge Graph and default social settings Reads only Users who can manage the Social Networks settings

The term tools work on the public taxonomies whose SEO metabox is enabled. A taxonomy where Disable SEO metabox is checked in SEO > Titles & Metas, Taxonomies tab, is refused.

SEOPress PRO

Tool What it does Access Who can use it
list-redirections Lists the redirections and detected 404s, with pagination, search and filters Reads only Users who can read redirections
get-redirection Reads a single redirection Reads only Users who can read redirections
create-redirection Creates a redirection from an origin URL to a target URL Can change data Users who can publish redirections
update-redirection Updates an existing redirection Can change data Users who can edit the redirection
delete-redirection Permanently deletes a redirection Can change data Users who can delete the redirection
get-post-schemas Reads the manual structured data (schema.org) of a post Reads only Users who can edit the post
update-post-schemas Replaces the manual structured data of a post Can change data Users who can edit the post
update-target-keywords Updates the target keywords of a post Can change data Users who can edit the post
generate-seo-title Generates an SEO title suggestion with AI. The suggestion is not saved Reads only Users who can edit the post, if their role may use AI generation
generate-meta-description Generates a meta description suggestion with AI. The suggestion is not saved Reads only Users who can edit the post, if their role may use AI generation
generate-term-seo-title Generates an SEO title suggestion for a taxonomy term with AI. The suggestion is not saved: save it with update-term-title-description. Since 10.4 Reads only Users who can edit the term, if their role may use AI generation
generate-term-meta-description Generates a meta description suggestion for a taxonomy term with AI. The suggestion is not saved: save it with update-term-title-description. Since 10.4 Reads only Users who can edit the term, if their role may use AI generation
generate-alt-text Generates an alt text and a caption for an image with AI. The suggestion is not saved Reads only Users who can edit the image, if their role may use AI generation
upload-image Downloads an image from a URL and adds it to the Media Library Can change data Users who can upload files (and edit the post, when the image is attached to one)
get-technical-audit Runs the site-wide technical checks and returns a structured checklist Reads only Users who can manage the audit tools of SEOPress PRO

Settings and audit tools are reserved for administrators by default. The five generate-* tools use the AI provider configured in SEOPress PRO.

Since SEOPress 10.4, the MCP tools follow the role restrictions of SEO > Advanced, Security tab, like the WordPress admin does:

  • A role checked under SEO metaboxes: blocked roles cannot use the tools that change the SEO settings of a post or a term. It can still use the tools that read them.
  • With SEOPress PRO, when roles are checked under AI generation, only those roles (and administrators) can use the generate-* tools.

Security and permissions

The MCP server is designed so that connecting an AI client never gives it more power than you already have.

  • Off by default. The endpoint refuses every request until you turn exposure on.
  • Your own permissions, never more. A connection acts as the WordPress account that approved it. Each tool call goes through the same capability checks as the WordPress admin, including the role restrictions of the Security tab. An Editor connected over MCP cannot read SEOPress settings reserved for administrators, and an Author cannot edit somebody else’s posts.
  • Read only connections. Chosen on the approval screen, enforced by the server for the whole life of the connection.
  • SEOPress tools only. The server only serves SEOPress abilities. Abilities registered by other plugins are held back unless you opt in.
  • Tool by tool control. You can switch off any tool for the whole site.
  • No secret leaves your site. API keys stored in SEOPress settings are never returned by a tool. Application Passwords created from the MCP tab go from WordPress to your browser and are never stored or logged by SEOPress.
  • Standard OAuth 2.1. Sign-in uses PKCE, dynamic client registration and tokens bound to your site address. Access tokens last one hour and are renewed automatically. A connection that has not been used for 30 days has to sign in again.
  • Revocable at any time. One click in the MCP tab cuts a client off immediately.

Tools that change data save to your live site, exactly as if you had edited the post yourself. Ask your assistant to show you what it plans to change before it does, and use a read only connection when you only need an audit.

Managing the connection

Connected clients

The Connected clients section of the MCP tab lists every client that holds a token for your account: its name, what it was approved for (reading only, or reading and changing), when it was connected and when it was last used. Click Revoke to cut one off. The effect is immediate.

Each user only sees and revokes their own connections. One account can hold up to 25 connections.

If you change your site address, the connections issued for the old address are marked No longer valid. Revoke them and connect again.

This list only shows OAuth connections. A client that signs in with an Application Password is revoked from your WordPress profile, with the Manage Application Passwords link of the MCP tab.

Choosing which tools are served

The Exposed tools section lists every tool with its access level. Use the Served toggle at the end of a row to switch a tool off, then save. A tool that is switched off is no longer listed to any client and cannot be called, whatever the permissions of the user.

This is useful to keep a sensitive tool to yourself, for example delete-redirection.

Abilities from other plugins

Other plugins can register their own abilities in WordPress. By default, the SEOPress MCP server does not serve them, so that turning on your SEO tools never hands an AI client another plugin’s tools by accident.

To serve them as well, turn on Also serve abilities registered by other plugins in the Exposed tools section. Before you save, the MCP tab lists the tools this would add. Read the list: some of them may change or delete data.

Troubleshooting

The Diagnostics panel runs nine checks and tells you what to fix for each one that fails.

Check If it fails
WordPress Abilities API Update WordPress to 6.9 or later.
Abilities exposed to external clients Turn on Expose abilities to AI agents and external tools in the Advanced tab and save.
MCP route registered Another plugin is removing routes from the WordPress REST API. Allow the /seopress/mcp/v1 route.
MCP endpoint answering A security plugin, a firewall or a CDN is blocking the request, or your host blocks loopback requests. Allow POST requests to the MCP server URL. An HTTP 401 answer is expected here: the check calls the endpoint without credentials.
Application Passwords Only needed for clients that do not sign in over OAuth. WordPress offers them over HTTPS only, and a security plugin can switch them off.
HTTPS Install a TLS certificate and switch the WordPress Address and Site Address to https.
Permalinks A warning only: the URL works in its query string form. Choose any structure other than Plain for a shorter URL.
OAuth for browser clients OAuth needs HTTPS (or a local site). Since SEOPress 10.4, if the OAuth server was switched off on purpose with the seopress_mcp_oauth_enabled filter, this line is blue: that is expected if you connect with an Application Password.
OAuth discovery document Your server does not route /.well-known/ requests to WordPress. Choose a permalink structure other than Plain. If WordPress is installed in a subdirectory, add a rule that forwards /.well-known/ requests to it. Some hosts answer /.well-known/ addresses themselves, before WordPress runs: ask yours to pass /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server through to WordPress. Until then, the Claude and Cursor tabs switch to an Application Password.

When the checks are green but a client fails

The readiness checks call your site from itself, so a firewall or a CDN in front of it never sees them. Since SEOPress 10.4, the MCP tab has a Troubleshooting section, below the connection steps, that starts from the message your client shows:

  • claude.ai or ChatGPT is refused while every check is green (for instance Dynamic client registration failed: registration endpoint returned 403). claude.ai and ChatGPT call your site from their own servers, with no browser, and bot protection treats that as a bot. Allow GET and POST requests to the Registration, Token and MCP server addresses listed in the tab, from any IP address. On Cloudflare, look in Security, Events: if Bot Fight Mode challenged them, turn it off (on the Free plan, a custom WAF rule cannot skip it), or on a paid plan add a WAF rule that skips bot protection for these addresses. Then add the server to your client again.
  • claude.ai or ChatGPT finds the site, then cannot sign in. The client could not read the OAuth discovery documents. Open the two addresses listed in the tab in a browser: both must answer with JSON, not a “not found” page. If they do not, ask your host to pass them through to WordPress.
  • The Claude desktop app does not list the server. Its configuration file only accepts servers it starts itself: an entry with a url is not supported and can make the app drop every server in the file. Use the mcp-remote configuration of the Claude tab, check that Node.js is installed (npx --version prints a version number), quit the app completely and open it again, then read the server’s log in Settings > Developer.
  • Claude Code, the desktop app or Cursor is refused with HTTP 401. The Authorization header is wrong: a placeholder left in the configuration, another account’s user name, or a revoked password. Create a new Application Password in the tab, or run the Base64 command again and paste its output in place of the placeholder.

Other common situations:

  • The client connects but lists no tool. Check the Exposed tools section, and that your WordPress account has the required capabilities.
  • “This connection was approved for reading only”. The connection was approved as read only. Remove it in your client, connect again and choose Read and change.
  • “You do not have permission to use this tool”. Your WordPress account does not have the capability the tool requires, or its role is restricted in the Security tab.
  • The connector fails on the first attempt. Open the two addresses listed under Discovery documents in the Connected clients section. Both must answer with JSON. If they do not, a security plugin, a cache or a server rule is in the way.
  • A caching or security layer in front of the site. Exclude /wp-json/seopress/mcp/ and /.well-known/oauth-* from page caching, and do not strip the Authorization header.
  • Another plugin runs its own MCP server on the same site. Update to SEOPress 10.4 or later. Earlier versions also answered the OAuth discovery requests meant for the other server, so its clients received the SEOPress discovery documents instead of its own. SEOPress now only answers the discovery addresses of its own server, and leaves the others to the plugin they belong to.

For developers

The server implements the MCP Streamable HTTP transport on a single REST route (POST /wp-json/seopress/mcp/v1) and supports the protocol revisions 2025-06-18, 2025-03-26 and 2024-11-05. It exposes tools only (no resources, no prompts).

Every tool is a WordPress ability registered with wp_register_ability() in the seopress namespace. The following filters let you adjust the behavior:

Filter Purpose
seopress_abilities_api_rest_enabled Force exposure on or off, whatever the setting says.
seopress_mcp_read_only Force every connection to read only.
seopress_mcp_disabled_abilities Switch abilities off by name.
seopress_mcp_served_abilities Last word on the list of abilities served to clients.
seopress_mcp_exposed_namespaces Add ability namespaces to serve besides seopress.
seopress_mcp_foreign_namespaces_enabled Serve, or not, the abilities of every other plugin.
seopress_mcp_allowed_origins Origins allowed to reach the endpoint from a browser.
seopress_mcp_oauth_enabled Switch the OAuth server off.
seopress_mcp_oauth_transport_is_secure Tell the OAuth server the site is served securely, for instance behind a TLS terminating proxy.
seopress_remove_feature_mcp Return false to hide the MCP Server card of the SEO dashboard. Since 10.4.

Example: make every MCP connection read only on a production site.

add_filter( 'seopress_mcp_read_only', '__return_true' );

Example: serve the abilities of your own plugin alongside SEOPress.

add_filter( 'seopress_mcp_exposed_namespaces', function ( $namespaces ) {
	$namespaces[] = 'my-plugin';

	return $namespaces;
} );

FAQ

Is the MCP server available in SEOPress Free?

Yes. The server and 21 tools ship in SEOPress Free. SEOPress PRO adds 15 tools (redirections, structured data, target keywords, AI generation for posts, terms and images, image upload, technical audit).

Does SEOPress send my content to an AI provider?

No. SEOPress only answers the requests of the AI client you connected. What your client does with the answers depends on that client and its provider.

Do I need an OpenAI or Anthropic API key?

No. You use your own ChatGPT, Claude or Cursor plan. Only the five generate-* tools of SEOPress PRO rely on the AI provider configured in SEOPress PRO. Note that a ChatGPT or Claude subscription does not include API credits.

Can several users connect their own client?

Yes. Each connection is tied to the WordPress account that approved it and is limited to that account’s permissions.

Does it work on a multisite network?

Each site of the network has its own MCP server URL and its own setting.

How do I turn everything off?

Turn off Expose abilities to AI agents and external tools and save. The endpoint and the OAuth server stop answering immediately.