By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Microsoft Copilot to WordPress is the Ryze AI connector. Microsoft's pages show no Copilot chat window with a field for an MCP address, so the connector goes onto an agent: connect your site in Ryze AI, then on a Copilot Studio agent add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool with OAuth 2.0 and Dynamic discovery, and sign in to Ryze AI. The agent then holds 9 WordPress tools: 2 read, 6 write and 1 delete.
- In Ryze AI open Integrations, click Connect on the WordPress card, and enter the site URL, a username and an application password (or sign in with WordPress.com)
- In Copilot Studio switch to the classic experience, open your agent, then Tools, Add a tool, New tool, Model Context Protocol
- Enter a name, a description and the URL, pick OAuth 2.0 with Dynamic discovery, then select Create and Next
- Create a new connection, sign in to Ryze AI, select Add to agent and ask a content question in the test chat
Microsoft Copilot to WordPress at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that a Copilot Studio agent takes as a tool. A Microsoft 365 Copilot declarative agent can take it as an action, a route not yet confirmed for Ryze AI |
| Server address | https://connector.get-ryze.ai/mcp, the same for every user |
| Where it goes in Copilot | On an agent. Classic experience: Tools > Add a tool > New tool > Model Context Protocol. New experience: Build tab > Tools > Add > Model Context Protocol (MCP). No chat window has a documented field for it |
| Sign-in | Copilot signs in to Ryze AI with OAuth 2.0 and Dynamic discovery. WordPress is joined once inside Ryze AI, with an application password or a WordPress.com sign-in, so no WordPress password is typed into Copilot |
| WordPress tools | 9: 2 read, 6 write and 1 delete |
| Can the agent change the site | Yes, through the write and delete tools, within the role of the connected WordPress user. Deletes sit in their own tool, so they can be approved on their own |
| Other data in the same chat | Other platforms connected in the same Ryze AI workspace, such as Google Search Console, are served by the same URL |
| Copilot plan | Microsoft's MCP pages name none. A trial cannot publish an agent, and the Copilot Studio for Teams plan lacks generative orchestration and Power Platform connectors |
| Ryze AI price | SEO Starter is $129 a month after a 3-day free trial. Adding the connector costs nothing; the WordPress tools need an active plan or trial |
| WordPress's own option for Copilot | A WordPress.com plugin for Microsoft 365 Copilot Cowork, listed on the WordPress.com MCP developer page. It needs a Microsoft 365 Copilot license and possibly approval from a tenant admin |
| Last tested | WordPress reads through the connector on November 14, 2026, from Claude Code, on a WordPress.com connection. No step inside a Microsoft product was run |
Before you start
- A Copilot Studio agent or a Microsoft 365 Copilot declarative agent. This is a builder task, usually done by an agent maker or admin in a work or school tenant. Microsoft says Copilot Studio is open to all Microsoft 365 users for creating agents and actions. A Copilot Studio trial lets you create and test agents but cannot publish them, and Microsoft asks for a work or school account to sign up for it.
- A Copilot Studio plan that carries MCP. Microsoft documents that MCP access in Copilot Studio relies on Power Platform connectors, and its licensing page marks Power Platform connectors and generative orchestration as not available in the Copilot Studio for Teams plan. Whether MCP tools run on the Teams plan is not documented, so test before you promise it to anyone.
- A WordPress user with the right role. On a self-hosted site you need to create an application password: WordPress has shipped them since version 5.6, they are on by default for sites served over HTTPS, and the password acts with its user's own access. Use an administrator if you want plugin installs, the SEO bridges or head code. On a WordPress.com or Jetpack site you sign in on WordPress.com instead, and for a Jetpack site the Jetpack JSON API module must be enabled.
- A site that answers on /wp-json. A security plugin, firewall or host that blocks /wp-json requests stops the connection until requests from Ryze AI are allowed.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial and covers publishing Content Plan articles to the site. Annual billing takes 30% off the first year. Connecting the connector is free, and the WordPress tools need an active plan or trial.
How to connect Copilot Studio to WordPress
Step 1 happens in WordPress and Ryze AI, steps 2 to 6 in Copilot Studio. Every user adds the same connector URL.
Connect your WordPress site in Ryze AI
Self-hosted site: in WordPress admin open Users, then Profile, scroll to Application Passwords, enter a name such as Ryze AI, click Add New Application Password and copy the password, which is shown once. In Ryze AI open Integrations, click Connect on the WordPress card, pick the Self-hosted site tab, enter the Site URL (https://), the username you sign in to wp-admin with and the application password, then click Continue. WordPress.com or Jetpack site: pick the WordPress.com / Jetpack tab instead, sign in on WordPress.com, approve access and choose the site. Do this before you add the connector to Copilot.
Open the agent and start a new MCP tool
These steps are for the classic experience (the standard harness). New agents from the Copilot Studio home page run on the Microsoft Copilot harness, so switch first: select the three dots at the bottom of the home page side bar, then Open classic experience, which lasts for the session, or start the agent from Other ways to build. Open your agent and go to its Tools page. Select Add a tool, then New tool, then Model Context Protocol in the Create new section. The MCP onboarding wizard opens.
Fill in the server details
Server name: Ryze AI. Server description: a plain note on what the tools do, for example Reads and edits WordPress posts, pages, media, categories and tags. Microsoft says the agent orchestrator uses this description to decide when to call the server. Server URL: https://connector.get-ryze.ai/mcp.
Choose OAuth 2.0 with Dynamic discovery
Set the authentication type to OAuth 2.0 and the OAuth type to Dynamic discovery. The Ryze AI server supports dynamic client registration, so no client ID, secret or callback URL is typed. Select Create, then Next.
Create the connection and add the tool
On Add tool, select Create a new connection and complete the Ryze AI sign-in, or pick an existing connection. Microsoft's page stops at that button and does not show the sign-in window, and this step was not run for this guide. Then select Add to agent.
Ask a content question in the test chat
MCP needs generative orchestration, which Microsoft says is on by default. Open the test chat panel and ask: List the content types and taxonomies registered on my WordPress site. If the WordPress tools do not run, check the troubleshooting list below.
The Ryze AI help article for WordPress covers the WordPress side of the connection. Microsoft's page on connecting an agent to an existing MCP server covers the Copilot Studio wizard, and its page on switching experiences shows how to open the classic experience. Checked November 14, 2026.
Microsoft 365 Copilot declarative agent
If your colleagues work in Microsoft 365 Copilot and not in Copilot Studio, the same URL can ride in a declarative agent as an MCP action. Microsoft documents this route in its Agents Toolkit walkthrough.
- Install Visual Studio Code and Microsoft 365 Agents Toolkit version 6.12.0 or later.
- Select the Agents Toolkit icon in the Activity Bar, then Create a New Agent/App, then Declarative Agent.
- Select Add an Action, then Start with an MCP Server, and enter https://connector.get-ryze.ai/mcp.
- Choose OAuth (with dynamic registration) as the authentication type, then pick a project location and an agent name. Microsoft requires the authorization server to hand back a client secret at registration; whether the Ryze AI server does so for Microsoft was not checked.
- In the Accounts pane sign in to Microsoft 365 and look for Custom App Upload Enabled and Copilot Access Enabled. If either is missing, an admin has to allow custom app upload.
- In the Lifecycle pane select Provision, read the dialog, select Confirm and wait until the toolkit reports that provisioning finished.
- Open m365.cloud.microsoft/chat, find the agent in the Agents section of the sidebar (its name ends in dev), ask a content question and select the Sign in button that carries the agent's name.
Microsoft says Agents Toolkit sets a new MCP plugin to dynamic tool discovery, so Copilot reads the server's tool list at run time and you add no tools by hand. Sideloading needs Upload custom apps switched on by an admin in the Teams admin center. The first time the agent uses the plugin, Copilot asks the person to allow or cancel. After that, tools that only read do not ask again, and tools that change data do.
Sources: Build a plugin for a declarative agent from an MCP server, dynamic client registration for plugins, Microsoft 365 Copilot extensibility requirements, plugin overview. Checked November 14, 2026.
New experience, admin connector and personal Copilot
Microsoft documents more places that accept an MCP address than the two above, and WordPress.com has a Copilot plugin of its own. Each changes who does the setup and how sign-in works.
Copilot Studio, new experience
On the Microsoft Copilot harness the server is added from the agent's Build tab: Tools in the components panel on the right, Add beside the search bar, then Model Context Protocol (MCP). The Add MCP server page asks for Name, Description, Server URL and Authentication; select Add, review the tools Copilot Studio lists, then Save. Microsoft labels that how-to page preview, and its Authentication field lists no choices, so the page does not say whether Dynamic discovery is among them. The classic steps above are the documented route for the Ryze AI connector.
Getting the agent in front of colleagues
People reach a Copilot Studio agent from Teams and Microsoft Copilot after it has been published at least once and connected to the Teams and Microsoft Copilot channels. A trial license cannot publish, so a trial agent that holds the WordPress tools lives in the test chat panel only.
Copilot Cowork and the WordPress.com plugin
WordPress.com lists Microsoft 365 Copilot Cowork among the assistants for its own MCP server, and says the WordPress.com plugin comes from the Microsoft 365 App Store, needs a Microsoft 365 Copilot license and may need approval from a tenant admin. That plugin signs in to WordPress.com, so it fits sites on WordPress.com and Jetpack-connected sites. It is a separate product from the Ryze AI connector and was not opened inside Cowork for this guide.
Admin route: a custom federated connector
A Global Administrator or AI Administrator can turn an MCP address into a connector in the Microsoft 365 admin center under Copilot > Connectors > Gallery > Create a new connector > Connect to MCP server. People with a Microsoft 365 Copilot license then connect it in Copilot Chat under Settings > Sources. Its sign-in methods are Microsoft Entra SSO, OAuth 2.0 with a client registered by hand in the Teams Developer Portal, or No Auth. Dynamic registration is not listed, so this route is unconfirmed for Ryze AI.
Copilot with a personal Microsoft account
Copilot on Copilot.com and Copilot Mobile with a personal account has four built-in connectors under Profile > Connectors: OneDrive, Outlook.com, Google Drive, and Gmail with Google Calendar and Contacts. Microsoft's support article does not mention MCP or a way to add your own, so a personal account has no documented place for WordPress through Ryze AI.
Microsoft Copilot and MCP in one table
| Topic | What Microsoft's pages say |
|---|---|
| Where the address is typed | In an agent or in an admin connector. Copilot Studio: the MCP wizard (classic) or the Add MCP server page (new). Microsoft 365 Copilot: a declarative agent action, a custom federated connector, or a plugin package manifest |
| Servers on your own computer | No route accepts a start command. Microsoft 365 Copilot must reach the server over the internet, and Microsoft points to a dev tunnel with a public HTTPS address for local work |
| Transport | Copilot Studio takes Streamable and dropped SSE after August 2025. Plugin packages and Cowork expect Streamable HTTP over HTTPS with TLS 1.2 or later |
| Sign-in, Copilot Studio wizard | None, an API key sent in a header or query parameter you name, or OAuth 2.0 as Dynamic discovery, Dynamic or Manual |
| Sign-in, declarative agent | Microsoft Entra SSO, dynamic client registration, the OAuth 2.0 authorization code flow or none. API keys are unsupported for MCP plugins |
| Whose account a tool uses | In Copilot Studio a tool uses End user credentials by default, so each person signs in; Maker-provided credentials is the other choice |
| Confirmation before a tool runs | Copilot Studio turns on every tool of a new server (Allow all). Declarative agents ask on first use and then before tools that change data |
| Plan and billing | The MCP how-to pages name no plan. Agents on the new experience are billed in Copilot Credits, charged for model tokens, the harness and tools, MCP servers included |
| Where servers are managed | Classic: select the server on the Tools page for Details, Tools, Resources and an Enabled toggle. New: the tools list on the Build tab. Declarative agents: Teams > Apps > Manage your apps |
| Admin controls | A data policy on Power Platform connectors also covers MCP servers. In the Microsoft 365 admin center, Agents > Tools > Registry can block a server, which turns off every tool it exposes |
Sources: adding an MCP server in the new experience, MCP in Copilot Studio, MCP tools and resources on an agent, agent tools and credentials, managing tools in the new experience, Teams and Microsoft Copilot channels, Copilot Credits, Copilot Studio access and browsers, plugin sign-in types, MCP servers in plugin packages, custom federated connectors, federated connector approvals, admin tool registry, Copilot connectors for personal accounts. Checked November 14, 2026.
Other AI clients
The same connector URL works in other MCP clients, and your site stays connected once in Ryze AI. Guides for WordPress:
WordPress access and roles
Two sign-ins are involved, and each limits what the agent can reach.
- WordPress sign-in saved in Ryze AI
- A self-hosted site is joined with its URL, a username and an application password, and the password acts with that user's own role. A WordPress.com or Jetpack site is joined with a WordPress.com sign-in. Nothing from WordPress is typed into Copilot.
- Ryze AI sign-in from Copilot
- The Copilot connection signs in to Ryze AI with OAuth 2.0. In Copilot Studio the tool runs on End user credentials unless the maker changes it, so each person who uses the agent makes a connection of their own. The agent reaches the sites connected in the chosen Ryze AI workspace.
- Which site
- Several WordPress sites can be connected to one workspace with Add one more account. The agent uses the primary site unless you name another one, and the tools accept an optional connection_id. Do not read this as one SEO plan publishing to many sites: the help center does not explain how the two interact.
- Power Platform data policy
- Microsoft notes that a data policy on Power Platform connectors also regulates access to the MCP server and its tools. If a policy blocks the connector, ask your Power Platform admin.
Access behind each action
WordPress has no app scopes for an application password: the connected user's role decides. The table lists what Ryze AI documents for each kind of action.
| Action in Ryze AI | WordPress access needed |
|---|---|
| Read posts, pages, media, categories, tags, users, plugins and custom post types | Any connection, within the connected user's role. Reading plugins needs the activate_plugins capability |
| Create, update and delete posts, pages, media, categories and tags | Any connection, if the user's role allows that change |
| Find and replace text inside one post or page | Any connection, if the user's role may edit that post |
| Yoast SEO or Rank Math title, description, canonical and focus keyword | A self-hosted site, an administrator user and a one-time bridge. Not on WordPress.com connections |
| Head code and plugin installs | A self-hosted site and an administrator user. Not on WordPress.com connections |
Which WordPress user decides what the agent can do
A self-hosted connection has no scopes of its own, so the role of the WordPress user is the limit. The Ryze AI sign-in on a WordPress.com or Jetpack site goes through WordPress.com, and which OAuth scope it asks for is not in Ryze AI's facts, so this page names none.
| Role or key | What WordPress says | With Ryze AI |
|---|---|---|
| Application password (self-hosted) | A 24-character password made on a user's profile, shown once and revocable on its own. It cannot be used to log in at wp-login.php, and it acts with its user's own access | Entered once in Ryze AI with the site URL and username |
| WordPress.com sign-in | WordPress.com OAuth2 serves WordPress.com sites and Jetpack-connected sites alike, and its /wp/v2 routes mirror the core REST API | One-click sign-in. Only core /wp/v2 routes are reachable |
| Administrator | Reaches every administration feature on a single site and holds activate_plugins | Needed for plugin installs, the Yoast and Rank Math bridges and head code |
| Editor | Publishes and manages posts, including other users' posts | Covers content work across authors |
| Author | Publishes and manages their own posts | Covers the user's own posts |
| Contributor | Writes and manages their own posts but cannot publish them | Writes can be refused when they need publish rights |
| Subscriber | Can manage only their own profile | Too low for content work |
Not included: plugin installs, the SEO bridges and head code on WordPress.com connections; plugin routes such as /yoast/v1 there (a read of that route came back as not found in the test); plugins from uploaded zip files or URLs, since only wordpress.org directory plugins can be installed; robots.txt changes; Elementor text where the post type does not expose meta._elementor_data. Yoast and Rank Math fields sent through the plain REST API without the bridge are dropped by WordPress without an error.
Removing access
To take WordPress away from a Copilot Studio agent, open its Tools page in the classic experience, hover over Ryze AI, select the three dots and Delete. To cut off the site at the source, revoke the application password on the user's Edit User page in WordPress, where WordPress lets you view and revoke each one.
Sources: REST API authentication, application passwords guide, roles and capabilities, WordPress.com OAuth2, Jetpack JSON API, Microsoft note on MCP servers and data policies, Ryze AI WordPress integration. Checked November 14, 2026.
What Copilot can do in WordPress
The Ryze AI connector exposes 9 WordPress tools: 2 read, 6 write and 1 delete. Writes and deletes are separate tools, so a Copilot agent can be set up to treat them differently.
| Tool | Type | What it does |
|---|---|---|
| wordpress__read | Read | Runs a read-only (GET) WordPress REST API request on the connected site, covering posts, pages, media, categories, tags, users, plugins and custom post types. |
| wordpress__search_content | Read | Searches a text field such as a post's raw content and returns the matching lines with line numbers and context. |
| wordpress__write | Write | Runs a REST API request that creates or updates resources (POST, PUT or PATCH), such as creating a post or updating a page. |
| wordpress__edit_content | Write | Makes find-and-replace edits to a text field such as content, an excerpt or a title, and writes it back without resending the whole content. |
| wordpress__installPlugin | Write | Installs and activates a plugin from the wordpress.org directory on a self-hosted site. |
| wordpress__enableYoastRestBridge | Write | One-time setup on a self-hosted Yoast SEO site that makes the Yoast title, meta description, focus keyword, canonical and noindex fields writable through the REST API, using a Code Snippets plugin snippet. |
| wordpress__enableRankMathRestBridge | Write | One-time setup on a self-hosted Rank Math site that makes the Rank Math title, description, canonical URL and focus keyword fields writable through the REST API, using a Code Snippets plugin snippet. |
| wordpress__addHeadCode | Write | Adds a block of HTML inside the head of every page on a self-hosted site, such as a tracking snippet, a pixel or a verification tag, through a Code Snippets plugin snippet. |
| wordpress__delete | Delete | Runs a DELETE REST API request, for example to delete a post. |
Some limits apply in every client. Four tools, the plugin install, the two SEO bridges and head code, work only on a self-hosted connection made with an administrator user. A plugin install can crash a WordPress site, so approve each one. WordPress.com connections reach only the core /wp/v2 routes.
In Copilot Studio, a new MCP server arrives with every tool turned on (Allow all), and Microsoft does not describe a confirmation prompt for MCP tools there. To keep a person in the loop, switch off the write and delete tools in the server's tool list on the Tools page, or use a declarative agent, where Copilot asks on first use and before tools that change data. The bridge tools and addHeadCode default to installIfMissing false, and their descriptions require your explicit yes before the Code Snippets plugin is installed. Separately, the Ryze AI chat has a Tool approvals picker that starts on Skip all approvals; you can switch it to Approve write & delete or Manual approve there, and article publishing follows Publishing mode under SEO > Preferences > Publishing.
Limits in numbers
| Limit | Figure or rule | Set by |
|---|---|---|
| Records per request | per_page takes 1 to 100. The posts reference gives a default of 10, so larger sets need several requests with page or offset | WordPress REST API |
| Paging totals | Every paged answer carries the headers X-WP-Total and X-WP-TotalPages. The connector's read answers carried total and totalPages fields | WordPress REST API, Ryze AI test |
| Smaller answers | _fields limits a response to the fields you name, and nested fields work since WordPress 5.3 | WordPress REST API |
| Request quota | No request quota figure appears on the REST API handbook pages or the WordPress.com MCP pages that were read. WordPress.com's API guidelines ask developers not to make excessive calls and give no number. This records an absence, not a statement by WordPress | Not published on the pages read |
| Application password | 24 characters, letters and digits only, available by default on sites served over HTTPS | WordPress |
| Trash | Trashed posts, pages, attachments and comments are deleted for good after 30 days by default. On WordPress.com, deleted media, categories and tags are permanent | WordPress, WordPress.com |
| Revisions and autosave | Autosave runs every 60 seconds by default, and post revisions are on by default unless a site caps or turns them off | WordPress |
| Search input | The search pattern takes up to 500 characters and context_lines 0 to 10, default 2 | Ryze AI tool definition |
| Edits per call | 1 to 50 edits in one edit call, with old_string up to 20,000 characters and new_string up to 100,000 | Ryze AI tool definition |
| Head code | addHeadCode takes HTML up to 8,192 characters | Ryze AI tool definition |
| Free WordPress.com access | WordPress.com's own MCP server is open to free sites through November 30, 2026. This limit applies to that server, not to the Ryze AI connector | WordPress.com |
| Tools on a Copilot Studio agent | Up to 128 with generative orchestration, and Microsoft suggests 25 to 30. The Ryze AI server is added as one tool; Microsoft does not say whether the 9 WordPress tools inside it count toward 128 | Microsoft, classic experience |
| MCP servers in one conversation | An agent can hold several, but only a capped number run in one conversation and the rest are skipped for that turn. Microsoft gives no figure | Microsoft, new experience |
| Tool call time in plugin packages | A tool call should finish in under 30 seconds. Microsoft names this for plugin packages and Cowork | Microsoft |
Sources: REST API pagination, REST API global parameters, wp-config options, WordPress.com MCP developer page, Copilot Studio tool limits, MCP servers per conversation, tool call time in plugin packages, Ryze AI WordPress integration. Checked November 14, 2026.
What the connection answered, tested
Each row is one call to wordpress__read made on November 14, 2026 through a Ryze AI test workspace with one WordPress.com connection, from Claude Code. Copilot was not used, and no call read posts, pages, media or users.
| What was asked | What came back | Result |
|---|---|---|
| The registered content types (/wp/v2/types) | 18 post types | Worked |
| The registered taxonomies (/wp/v2/taxonomies) | 6 taxonomies | Worked |
| A post ID that does not exist | not_found with Invalid post ID. | Refused |
| A route that does not exist | not_found with No route was found matching the URL and request method. | Refused |
| A post type that does not exist | not_found with Invalid post type. | Refused |
| Posts with per_page set to 101 | HTTP 400, rest_invalid_param, Invalid parameter(s): per_page | Refused |
| Posts sorted by a field that does not exist | HTTP 400, rest_invalid_param, Invalid parameter(s): orderby | Refused |
| A read sent with a body | invalid_arguments, refused by the connector before any request | Refused |
| The /yoast/v1 plugin route on a WordPress.com connection | not_found, as expected for plugin routes there | Refused |
First 3 prompts to run, with a real result
The first prompt has a real result from a test connection, produced through the connector from Claude Code. Copilot has not run these prompts, so the other two describe what should come back.
1. List the taxonomies the site registers
Read the taxonomies registered on my WordPress site and list each one by its slug.
Tools used: wordpress__read
What comes back: A list of taxonomy slugs, read from the site. Nothing is changed.
A real result: This is what the connector returned for the taxonomies read on November 14, 2026. The connection was a WordPress.com site in a test workspace. The answer held 6 taxonomies.
| Taxonomy slug | Kind |
|---|---|
| category | Core: categories |
| post_tag | Core: tags |
| nav_menu | Core: navigation menus |
| wp_pattern_category | Core: block pattern categories |
| wp_guideline_type | Registered on the test site |
| wp_knowledge_type | Registered on the test site |
Returned by wordpress__read in one call. Nothing on the site was changed. The site name and its content are not recorded on this page.
2. Fix a phrase inside a long post
Search the content of the post with ID 123 for the phrase old phrase and show me the matching lines with line numbers. Then replace it with new phrase.
Tools used: wordpress__search_content, wordpress__edit_content
What comes back: The matching lines with line numbers, then a single in-place edit to that text field.
3. Create a draft page
Create a page titled the title I give you with the text I paste below, set its status to draft, then read it back and confirm the status.
Tools used: wordpress__write, wordpress__read
What comes back: A page created through a write request, then a read of the page so you can compare it with what you asked for.
The second and third prompts change the site, so this page shows no result for them. Replace the ID, phrases and title with your own.
The query behind the result
The agent builds the request itself. This is the call behind the result above, as a path relative to /wp-json. Paste it into a prompt and ask the agent to run it with wordpress__read.
path: /wp/v2/taxonomies
tool: wordpress__read (a GET request, no body)The search tool answers with line numbers, which is what makes a small edit safe. It was not run in the test, so this page shows no sample output. Its description says it returns the matching lines with context.
10 jobs to hand to a Copilot agent
Ten jobs a Copilot agent with the Ryze AI tool can take on, each matched to its tool. Only the content-type and taxonomy reads were run through the connector, and none of these jobs was run from Copilot. Four need a self-hosted site and an administrator.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| Recent posts | List my recent posts with title, status, date and category. | wordpress__read | Yes, up to 100 per request |
| Content types | List the custom post types on the site and read the items of one of them. | wordpress__read | Yes |
| Find a phrase | Find every line in a post or page that contains a phrase. | wordpress__search_content | Yes |
| Fix a phrase | Replace that phrase in the post and show me the line before and after. | wordpress__edit_content | Yes, not run in the test |
| Draft a page | Create a draft post or page from the text I give you. | wordpress__write | Yes, not run in the test |
| Tidy a post | Change the title, excerpt, status, categories or tags of a post. | wordpress__write | Yes, not run in the test |
| Alt text | Update image alt text and captions in the media library. | wordpress__write | Yes, not run in the test |
| Delete a post | Delete this post or page after I confirm. | wordpress__delete | Yes. Set this tool to need approval |
| Yoast or Rank Math fields | Write the SEO title, meta description and focus keyword of a post. | wordpress__enableYoastRestBridge or wordpress__enableRankMathRestBridge, then wordpress__write | Self-hosted with an administrator only |
| Head code | Add a verification tag to the head of every page. | wordpress__addHeadCode | Self-hosted with an administrator only |
6 ways to connect Microsoft Copilot to WordPress
Six ways can bring a WordPress site into a Microsoft Copilot product. This guide uses the first, the Ryze AI connector, as the main way: one hosted address that a Copilot Studio agent takes as a tool, with no plugin to run on the site. The others were checked on the dates in the Sources line.
| Way | Runs where | Setup in Copilot | What it reaches on the site | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every user | A Copilot Studio tool (classic experience) or a declarative agent action, with OAuth sign-in | Posts, pages, media, categories, tags, users, plugins and custom post types, to read and to edit. On self-hosted sites also plugin installs, SEO plugin bridges and head code. Deletes go through a separate tool | SEO Starter is $129 per month with a 3-day free trial |
| WordPress.com MCP server | Hosted by WordPress.com at https://public-api.wordpress.com/wpcom/v2/mcp/v1 | Listed for Microsoft 365 Copilot Cowork as a WordPress.com plugin from the Microsoft 365 App Store. For Copilot Studio, whether Dynamic discovery works with its OAuth 2.1 sign-in was not checked | Content, site editing, settings, plugins and more, by the user's role. Jetpack-connected self-hosted sites use the same server. WooCommerce prices, stock and orders are not covered | Included on paid WordPress.com plans. Free sites and Jetpack sites without a plan have access through November 30, 2026. The assistant is billed by its own provider |
| MCP Adapter plugin | On your site, at /wp-json/mcp/mcp-adapter-default-server | A server address and a sign-in as a WordPress user. Microsoft's sign-in list has no Basic auth, so whether an API key header can carry it was not checked | Only the abilities that WordPress core or other plugins register and mark public. The default server exposes 3 meta-tools | Free, GPL-2.0-or-later |
| Composio | Hosted | A remote address from a Composio session. Whether Copilot Studio's sign-in options fit it was not checked | 26 WordPress.com tools: drafts, posts, pages, media, menus, templates, site settings and stats. WordPress.com connections need your own OAuth app | The free plan stops at 10,000 tool calls a month. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Zapier provisions a server for the apps already connected to your Zapier account. Whether Copilot Studio accepts it was not checked | The WordPress actions of your Zapier account, such as Create Post, Update Post and Upload Media | Each successful tool call uses two tasks from your Zapier plan |
| AI Engine plugin | On your site, as a WordPress plugin | A server address with OAuth, which the plugin page describes for Claude and ChatGPT. Copilot is not named | More than 140 tools by the vendor's count, including SEO fields in the installed SEO plugin, with a change history kept 30 days. Pro adds plugins, themes and WooCommerce | The MCP server is in the free plugin. Pro starts at $59 per year |
With a hosted way your site content passes through that vendor, and Microsoft says a Power Platform data policy applies to any MCP server added to Copilot Studio. A plugin on your site keeps the server inside your own hosting, which then has to be reachable from the internet.
Options that do not fit a Copilot agent
- The @automattic/mcp-wordpress-remote proxy, InstaWP/mcp-wp and docdyhr/mcp-wordpress. All three run as Node processes on your computer. No Microsoft route accepts a start command, so each would need a public HTTPS address in front of it, for example a dev tunnel.
- WordPress Studio and WordPress Playground MCP servers. Studio works on local Studio sites and the account's WordPress.com sites, and Playground works on an instance in a browser tab. Neither is a route to a live self-hosted site.
- Automattic/wordpress-mcp. The repository is archived, and WordPress.com's page says it is retired in favor of the MCP Adapter.
- WordPress 7.0 AI Client and Connectors screen. They let plugins on a site call AI models. They point from WordPress out to a model, so they are not a way for Copilot to reach a site.
Which one to pick
Ryze AI is the best way to connect Microsoft Copilot to WordPress for publishing and editing content on self-hosted or WordPress.com sites that an agent maker sets up, with one caveat: WooCommerce prices, stock and orders are outside what the tools cover, and the SEO bridges, head code and plugin installs work only on self-hosted sites with an administrator. WordPress.com's own plugin for Copilot Cowork is the better fit when your Microsoft 365 admin already allows it and your people want to work in Cowork without anyone building an agent. The MCP Adapter suits a developer who registers abilities on the site, and Composio and Zapier make sense when your team already uses one of them for other apps.
Sources: WordPress.com MCP developer page, WordPress.com MCP support page, WordPress.com MCP tools reference, WordPress.com MCP landing page, Jetpack MCP page, MCP Adapter plugin, WordPress/mcp-adapter, Composio WordPress.com toolkit, Composio pricing, Zapier MCP for WordPress, Zapier MCP quickstart, AI Engine plugin, InstaWP/mcp-wp, docdyhr/mcp-wordpress, Copilot Studio MCP guide, debugging a local server with a dev tunnel, Ryze AI WordPress integration. Checked November 14, 2026.
Copilot, WordPress and MCP: dates that matter
| Date | What happened |
|---|---|
| March 19, 2025 | Microsoft announced MCP support in Copilot Studio. The first release used the SSE transport. |
| May 29, 2025 | MCP in Copilot Studio reached general availability. |
| August 2025 | Copilot Studio stopped supporting SSE for MCP; Streamable is the only supported transport. Microsoft gives no exact day. |
| October 7, 2025 | WordPress.com announced MCP support, read-only at first, with write access to come. |
| December 15, 2025 | Microsoft announced general availability of MCP in declarative agents for Microsoft 365 Copilot, built in Agents Toolkit. |
| January 22, 2026 | WordPress.com added OAuth 2.1 for MCP connections. |
| March 20, 2026 | WordPress.com MCP gained write tools: 19 new writing abilities across posts, pages, comments, categories, tags and media. |
| September 2, 2026 | A Microsoft Copilot blog post announced general availability of the GitHub Copilot harness in Copilot Studio, since renamed the Microsoft Copilot harness. Microsoft's how-to page for adding a server on that harness still carries a preview label. |
| October 2, 2026 | The MCP Adapter, WordPress's official MCP plugin, joined the wordpress.org plugin directory with version 0.7.0. |
| October 27, 2026 | The Microsoft 365 Copilot release notes list, under this date, admins creating custom MCP connectors in the Microsoft 365 admin center. Microsoft's roadmap item gives an earlier availability month, February 2026. |
| November 3, 2026 | WordPress.com opened MCP access to free sites for a limited time. |
| November 30, 2026 | Last day of WordPress.com MCP access for free sites and for Jetpack-connected sites without a Jetpack AI or Complete plan. |
Sources: Microsoft Copilot blog, March 19, 2025, Microsoft Copilot blog, May 29, 2025, SSE support ended after August 2025, Microsoft 365 Developer Blog, December 15, 2025, Microsoft Copilot blog, September 2, 2026, Microsoft 365 Copilot release notes, Microsoft 365 roadmap item 501585, WordPress.com blog, October 7, 2025, WordPress.com blog, January 22, 2026, WordPress.com blog, March 20, 2026, WordPress.com blog, November 3, 2026, WordPress.com MCP developer page, free access through November 30, 2026, MCP Adapter plugin changelog. Checked November 14, 2026.
How this guide was tested
The WordPress side was checked through the live connector on November 14, 2026, from Claude Code, on a WordPress.com connection. The Microsoft side was read from Microsoft's own pages on the same day. The table lists what was run and what came back.
| What was run | What came back |
|---|---|
| The tool list in a signed-in MCP client | All 9 WordPress tools loaded by name, each with a definition. Only wordpress__read was called. |
| wordpress__read of content types and taxonomies | 18 post types and 6 taxonomies came back. |
| Calls made to fail on purpose | Seven reads were refused, as listed in the table of tested reads above, and their messages are in the errors table below. |
| A page size above the maximum | per_page 101 was refused with a 400, which confirms the maximum of 100. |
| A plugin route on a WordPress.com connection | /yoast/v1 came back as not found, which matches the rule that plugin routes need a self-hosted connection. |
| Microsoft's pages | Every Copilot Studio and Microsoft 365 Copilot step on this page was read from learn.microsoft.com on November 14, 2026. |
Not run for this guide: every step inside Copilot Studio, Microsoft 365 Copilot, the Microsoft 365 admin center and Agents Toolkit. No agent was created, no server was added, no sign-in was done and no tool was called from a Microsoft product. No read returned posts, pages, media, users or plugins, and the search tool was not run. The write, delete, edit, plugin install, bridge and head-code tools were not run either, because they change the site, and no call was made on a self-hosted connection, so no permission error was seen.
Errors and fixes
Exact error messages from the test
These are the exact messages WordPress and the connector returned in the test on November 14, 2026, from Claude Code. If a Copilot agent shows one of them, this is what it means.
| Message | What it means | What to do |
|---|---|---|
| Invalid post ID. | No post with that ID exists on the connected site. The connector returned the status not_found. | List posts first and use an ID from the list. |
| No route was found matching the URL and request method. | The path does not exist on this site or connection. It also came back for the /yoast/v1 plugin route on a WordPress.com connection. | Check the path against the content types the site lists. Plugin routes need a self-hosted connection. |
| Invalid post type. | The post type slug is not registered on the site. | Read the site's content types and use a slug from that list. |
| Invalid parameter(s): per_page | The status was 400 with the code rest_invalid_param. In the test per_page was 101, and WordPress accepts 1 to 100. | Ask for 100 or fewer per page and page through the rest. |
| Invalid parameter(s): orderby | The status was 400 with the code rest_invalid_param. The sort field does not exist. For posts the handbook lists date, relevance, id, include, title and slug. | Sort by a field the collection supports. |
| GET requests cannot carry a body | A read was sent with a body, so the read tool refused it before contacting WordPress. The full message goes on to say that filters belong in query. | Have the agent put the filters in query. |
Other problems
- There is no place to paste the URL in Copilot chat
- Microsoft's pages show no field for an MCP address in a Copilot chat window. Add the URL as a tool on a Copilot Studio agent or build a declarative agent in Agents Toolkit. An admin can also create a custom federated connector in the Microsoft 365 admin center, but that route was not confirmed for Ryze AI.
- The Tools page or the New tool button is missing
- The agent runs on the new experience, where tools sit on the Build tab. Open the classic experience from the three dots at the bottom of the home page side bar, or create the agent with Other ways to build.
- I cannot publish the agent
- A Copilot Studio trial lets you create and test agents but not publish them. Use the test chat panel, or move to a plan that can publish.
- Model Context Protocol or connectors are missing on the Teams plan
- The Copilot Studio for Teams plan does not include Power Platform connectors or generative orchestration, and MCP access relies on connectors. Ask your admin about a standalone Copilot Studio subscription.
- The connector is blocked
- A Power Platform data policy that regulates connectors also regulates the MCP server, and a blocked tool shows as disabled in the Add tool panel. Ask your Power Platform admin to allow it.
- Agents Toolkit says Custom App Upload is not enabled
- Sideloading needs Upload custom apps turned on by an admin in the Teams admin center. Ask your admin, then reload the Accounts pane.
- The declarative agent sign-in fails
- Microsoft's dynamic registration for declarative agents needs the authorization server to issue a client secret. This was not checked for the Ryze AI server, so use the Copilot Studio route if the sign-in does not complete.
- The agent never calls the WordPress tools
- Microsoft says the orchestrator uses the server description to decide whether to call the server. Rewrite the description to say what the tools do, such as reading and editing WordPress posts and pages, and check that generative orchestration is on.
- The tools return a subscription message or no data
- The WordPress tools need an active Ryze AI plan or free trial, and WordPress must show as connected under Integrations in Ryze AI. If the connector was added before WordPress was connected, remove it from the agent, add it again and start a new test chat.
- Ryze AI cannot reach the site
- A security plugin, firewall or host that blocks /wp-json requests stops the connection. Allow the requests, then connect again. A self-hosted site also needs the Site URL to start with https:// and an application password from the right user.
- A 401 or 403 answer
- Ryze AI's tool definitions treat a 403 saying you are not allowed as a role that is too low, fixed by reconnecting with an administrator application password, and a 401 as a revoked credential. No such error was seen in the test.
- Plugin installs, SEO bridges or head code do nothing
- These four tools work only on a self-hosted connection made with an administrator. On a WordPress.com connection, edit SEO plugin fields in wp-admin.
- Yoast or Rank Math fields do not change
- WordPress drops those fields without an error when they are sent through the plain REST API. Run the one-time bridge for your SEO plugin first, on a self-hosted site, and say yes when the agent asks before it installs the Code Snippets plugin.
Sources: REST API pagination, REST API posts reference, Copilot Studio MCP troubleshooting. Checked November 14, 2026.
Terms on this page
- MCP (Model Context Protocol)
- An open standard through which an AI model reaches outside data and applications. Copilot Studio adds an MCP server to an agent as a tool.
- Classic and new experience
- The two ways Copilot Studio builds agents. Microsoft's pages call the classic one the standard harness and the new one the Microsoft Copilot harness. The setup steps in this guide use the classic one.
- Dynamic discovery
- A Copilot Studio OAuth 2.0 option for servers that support dynamic client registration: Copilot Studio finds the sign-in endpoints and registers itself, so nobody types a client ID.
- Declarative agent
- A Microsoft 365 Copilot agent built from a manifest, here in Agents Toolkit, that can carry an MCP server as an action.
- Application password
- A 24-character password that WordPress makes on a user's profile for programs that use the REST API. It can be revoked on its own and cannot be used to log in at wp-login.php.
- REST API (wp-json)
- WordPress's built-in HTTP interface under /wp-json. Core content lives in the /wp/v2 routes: posts, pages, media, categories, tags and users.
- Role and capability
- A role such as Administrator or Editor is a set of capabilities, and a connection can do only what its user's role allows.
- Jetpack connection
- Links a self-hosted site to a WordPress.com account. Its JSON API forwards signed-in REST requests from WordPress.com to the live site.
Sources: Copilot Studio experiences, Dynamic discovery, declarative agents with MCP, Application passwords, Roles and capabilities, modelcontextprotocol.io. Checked November 14, 2026.
Frequently asked questions
How do I connect Copilot to WordPress?
Connect your site in Ryze AI under Integrations, with a site URL, a username and an application password, or a WordPress.com sign-in. Then, on a Copilot Studio agent in the classic experience, add https://connector.get-ryze.ai/mcp under Tools, Add a tool, New tool, Model Context Protocol, with OAuth 2.0 and Dynamic discovery, and sign in to Ryze AI.
Is there a WordPress connector for Microsoft Copilot?
Yes, two. WordPress.com lists a WordPress.com plugin for Microsoft 365 Copilot Cowork, which needs a Microsoft 365 Copilot license. The Ryze AI connector at https://connector.get-ryze.ai/mcp is the other, added to a Copilot Studio agent as an MCP tool and offering 9 WordPress tools.
Does Copilot work with a WordPress MCP server?
Yes, on an agent. Copilot Studio documents adding an existing MCP server as a tool, and Agents Toolkit documents adding one to a declarative agent. Microsoft's pages show no field for an MCP address in a Copilot chat window, so the server goes onto an agent, not into the chat.
What is the WordPress MCP server URL for Copilot?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. WordPress.com's own server is https://public-api.wordpress.com/wpcom/v2/mcp/v1, and a self-hosted site running the MCP Adapter plugin answers at /wp-json/mcp/mcp-adapter-default-server on its own domain.
Can I paste an MCP URL into the Copilot chat window?
No field for it is documented. Microsoft's pages place the address on a Copilot Studio agent, in a declarative agent built in Agents Toolkit, or in an admin-created connector. Copilot with a personal Microsoft account lists four built-in connectors and mentions no way to add your own.
Which Copilot plan do I need?
Microsoft's MCP how-to pages name none. Copilot Studio is open to all Microsoft 365 users for creating agents, a trial cannot publish them, and the Teams plan lacks Power Platform connectors and generative orchestration. Whether MCP tools run on the Teams plan is not documented.
Are there AI SEO tools that integrate directly with WordPress?
Yes. Ryze AI connects to WordPress with an application password or a WordPress.com sign-in, publishes Content Plan articles to the site as posts, and exposes 9 WordPress tools to MCP clients such as a Copilot Studio agent. SEO Starter is $129 per month with a 3-day free trial.
Can a Copilot agent edit my WordPress posts?
Yes. Through Ryze AI, an agent can create and update posts, pages, media, categories and tags with the write tool, and edit part of a long text field with the edit tool, within the role of the connected WordPress user. It can also search the raw content of a post for a phrase.
Can a Copilot agent delete WordPress content?
Only through the separate wordpress__delete tool, which runs a DELETE request, for example to delete a post. In Copilot Studio you can switch off the delete tool in the server's tool list so the agent never has it. WordPress keeps trashed posts and pages for 30 days by default.
Can Copilot write Yoast or Rank Math fields?
Yes, on a self-hosted site with an administrator user. The agent runs a one-time bridge for Yoast SEO or Rank Math, after you say yes in chat, and can then write the SEO title, meta description, canonical and focus keyword. On WordPress.com connections those fields are edited in wp-admin.
Do I need an application password?
Only for a self-hosted site. An application password is made under Users, Profile, Application Passwords in WordPress admin and acts with that user's role. A WordPress.com or Jetpack site is connected with a WordPress.com sign-in instead, and for a Jetpack site the Jetpack JSON API module must be on.
Can I connect more than one WordPress site?
Yes. Several sites can be connected to one workspace with Add one more account, and the agent uses the primary site unless you name another one. How this interacts with the one-website rule of an SEO plan is not explained in the help center, so check before you rely on it.
Why do the WordPress tools not show up on my agent?
If you connected WordPress in Ryze AI after adding the server, remove the Ryze AI tool from the agent, add it again and start a new test chat so the tool list refreshes.
Was this tested in Copilot?
No. The WordPress reads were run through the Ryze AI connector from Claude Code on November 14, 2026, on a WordPress.com connection. The steps inside Copilot Studio and Microsoft 365 Copilot follow Microsoft's documentation as read on the same day, and were not run.
How much does it cost to connect Copilot to WordPress?
Adding the connector costs nothing, but the WordPress tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month with a 7-day free trial, Agency is $279 per month and Shopify CRO is $1,499 per month. Annual billing takes 30% off the first year. Microsoft's own licensing for Copilot Studio is separate.