By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect VS Code to WordPress is the Ryze AI connector. Connect your site once in Ryze AI, with an application password for a self-hosted site or a WordPress.com sign-in. Then, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers and add an HTTP server with https://connector.get-ryze.ai/mcp and the server ID ryze. Trust it and finish the Ryze AI sign-in in your browser. Copilot Chat then has 9 WordPress tools to read, create, edit and delete content, and 4 of them work on self-hosted sites only.
- Self-hosted site: create an application password under Users > Profile in WP Admin. WordPress.com site: have your sign-in ready
- In Ryze AI open Integrations, click Connect on the WordPress card and enter the site details or sign in to WordPress.com
- In VS Code run Chat: Open Customizations, select MCP Servers and add an HTTP server with the connector URL
- Trust the server, sign in to Ryze AI and ask Copilot Chat to list your recent posts
VS Code to WordPress at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, saved in VS Code as one HTTP MCP server called ryze |
| Server address | https://connector.get-ryze.ai/mcp, the same for every user |
| Where it goes in VS Code | Chat: Open Customizations > MCP Servers > Add Server (+), or the MCP: Add Server command. A personal entry lands in Copilot Global, ~/.copilot/mcp-config.json |
| Sign-in from VS Code | OAuth in the browser, run by VS Code. No WordPress password is typed into VS Code |
| Sign-in to WordPress | Done once in Ryze AI. A self-hosted site takes the site URL, a WordPress username and an application password. A WordPress.com or Jetpack site takes a WordPress.com sign-in |
| WordPress tools | 9: 2 read, 6 write and 1 delete. Installing plugins, the Yoast and Rank Math bridges and head code work on self-hosted sites only |
| Can Copilot change the site | Yes, through the write, edit and delete tools. A new VS Code session starts on Manual permissions, which show a call that is not auto-approved before it runs |
| Other data in the same chat | This guide covers the WordPress tools only. Tools for other Ryze AI platforms appear when you connect those platforms in the same workspace |
| Copilot plan | GitHub lists MCP in every Copilot plan. Business and Enterprise seats also need the MCP servers in Copilot policy, which ships off |
| Ryze AI price | SEO Starter is $129 per month with a 3-day free trial. Adding the connector is free |
| WordPress's own option for VS Code | The WordPress.com MCP server at https://public-api.wordpress.com/wpcom/v2/mcp/v1 names VS Code on its pages. Free sites and Jetpack sites without a Jetpack plan have access only through November 30, 2026 |
| Last tested | 9 read-only WordPress calls through the connector on November 14, 2026, on a WordPress.com connection. No step inside VS Code was run |
Before you start
- GitHub Copilot in a current VS Code. GitHub's MCP article asks for Copilot access and VS Code 1.99 or later. The steps below save the server to Copilot Global, which arrived in VS Code 1.140, so update an older install first. An eligible GitHub account with no plan is enrolled in Copilot Free when it signs in to VS Code.
- The MCP policy, when Copilot comes from an organization. On Copilot Business or Copilot Enterprise through an organization or enterprise, the MCP servers in Copilot policy must be on, and GitHub ships it off. Copilot Free, Pro, Pro+ and Max are outside that policy.
- A local folder, with Copilot as the session target. Microsoft's walkthrough asks for AI features on, a local folder open and Copilot picked in the Session Target dropdown before a server is added.
- A WordPress user whose role fits the job. The connection acts as that user. An Editor can publish and manage posts, an Author only their own, and a Contributor cannot publish. Plugin installs, the Yoast and Rank Math bridges and head code need an Administrator on a self-hosted site.
- A site that answers over HTTPS. WordPress turns application passwords on by default only for sites served over HTTPS. A security plugin, firewall or host that blocks /wp-json requests stops the connection until you allow them.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial and publishes Content Plan articles to your WordPress site. Adding the connector is free, but the WordPress tools need any active Ryze AI plan or trial.
How to connect VS Code to WordPress with the Customizations editor
The first two steps happen in WordPress and Ryze AI, the other four in VS Code. The connector URL is the same for every user.
Prepare the WordPress login
On a self-hosted site, open Users > Profile in WP Admin, scroll to Application Passwords, type a name such as Ryze AI, click Add New Application Password and copy the result. WordPress shows it once. On a WordPress.com or Jetpack site there is nothing to create. For a Jetpack site, the Jetpack JSON API module must be enabled.
Connect the site in Ryze AI
Create a Ryze AI account or sign in, open Integrations and click Connect on the WordPress card. On the Self-hosted site tab enter the site URL starting with https://, your wp-admin username and the application password, then click Continue. On the WordPress.com / Jetpack tab sign in, approve access and choose the site if the account has several.
Open the MCP Servers list in VS Code
Open a local project folder and pick Copilot in the Session Target dropdown, because the editor lists the servers of the selected harness. Run Chat: Open Customizations from the Command Palette, select MCP Servers and choose Add Server (+) in the User group.
Add the HTTP server
Choose HTTP (HTTP or Server-Sent Events) and enter https://connector.get-ryze.ai/mcp. Type ryze as the server ID. For a personal setup select Global, then Copilot Global. There is no client ID or secret to enter.
Trust the server and sign in
Read the trust prompt before you accept it, then finish the Ryze AI sign-in in the browser. If no sign-in page opens, use the ellipsis (...) beside ryze in MCP Servers and choose Authenticate. On the Ryze AI page pick the workspace that holds your WordPress connection and click Allow connection.
Ask your first question in Copilot Chat
Open Copilot Chat and ask: List my 10 most recent WordPress posts with title, status, date and category. Expand the tool call in the conversation to confirm the ryze server answered. Microsoft's docs point out that a reply with no tool call proves nothing about the connection.
Optional: click View on the WordPress card in Ryze AI to choose the Author and Category that new posts use, then click Save. To add a second site, click View and then Add one more account.
The Ryze AI help center page for WordPress covers the WordPress side of the connection, and the VS Code MCP servers documentation covers the editor side.
Sources: VS Code MCP servers, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans, Application Passwords integration guide, WordPress.com MCP support page, Ryze AI help center page for WordPress. Checked November 14, 2026.
Command Palette and config files
The Customizations editor, the guided command and the config files all end in the same server entry. Pick by how you manage VS Code. WordPress needs nothing different for any of them, because the site was connected in Ryze AI before VS Code was involved.
Guided flow
Run MCP: Add Server from the Command Palette and answer the prompts with the same URL and the server ID ryze. It skips the Customizations editor.
Portable config file
To write the entry by hand, use the portable format that the Copilot harness reads. It lives in ~/.copilot/mcp-config.json for you alone ($COPILOT_HOME/mcp-config.json when that variable is set) or in .mcp.json at the workspace root. Both start with mcpServers. Every portable HTTP example in Microsoft's reference carries a tools field, so this one does too:
{
"mcpServers": {
"ryze": {
"type": "http",
"url": "https://connector.get-ryze.ai/mcp",
"tools": ["*"]
}
}
}Older VS Code format
The earlier format uses the key servers in .vscode/mcp.json or the profile mcp.json. It belongs to the Local harness, which VS Code 1.146 deprecated on November 11, 2026, with removal announced for February 2027. Copilot harness sessions do not read these files directly. Older tutorials still show this shape, and WordPress.com's own VS Code command writes it too:
{
"servers": {
"ryze": {
"type": "http",
"url": "https://connector.get-ryze.ai/mcp"
}
}
}In the portable entry, ["*"] makes every tool of the server available and leaves approvals in place. Portable files do not support VS Code input variables, envFile or SecretStorage. A workspace .mcp.json is meant to be committed for a team, and with this connector it holds only the address. The WordPress credential stays in Ryze AI and never lands in a file you commit.
Limits of VS Code to know
- The type field sets the transport: http for Streamable HTTP, stdio for a local command and sse for older endpoints that Microsoft labels legacy. The ryze entry uses http.
- Trusting a server lets it start, signing in gives it access, and approving covers single tool calls. VS Code treats these as three steps.
- Copilot Global does not sync to your other machines, and a remote host or Dev Container does not read the local file. Add the server on the machine where the session runs.
- Settings Sync carries the profile mcp.json only, so it leaves both the Copilot user file and .mcp.json files behind.
- Microsoft's MCP developer guide says VS Code signs in to providers other than GitHub and Microsoft Entra through Dynamic Client Registration or a pre-registered OAuth client. Ryze AI was not tried inside VS Code for this guide. If the sign-in does not start, email Ryze AI support with the link at the end of the page.
VS Code, Copilot and MCP in one table
| Topic | What Microsoft and GitHub document |
|---|---|
| Screen for adding a server | Chat: Open Customizations opens the Agent Customizations editor. Its MCP Servers page has Add Server (+). The Chat title bar and the Agents window sidebar open the same editor |
| Files the Copilot harness reads | ~/.copilot/mcp-config.json (Copilot Global) for one person and .mcp.json at the workspace root for a shared setup, each with a top-level mcpServers object |
| Legacy files | .vscode/mcp.json and the profile mcp.json, with a servers object, kept for the deprecated Local harness |
| Transports | stdio starts a command, http speaks Streamable HTTP, and sse reaches older endpoints that lack Streamable HTTP |
| Sign-in | When a server asks for OAuth, the Copilot runtime hands the sign-in to VS Code, which stores the credentials. Redirects go to http://127.0.0.1:33418 or https://vscode.dev/redirect. The portable format has a flat oauthClientId field for a pre-registered client |
| Keys and headers | HTTP entries accept a headers object whose values can read environment variables as ${NAME}. The portable files ignore input prompts, envFile and SecretStorage, so VS Code never asks you for a key there |
| Tool approval | New sessions start on Manual permissions and show the tool name and its inputs for any call that is not auto-approved. The chat input dropdown also offers Assisted permissions, where an LLM judges each call, and Allow all. Autopilot approves every tool |
| Plan | GitHub includes MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise. Business and Enterprise seats also need the MCP servers in Copilot policy, off by default |
| Admin controls | allowedMcpServers and deniedMcpServers in enterprise-managed settings match a server by URL, command or name, and a local file cannot lift a block. chat.mcp.access set to none turns MCP off |
| Managing a server | Each entry in MCP Servers has a toggle and an ellipsis menu with Start, Stop, Enable or Disable, Uninstall and Show Output, plus Authenticate when a sign-in is pending. MCP: List Servers offers the same actions |
| Tool cap | 128 enabled tools per chat request. Past that, VS Code answers Cannot have more than 128 tools per request. |
Sources: VS Code MCP servers, VS Code MCP configuration reference, VS Code: manage MCP servers, VS Code MCP developer guide, VS Code tool approvals, VS Code agent harnesses, VS Code enterprise AI settings, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans. Checked November 14, 2026.
Other editors and assistants
The same URL works in other MCP clients. The site is connected once in Ryze AI, so nothing changes on the WordPress side.
Cursor
Cursor keeps its servers in its own mcp.json, with mcpServers and a url field. The same Ryze AI connection serves it. How to connect Cursor to WordPress.
Claude and Claude Code
Claude takes the same URL under Customize, Connectors, and Claude Code takes it from the command line. How to connect Claude Code to WordPress.
ChatGPT
ChatGPT takes the same URL as a custom MCP app. Its plan rules differ from Copilot's, so follow its own guide. How to connect ChatGPT to WordPress.
WordPress access, roles and credentials
A self-hosted connection has no app scopes to approve, so the access question is about the user behind it, and the WordPress.com sign-in adds its own limits. Two sign-ins are involved: the WordPress one, done once in Ryze AI, and the Ryze AI sign-in that VS Code starts. Four things decide what Copilot Chat can reach.
- Which site
- The site you connected in Ryze AI. One workspace can hold several WordPress sites through Add one more account. The agent uses the primary site unless you name another, and the live tools accept a connection_id to aim at one.
- Which credential
- A self-hosted site uses an application password, which acts with the access of the WordPress user it belongs to. A WordPress.com or Jetpack site uses a WordPress.com sign-in. Which OAuth scope that sign-in requests is not stated in the Ryze AI facts, so this guide names none.
- Which role the user has
- The role of the connected user limits every call. A 403 that says the user is not allowed to do something means the role is too low, and the fix is to reconnect with a user whose role fits, an Administrator for plugin installs, bridges and head code.
- What VS Code asks
- A server saved in Copilot Global can ask for your trust before it starts, and again after its entry changes. Manual permissions then show each WordPress call that is not auto-approved, with its tool name and inputs.
Scopes behind each action
The table maps what you ask Copilot Chat to do to the WordPress access involved. WordPress decides by role, so the third column says which role covers the job according to WordPress's roles page.
| Action in Ryze AI | WordPress access | Who can do it |
|---|---|---|
| Read posts, pages, media, categories, tags and custom post types | REST API reads on the connected site | Depends on the route and the user's role. Reading the plugin list needs the activate_plugins capability |
| Create or update posts and pages | REST API writes | Editor and Author can publish, and an Author only their own posts. A Contributor can write but cannot publish |
| Delete a post or page | A DELETE request | The user's role must allow deleting that item |
| Targeted text edits | A read, then a write of the same field | Same role rule as an update |
| Install a plugin from wordpress.org | Self-hosted connections only | Administrator with activate_plugins |
| Yoast or Rank Math fields, head code | Self-hosted connections only, through a Code Snippets plugin snippet | Administrator with activate_plugins |
Each credential and role, in WordPress's words
WordPress lists no per-app scopes for application passwords, and the guide it publishes names scoping a password to less access as future work. So the credential and the role are what matter. The table sets out each credential type and each role that comes up, with what WordPress says about it.
| Credential or role | What WordPress says | What it means for the Ryze AI tools |
|---|---|---|
| Application password (self-hosted) | Shipped with WordPress 5.6. 24 characters, letters and digits. Created on the Edit User page, where it can also be revoked. It cannot be used to log in at wp-login.php | The default for self-hosted sites. It acts with its user's own access |
| WordPress.com sign-in (WordPress.com and Jetpack sites) | WordPress.com's OAuth endpoints work the same for WordPress.com sites and Jetpack-connected sites. The Jetpack JSON API forwards authenticated REST requests to the live site once Jetpack is connected | Reaches only the core /wp/v2 routes. Plugin routes such as /yoast/v1 answer not found |
| Administrator | Access to all administration features within a single site, including activate_plugins | The only role for plugin installs, the SEO bridges and head code |
| Editor | Can publish and manage posts, including other users' posts | Covers content edits across authors |
| Author | Can publish and manage their own posts | Covers edits to their own posts only |
| Contributor | Can write and manage their own posts but cannot publish them | Drafts only |
| Subscriber | Can only manage their profile | Too low for content work |
WordPress.com adds one more rule on top of roles: its connection reaches the core /wp/v2 REST routes and nothing else. On a self-hosted site, plugin routes are reachable when the plugin registers them.
Not included: plugin installs, the Yoast and Rank Math bridges and head code on WordPress.com connections, where SEO plugin fields are edited in wp-admin. Plugins from uploaded zip files or URLs, because only the wordpress.org directory is supported. robots.txt changes, which Technical Audit explains step by step instead. Elementor text where the post type does not expose meta._elementor_data. Yoast and Rank Math fields written through the plain REST API without the bridge, which WordPress silently drops.
Sources: WordPress REST API authentication, Application Passwords integration guide, WordPress roles and capabilities, WordPress.com OAuth2, WordPress.com API namespaces, Jetpack JSON API, WordPress plugins REST reference, Ryze AI help center page for WordPress. Checked November 14, 2026.
Removing access
To stop access from VS Code, open Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. Stop is weaker: it ends the current run and a later request can start the server again. To end WordPress access, disconnect the site in Ryze AI, and on a self-hosted site also revoke the application password on the user's profile page.
What Copilot Chat can do in WordPress
The Ryze AI connector exposes 9 WordPress tools: 2 read, 6 write and 1 delete. Each takes a workspace and an optional connection_id that picks one of the connected sites. Reads, writes and deletes are separate tools, so VS Code can ask about each one on its own.
| 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 post 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 connected 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 WordPress REST API request, for example to delete a post. |
Some limits hold in every client. The last four write tools, plugin installs, both bridges and head code, work on self-hosted sites only. Plugin installs can crash a WordPress site, so approve each one. The bridge and head-code tools default to installIfMissing false, and their descriptions require your explicit yes in chat before the Code Snippets plugin is installed. A security plugin, WAF or host that blocks /wp-json requests stops the connection until you allow them.
A new VS Code session uses Manual permissions unless a setting or an organization default says otherwise, so a WordPress call that is not auto-approved shows its tool name and inputs before it runs. Watch Chat: Manage Tool Approval, because the top-level checkbox for ryze trusts every tool on the server, wordpress__delete and wordpress__installPlugin included. Setting a tool to false in chat.tools.eligibleForAutoApproval keeps it on manual approval, while Allow all and Autopilot approve everything. The Ryze AI chat itself starts on Skip all approvals and can switch to Approve write & delete or Manual approve. Article publishing from a Content Plan follows Publishing mode in SEO > Preferences > Publishing, which is Automatic by default or Manual.
Calls tested through the connector
Each row is one read-only call that went through the Ryze AI connector on November 14, 2026, to a WordPress.com site already linked in a test workspace. Claude Code sent the calls, and it reaches the same server and tools that VS Code does. No post, page or user was read, and no site detail is kept here.
| Request | Tool and input | What came back |
|---|---|---|
| List the post types | wordpress__read, /wp/v2/types | Worked. 18 post types, among them post, page and attachment |
| List the taxonomies | wordpress__read, /wp/v2/taxonomies | Worked. 6 taxonomies, among them category and post_tag |
| Read a post that does not exist | wordpress__read, /wp/v2/posts/ with the ID 999999999 | Refused with status not_found |
| Read a route that does not exist | wordpress__read, /wp/v2/no-such-route | Refused with status not_found |
| Read a post type that does not exist | wordpress__read, /wp/v2/types/not_a_type | Refused with status not_found |
| Ask for 101 posts in one page | wordpress__read, /wp/v2/posts with per_page 101 | Refused by WordPress, HTTP 400, code rest_invalid_param |
| Sort by a field that does not exist | wordpress__read, /wp/v2/posts with orderby no_such_field | Refused by WordPress, HTTP 400, code rest_invalid_param |
| Send a body with a read | wordpress__read, /wp/v2/types with a body | Refused by the connector before any request, status invalid_arguments |
| Read a plugin route | wordpress__read, /yoast/v1 | Refused with status not_found, as expected on a WordPress.com connection |
Limits in numbers
WordPress sets most of these numbers, in its own units. The Ryze AI rows come from the live tool definitions and the last row is VS Code's. The pages opened for this guide give no request quota or rate limit figure. That records what the pages say and is not a statement by WordPress that no limit exists.
| Limit | Figure | Source |
|---|---|---|
| Records per REST request | per_page takes 1 to 100. The posts reference gives a default of 10. Bigger sets need several requests with page or offset | WordPress REST API pagination |
| Paging totals | Every paged answer carries X-WP-Total and X-WP-TotalPages headers. The Ryze AI read tool returned total and totalPages fields in the test | WordPress REST API pagination |
| Field selection | _fields limits an answer to named fields, and nested fields work since WordPress 5.3 | WordPress global parameters |
| Application password | 24 characters, upper-case, lower-case and numeric only. On by default for users on HTTPS sites. The Last Used column is accurate to within 24 hours | Application Passwords integration guide |
| Trash | Trashed posts, pages and attachments are deleted for good after 30 days by default (EMPTY_TRASH_DAYS). On WordPress.com, deleted media, categories and tags are permanent | wp-config reference |
| Autosave and revisions | Autosave every 60 seconds by default. Revisions are on by default and can be capped or turned off | wp-config reference |
| path in read, write and delete | Up to 2,000 characters | Ryze AI tool definition, November 14, 2026 |
| Edits per edit_content call | 1 to 50 edits. old_string up to 20,000 characters and new_string up to 100,000 | Ryze AI tool definition, November 14, 2026 |
| search_content | pattern up to 500 characters, context_lines 0 to 10 with a default of 2, content_path up to 500 characters | Ryze AI tool definition, November 14, 2026 |
| addHeadCode and installPlugin | html up to 8,192 characters and name up to 80. A plugin slug up to 128 characters, lower-case letters, digits and hyphens | Ryze AI tool definition, November 14, 2026 |
| WordPress.com MCP, free access | Free WordPress.com sites and Jetpack sites without a Jetpack AI or Complete plan have MCP access through November 30, 2026 | WordPress.com MCP documentation |
| VS Code | 128 enabled tools per chat request | VS Code tools |
Sources: WordPress REST API pagination, WordPress global parameters, WordPress posts reference, wp-config reference, WordPress.com MCP documentation, VS Code tools, Ryze AI help center page for WordPress. Checked November 14, 2026.
First 3 prompts to run
These prompts use only what the 9 tools document. What comes back is your own site content, so no sample output is shown.
1. List recent posts
List my 10 most recent WordPress posts with title, status, date and category.
Tools used: wordpress__read
What comes back: A list of posts with the fields you named, up to 100 per request. Nothing is changed.
2. Find and fix a phrase
Search the content of the post with ID 123 for the phrase old phrase and show me the matching lines. Then replace it with new phrase.
Tools used: wordpress__search_content, wordpress__edit_content
What comes back: The matching lines with line numbers and context, then one find-and-replace edit to that field once you approve the call in VS Code.
3. Create a draft page
Create a draft page titled Example page with the text I give you, then read it back so I can check the status is draft.
Tools used: wordpress__write, wordpress__read
What comes back: A write call that creates the page once you approve it, then a read of the saved page so you can compare it with your request.
Replace the ID, the phrases and the title with your own. Read each write and delete call before you approve it in VS Code.
10 jobs to hand to Copilot Chat
Ten jobs to type into Copilot Chat once the ryze server is running, each with the tool behind it and whether either connection method can do it. Only the post type and taxonomy reads and some refused calls were run in the November 14, 2026 test, and none of them read content. Jobs that change the site use a write or delete tool.
| Job | Ask Copilot | Tool | On the default connection |
|---|---|---|---|
| Post inventory | List my recent posts with title, status, date and category. | wordpress__read | Yes, on both methods. Not run in the test |
| Custom post types | Which custom post types does this site have, and what are their routes? | wordpress__read on /wp/v2/types | Yes. Run in the test |
| Find a phrase | Show every line in this post that contains this phrase. | wordpress__search_content | Yes. Not run in the test |
| Replace a phrase | Replace that phrase in this post and show the line before and after. | wordpress__edit_content | Yes, after you approve the call. Not run, because it changes the site |
| Create a draft | Create a draft post with this title and text. | wordpress__write | Yes, after you approve the call. Not run |
| Retitle and recategorize | Change this post's title and move it to this category. | wordpress__write | Yes, after approval. Not run. Also creates and renames categories and tags |
| Alt text | Update the alt text and caption of this image in the media library. | wordpress__write | Yes, after approval. Not run |
| Delete a post | Delete this post. | wordpress__delete | Yes, if the role allows it. Keep this tool on manual approval |
| SEO plugin fields | Set the Yoast SEO title and meta description for this post. | wordpress__enableYoastRestBridge, then wordpress__write | Self-hosted with an Administrator only. Not on WordPress.com. Rank Math works the same way with its own bridge tool |
| Tracking tag | Add this verification tag to the head of every page. | wordpress__addHeadCode | Self-hosted with an Administrator only. Not on WordPress.com |
6 ways to connect VS Code to WordPress
Six ways can bring a WordPress site into Copilot Chat in VS Code. They differ in where they run, which kind of site they reach and what the assistant can change. This guide treats the Ryze AI connector as the main way, because the site is connected once in Ryze AI, VS Code holds one hosted address and reads, writes and deletes stay separate tools. The other five were read on their own pages on November 14, 2026. None was set up for this guide.
| Way | Runs where | Setup in VS Code | What it reaches in WordPress | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at one address | Chat: Open Customizations > MCP Servers > Add Server (+), HTTP, ID ryze, saved to Copilot Global, or an mcpServers entry in a portable file. Sign in to Ryze AI in the browser. The site is connected once in Ryze AI | Posts, pages, media, categories, tags and custom post types to read, create, update and delete. On self-hosted sites also plugin installs, Yoast and Rank Math fields and head code. Several sites per workspace | 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 | WordPress.com's Jetpack page gives code --add-mcp with that address. VS Code's reference says that command writes the older format, not the Copilot user file. The sign-in is OAuth 2.1 with PKCE in the browser, after you switch on Enable MCP access under Preferences, AI and MCP | Content, site editing, settings, plugins, users, comments, stats and domains, plus Jetpack features on connected self-hosted sites. One connection covers every site on the account. WooCommerce store data such as prices, stock and orders is not covered | Included on paid WordPress.com plans. Free sites and Jetpack sites without a Jetpack AI or Complete plan have access through November 30, 2026 |
| MCP Adapter plugin | On the WordPress site, version 0.7.1 from wordpress.org | Install the plugin from Plugins > Add New, register or install abilities, then point an HTTP client at /wp-json/mcp/mcp-adapter-default-server. The plugin's CLI guide names VS Code. Its README shows an Authorization: Basic header built from a username and application password for Claude Code. VS Code accepts a headers object on an HTTP entry, and that combination was not tried here | Only the abilities the site registers and marks public. The default server exposes 3 meta-tools. It adds no content tools of its own. Needs WordPress 6.9 and PHP 7.4 | Free, GPL-2.0-or-later |
| docdyhr/mcp-wordpress, open source | A Node process you run, or a Claude Desktop extension file | A command entry that runs npx mcp-wordpress with WORDPRESS_SITE_URL, WORDPRESS_USERNAME and WORDPRESS_APP_PASSWORD. The README lists VS Code among its guide links, and those guides were not opened. Version 4.2.6 declares Node.js 22.22.2 or higher | 73 tools and up to 50 sites, as the README states it. Needs WordPress 5.6 or later with the REST API on and an application password | Free, MIT licence. 114 GitHub stars, last push November 10, 2026 |
| Composio | Hosted | A hosted MCP address, https://connect.composio.dev/mcp, added to VS Code as an HTTP server. Composio's per-client pages for VS Code were not opened. WordPress.com connections must go through your own OAuth app, registered with WordPress.com once | 26 tools for WordPress.com accounts: drafts, posts, pages, media, menus, templates, site settings, stats and the site list. No toolkit page for self-hosted WordPress was found | Free plan stops at 10,000 app tool calls a month on Composio's pricing page, while its WordPress.com toolkit page names 100,000. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Zapier lists VS Code among its supported MCP clients. Add Zapier as a connector and sign in, and Zapier turns on actions for apps already linked to your Zapier account | 8 actions are shown before Load More, among them Create Post, Update Post, Upload Media, Create Tag and API Request. The page states no total, and does not say whether WordPress.com sites, self-hosted sites or both are covered | Each successful tool call uses 2 tasks from your Zapier plan |
WordPress options that do not fit this job
- A Copilot connector for WordPress. GitHub's supported connectors page listed 26 services on November 14, 2026, and WordPress was not one of them. The list is in public preview and can change.
- WordPress Studio MCP server. It lets an agent create, start and stop local Studio sites on your computer and run WP-CLI there, and the docs say it can also work on the account's WordPress.com sites. The page describes no route to a live self-hosted site.
- AI Engine by Meow Apps. This plugin has an MCP server of its own on the site, with more than 140 tools by its page. The plugin page says Claude and ChatGPT connect with OAuth, and it names ChatGPT, Claude, Claude Code and OpenClaw but not VS Code.
- InstaWP/mcp-wp and @automattic/mcp-wordpress-remote. The first is a Node server whose README walks through Claude Desktop only. The second is a stdio-to-HTTP proxy for clients that cannot reach an HTTP server, and its README says a client that supports Streamable HTTP can connect to the endpoint directly. VS Code can.
- Automattic/wordpress-mcp. The earlier plugin. Its repository is archived, and WordPress.com says it is being retired in favor of the MCP Adapter.
- WordPress Playground MCP and WordPress Agent Skills. The Playground server works on a Playground instance in a browser tab and not on a live site. Agent Skills teach an assistant WordPress development patterns and give no access to a site or its data.
- The AI Client and Connectors screen in WordPress 7.0. These let plugins on a site call out to Claude, ChatGPT or Gemini. They point from WordPress to a model, so they do not let VS Code reach a site.
Which one to pick
Ryze AI is the best way to connect VS Code to WordPress for editing content and SEO fields on a self-hosted or WordPress.com site through one hosted address, with one caveat: its tools use the REST API, so what they reach depends on the user's role, and plugin installs, the SEO bridges and head code do not work on WordPress.com. The WordPress.com MCP server reaches wider into a WordPress.com account, including domains and plans, and is the better pick when you manage the account itself and not only the content. The MCP Adapter suits a developer who registers custom abilities on a site. Composio and Zapier fit teams that already route other apps through them. VS Code caps a chat request at 128 tools, so switch off servers you do not need.
Sources: WordPress.com MCP documentation, WordPress.com MCP tools reference, WordPress.com MCP support page, Jetpack MCP page, MCP Adapter on wordpress.org, MCP Adapter on GitHub, docdyhr/mcp-wordpress, Composio WordPress.com toolkit, Composio pricing, Zapier MCP for WordPress, Zapier MCP quickstart, WordPress Studio MCP, AI Engine on wordpress.org, InstaWP/mcp-wp, @automattic/mcp-wordpress-remote, WordPress Playground MCP announcement, WordPress Agent Skills, WordPress 7.0 announcement, GitHub supported connectors, Ryze AI help center page for WordPress. Checked November 14, 2026.
WordPress, Copilot and MCP: dates that matter
| Date | What happened |
|---|---|
| November 5, 2020 | WordPress published its integration guide for Application Passwords, which shipped with WordPress 5.6. |
| April 4, 2025 | VS Code 1.99, the March 2025 release, came out with MCP server support in agent mode. |
| October 7, 2025 | WordPress.com announced MCP support, read-only for the time being, with write access promised next. |
| December 2, 2025 | WordPress 6.9 shipped with the Abilities API included, which the MCP Adapter builds on. |
| January 22, 2026 | WordPress.com added OAuth 2.1 to its MCP connections. |
| March 20, 2026 | WordPress.com MCP gained 19 writing abilities across posts, pages, comments, categories, tags and media. |
| September 30, 2026 | VS Code 1.140 added Copilot Global and the workspace .mcp.json as destinations in MCP: Add Server. |
| October 2, 2026 | The MCP Adapter entered the wordpress.org plugin directory with version 0.7.0. |
| October 22, 2026 | VS Code 1.143 made the Copilot harness the default for new sessions. |
| October 28, 2026 | VS Code 1.144 and GitHub opened Copilot connectors in preview with 26 services. WordPress was not among them on November 14, 2026. |
| November 3, 2026 | WordPress.com opened MCP access to free sites for a limited time. |
| November 11, 2026 | VS Code 1.146 deprecated the Local harness that reads .vscode/mcp.json, with removal announced for February 2027. |
| November 30, 2026 | Last day of the free MCP access for free WordPress.com sites and for Jetpack sites without a Jetpack AI or Complete plan. |
Sources: Application Passwords integration guide, VS Code 1.99, WordPress.com MCP announcement, WordPress 6.9, WordPress.com OAuth 2.1 announcement, WordPress.com write abilities announcement, VS Code 1.140, MCP Adapter on wordpress.org, VS Code 1.143, VS Code 1.144, GitHub changelog, October 28, 2026, WordPress.com free access post, VS Code 1.146, WordPress.com MCP documentation. Checked November 14, 2026.
How this guide was tested
On November 14, 2026, a signed-in MCP client sent the live Ryze AI connector 9 read-only WordPress calls on one WordPress.com connection in a test workspace. The table sums up what came back.
| What was run | What came back |
|---|---|
| WordPress tool definitions | All 9 loaded by name from the live connector. Each takes a workspace and an optional connection_id. read, write and delete take a path relative to /wp-json, a query and a body. The two bridge tools and addHeadCode take installIfMissing, which defaults to false. |
| Two schema reads | The post types route listed 18 types and the taxonomies route listed 6. No content was kept. |
| Three reads of things that do not exist | A post ID, a route and a post type, each refused with status not_found and WordPress's own message. |
| Two reads WordPress refused | A page size of 101 and an unknown sort field, each answered with HTTP 400 and the code rest_invalid_param. |
| One read the connector refused | A read sent with a body, rejected before any request reached WordPress. |
| One plugin route | A /yoast/v1 read came back not found, which matches the rule that WordPress.com connections reach only the core /wp/v2 routes. |
Not run: anything inside VS Code. The ryze server was not added to Copilot Global, no trust prompt or sign-in was seen, and Copilot Chat sent no tool call. The VS Code steps follow Microsoft's documentation pages dated November 11, 2026 and GitHub's Copilot docs, both read on November 14, 2026. The WordPress calls came from Claude Code, a different client that reaches the same server and tools. Only a WordPress.com connection was tested. No self-hosted connection was made, so no application password, 401 or 403 answer, SEO bridge, head code or plugin install was seen. No read returned posts, pages, media, users or plugins, wordpress__search_content was not called, and the write, edit and delete tools were not run because they change the site.
Errors and fixes
Six answers came back in the calls of November 14, 2026. They come first. The rest of the list follows the documentation of Ryze AI, WordPress, Microsoft and GitHub, without a test behind it.
| Message | What it means | What to do |
|---|---|---|
| Invalid post ID. | status not_found. No post has that ID on the connected site. | List posts first and reuse an ID from the list. |
| No route was found matching the URL and request method. | status not_found. The path does not exist on this site or connection. It also comes back for a plugin namespace such as /yoast/v1 on a WordPress.com connection. | Check the path against /wp/v2/types. Plugin routes need a self-hosted connection. |
| Invalid post type. | status not_found. That post type slug is not registered on the site. | Read /wp/v2/types and use a slug from the answer. |
| Invalid parameter(s): per_page | HTTP 400 with the code rest_invalid_param. The test asked for 101 and WordPress accepts 1 to 100. | Ask for 100 or fewer per page and continue to the next page. |
| Invalid parameter(s): orderby | HTTP 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, with a hint to pass filters in query | status invalid_arguments. The read tool rejects the call before it contacts WordPress. The real message has a dash that this page does not print. | Put the filters in the query and leave the body out. |
- The MCP server does not start in VS Code
- On Copilot Business or Enterprise, ask an administrator to enable the MCP servers in Copilot policy, which ships off. Admins can also block a server with deniedMcpServers or turn MCP off with chat.mcp.access set to none, and a local file cannot override either. Check the version too: MCP needs VS Code 1.99 or later and Copilot Global needs 1.140.
- The sign-in never opens
- Trust and sign-in are separate steps, so trust the server first. Then choose Authenticate from the ellipsis menu of ryze in MCP Servers, or run MCP: List Servers to see its state. Show Output in the same menu opens the log. Email Ryze AI support if it stays stuck.
- An older tutorial does nothing
- Tutorials built on .vscode/mcp.json target the Local harness. New sessions have used the Copilot harness since VS Code 1.143, which reads ~/.copilot/mcp-config.json and the workspace .mcp.json. Add the server again through Chat: Open Customizations.
- No WordPress tools appear
- If the site was connected in Ryze AI after the server was added, remove the ryze server, add it again and start a new chat so the tool list refreshes. The WordPress tools also need an active Ryze AI plan or trial.
- Ryze AI cannot reach the site
- A security plugin, WAF or host that blocks /wp-json requests stops the connection. Allow those requests, and check that the site answers over HTTPS, because application passwords are on by default only there.
- A call says the user is not allowed
- A 403 with a message that starts Sorry, you are not allowed means the connected user's role is too low. Reconnect with a user whose role fits, an Administrator for plugin installs, bridges and head code. A 401 means the application password was revoked, so create a new one.
- Yoast or Rank Math fields do not save
- WordPress silently drops those fields when they are written through the plain REST API. On a self-hosted site, ask Copilot to run the bridge tool for your plugin once, and approve the Code Snippets install when it asks. On WordPress.com, edit them in wp-admin.
- Plugin installs, bridges or head code fail on WordPress.com
- These need a self-hosted connection. WordPress.com connections reach only the core /wp/v2 routes.
- Copilot edits the wrong site
- The agent uses the primary site unless you name another in the prompt. The live tools also accept a connection_id.
- Elementor text is missing
- Elementor page text is reachable only where the post type exposes meta._elementor_data. Otherwise edit it in wp-admin.
- The WordPress.com option stops working after November 30, 2026
- That date ends the free MCP access for free WordPress.com sites and for Jetpack sites without a Jetpack AI or Complete plan. WordPress.com's pages say paid WordPress.com plans include MCP access at no extra cost.
- Cannot have more than 128 tools per request.
- VS Code allows 128 enabled tools in one chat request. Deselect tools or whole MCP servers in the tools picker of the Chat view until the count drops.
Terms on this page
- Agent Customizations editor
- The VS Code screen opened by Chat: Open Customizations. Its MCP Servers page adds, lists and manages servers.
- Copilot Global
- The personal MCP destination in VS Code, ~/.copilot/mcp-config.json, read in every workspace.
- Application password
- A 24-character password that WordPress generates on a user's profile for programs that use the REST API. It can be revoked on its own and cannot 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.
- Role and capability
- A role such as Administrator, Editor, Author, Contributor or Subscriber is a set of capabilities, and a connection can do only what its user's role allows.
- Self-hosted and WordPress.com
- A self-hosted site runs WordPress on your own host. A WordPress.com site runs on Automattic's hosting. A Jetpack connection links a self-hosted site to a WordPress.com account.
- Abilities API
- A WordPress API in versions 6.9 and newer where core and plugins register what they can do. The MCP Adapter turns public abilities into MCP tools.
Sources: VS Code MCP servers, VS Code MCP configuration reference, Application Passwords integration guide, WordPress roles and capabilities, WordPress REST API posts reference, Jetpack JSON API, Introducing the Abilities API. Checked November 14, 2026.
Frequently asked questions
How do I connect VS Code to WordPress?
Connect your site in Ryze AI under Integrations, with an application password for a self-hosted site or a WordPress.com sign-in. In VS Code, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers, choose Add Server, pick HTTP, enter https://connector.get-ryze.ai/mcp and the server ID ryze, trust the server and finish the Ryze AI sign-in.
Is there a WordPress MCP server for VS Code?
Yes, several. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 9 WordPress tools for your connected site. WordPress.com runs its own server at https://public-api.wordpress.com/wpcom/v2/mcp/v1 and names VS Code on its pages. The MCP Adapter plugin adds an MCP endpoint to a self-hosted site, and Composio, Zapier and open-source servers are further options.
What is the WordPress MCP server URL for VS Code?
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 at https://public-api.wordpress.com/wpcom/v2/mcp/v1. The MCP Adapter plugin serves /wp-json/mcp/mcp-adapter-default-server on your own site.
Which WordPress server should I use in VS Code?
For posts, pages, media and SEO fields through one address, use the Ryze AI connector, which needs a Ryze AI plan. For account-level work such as domains on WordPress.com, use WordPress.com's server. To expose custom abilities from your own plugin code, use the MCP Adapter.
Do I need a WordPress.com account to connect VS Code?
No. A self-hosted site connects to Ryze AI with the site URL, a WordPress username and an application password. A WordPress.com or Jetpack site connects with a WordPress.com sign-in instead. Plugin installs, the Yoast and Rank Math bridges and head code work only on the self-hosted kind.
Is there a Copilot connector for WordPress?
Not as of November 14, 2026, when GitHub's supported connectors page named 26 services and WordPress was not one of them. That list is a public preview. For now, add WordPress by server address, such as the Ryze AI connector.
Which Copilot plan do I need?
Any plan. GitHub's plans tables include MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise, and GitHub's MCP article asks for VS Code 1.99 or later. Copilot Free, Pro, Pro+ and Max are outside the MCP policy. On Business or Enterprise through an organization, an administrator must enable the MCP servers in Copilot policy, which is off by default.
Can Copilot Chat edit my WordPress posts and pages?
Yes. Through Ryze AI, Copilot Chat can create and update posts, pages, media, categories, tags and custom post types with the write tool, and make targeted text edits with the edit tool. New VS Code sessions start on Manual permissions, so a call that is not auto-approved shows its tool name and inputs first.
Can Copilot Chat delete WordPress content?
Only through the separate wordpress__delete tool, and only when the connected user's role allows it. WordPress keeps trashed posts and pages for 30 days by default. Allow all, Autopilot or a server-wide approval in Chat: Manage Tool Approval skips the check, so keep the ryze server on manual approval if you want to review deletes.
Can Copilot write Yoast or Rank Math fields?
On a self-hosted site, yes, after a one-time bridge. The Yoast and Rank Math bridge tools make the SEO title, meta description, focus keyword and related fields writable, and they need an Administrator and your explicit yes before the Code Snippets plugin is installed. On WordPress.com those fields are edited in wp-admin.
How do AI tools publish articles to WordPress?
Ryze AI publishes Content Plan articles to your WordPress site as posts, with an optional Author and Category chosen after connecting. SEO Starter allows up to 90 articles per billing cycle and up to 3 a weekday. Publishing mode in SEO > Preferences > Publishing is Automatic by default or Manual.
Which AI SEO tools connect directly to WordPress?
Ryze AI connects to self-hosted WordPress sites with an application password and to WordPress.com or Jetpack sites with a sign-in, then works on them from the Ryze AI chat, Claude, ChatGPT and VS Code. On self-hosted sites it can also write Yoast and Rank Math fields after the bridge step.
Can I connect more than one WordPress site?
Yes. Several sites can be connected in one workspace with Add one more account. One is the primary and the agent uses it unless you name another, and the live tools accept a connection_id.
Why do the WordPress tools not show up in VS Code?
If you connected WordPress in Ryze AI after adding the server, remove the ryze server, add it again and start a new chat. Also confirm that you trusted the server and finished the Ryze AI sign-in, which are separate steps, and expand a tool call to see which server answered.
Which config file should I use?
For new setups use the portable format: ~/.copilot/mcp-config.json or .mcp.json at the workspace root, with the key mcpServers. The .vscode/mcp.json file with the key servers belongs to the Local harness, which VS Code 1.146 deprecated, with removal announced for February 2027.
How much does it cost to connect VS Code 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 and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect WordPress from VS Code?
In Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. To end WordPress access itself, disconnect the site in Ryze AI and, on a self-hosted site, revoke the application password on the user's profile page.