By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Antigravity to WordPress is the Ryze AI connector. Connect your site in Ryze AI with an application password (self-hosted) or a WordPress.com sign-in, then give Antigravity's mcp_config.json a ryze entry whose serverUrl is https://connector.get-ryze.ai/mcp and finish the Ryze AI sign-in. The agent then has 9 WordPress tools: 2 that read, 6 that write and 1 that deletes.
- In Ryze AI open Integrations, click Connect on the WordPress card and enter your site details or sign in on WordPress.com
- In Antigravity open MCP Servers, Manage MCP Servers, View raw config and add the ryze entry
- Complete the Ryze AI sign-in and click Allow connection
- Start a new agent chat and ask for your 10 newest posts with their status
Antigravity to WordPress at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that Antigravity reaches through one serverUrl entry, with nothing to install on your site or keep running |
| Server address | https://connector.get-ryze.ai/mcp |
| Where the entry goes | mcp_config.json, either ~/.gemini/config/mcp_config.json for every project or .agents/mcp_config.json inside one workspace. The IDE, the App and the CLI read the same format |
| Sign-in | WordPress: an application password for a self-hosted site, or one-click sign-in on WordPress.com. Antigravity: OAuth 2.0 with PKCE in the browser, with no client ID to type because the connector offers dynamic client registration. The App adds an Authenticate button and a pasted code |
| WordPress tools | 9 in all: 2 read, 6 write and 1 delete, each with an optional connection_id |
| Can it change the site | Yes. The agent can create, update and delete posts, pages, media, categories, tags and custom post types. Antigravity keeps any MCP tool without a rule in Ask mode, so each call waits for your click by default |
| Other data in the same chat | Other platforms connected in the same Ryze AI workspace are served from the same address |
| Antigravity plan needed | None is named. Google's MCP page lists no plan, and the plans page gives every plan all product features |
| Ryze AI price | Adding the connector costs nothing. The WordPress tools need an active plan or trial: SEO Starter is $129 per month with a 3-day free trial |
| WordPress's own option for Antigravity | The WordPress.com MCP server. WordPress.com's support page names Antigravity among its one-click agents. It reaches sites on a WordPress.com account and Jetpack-connected sites |
| Last tested | The connector's WordPress tools on November 14, 2026. Antigravity's documentation on November 15, 2026. Nothing was run inside Antigravity |
Before you start
- An Antigravity install. Google's MCP documentation names no plan for using MCP servers. Business and enterprise accounts use the App, the CLI or an IDE extension, because the standalone IDE is not supported for enterprise deployments, and an admin may need to allow MCP servers in the Gemini Enterprise settings.
- A WordPress user whose role fits the job. On a self-hosted site that is the WordPress username you sign in with, plus an application password, which WordPress offers by default to all users on HTTPS sites. Plugin installs, the SEO plugin bridges and head code need an administrator. A WordPress.com or Jetpack site signs in on WordPress.com instead.
- 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 WordPress site. Adding the connector is free, but the WordPress tools need any active Ryze AI plan or trial.
How to connect Antigravity to WordPress
Two steps happen in Ryze AI and WordPress, two in Antigravity, and the last is your first prompt. The connector URL is the same for every user.
Connect your WordPress site in Ryze AI
Create a Ryze AI account or sign in, open Integrations, find the WordPress card and click Connect. For a self-hosted site, first create an application password in WP Admin under Users, Profile, Application Passwords, then pick the Self-hosted site tab and enter the Site URL, your username and that password. For a WordPress.com or Jetpack site, pick the WordPress.com / Jetpack tab and sign in on WordPress.com.
Choose the author and category for new posts (optional)
Click View on the WordPress card to choose the Author and Category that new posts use, then click Save. To add another site later, click View, then Add one more account.
Add the Ryze AI server to Antigravity
In the Antigravity IDE click the ... menu at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers and View raw config. In the App choose Customizations, Installed, then Copy Config File Path under MCP Servers and open that file. Under mcpServers add an entry named ryze with the serverUrl shown below and save.
{ "mcpServers": { "ryze": { "serverUrl": "https://connector.get-ryze.ai/mcp" } } }Sign in from Antigravity
Antigravity runs OAuth 2.0 with PKCE on its own for servers that support dynamic client registration, so there is no client ID or secret to enter. Complete the Ryze AI sign-in in the browser and click Allow connection. In the App, click Authenticate next to ryze, copy the authorization code from the browser, paste it into Enter authorization code and click Submit.
Ask your first question in Antigravity
Start a new agent chat, approve the tool call when Antigravity asks, and try: List my 10 newest posts with their title, status and date.
The Ryze AI help center page for WordPress covers the WordPress side of the connection. Antigravity does not have its own Ryze AI help page; the Ryze AI in Antigravity page and the Ryze AI developers page cover the client side.
Sources: Antigravity MCP documentation, WordPress REST API authentication, Ryze AI WordPress guide. Checked November 15, 2026 and November 14, 2026.
IDE, App, CLI and mcp_config.json
mcp_config.json
Save this as ~/.gemini/config/mcp_config.json for every project, or as .agents/mcp_config.json inside one workspace. Antigravity accepts remote servers through serverUrl (url works as another name) and handles the OAuth sign-in itself.
{
"mcpServers": {
"ryze": {
"serverUrl": "https://connector.get-ryze.ai/mcp"
}
}
}The App's Add MCP Server (+) button opens a searchable catalog with no field for an address, so a custom server like this one is written into mcp_config.json by hand. Remote servers have to speak Streamable HTTP: Google's docs rule out the legacy HTTP+SSE transport and the httpUrl key. Antigravity's OAuth redirect URI is https://antigravity.google/oauth-callback.
Antigravity IDE
Click the ... menu at the top of the agent side panel and choose MCP Servers. Custom servers are added under Manage MCP Servers, then View raw config. The IDE also has a built-in MCP Store with an Install button per server; Ryze AI is not on the store list in Google's MCP page, which is why the entry is written by hand. Google's page does not describe how sign-in starts in the IDE.
Antigravity App
Open Customizations in the sidebar, then Installed, and scroll to MCP Servers. Click Copy Config File Path, add the ryze entry to that file, then click Authenticate next to ryze. Finish the sign-in in the browser, copy the authorization code, paste it into Enter authorization code and click Submit. The server then reconnects on its own.
In the App, if Customizations > Installed lists plugins only and has no MCP Servers section, you are in the Knowledge Work layout, which personal accounts can choose since App v2.30.0. Switch to Software Engineering under Settings > General > Interface Layout and the section and its Authenticate button appear.
Antigravity CLI
In the Antigravity CLI, put the same ryze entry in either file, then type /mcp in the prompt panel to open the MCP Manager, check the server status and reload the configuration. Google's MCP page does not describe how the CLI starts an OAuth sign-in, so this guide gives no CLI sign-in steps. The CLI changelog also lists mcp add, remove, list, enable and disable subcommands, whose exact syntax is not on Google's pages.
Editor extensions and imports
Antigravity's extensions for other editors read the same file. Google's Visual Studio extension page describes MCP setup with the MCP Store or mcp_config.json, and its changelog says the JetBrains, Zed and Xcode extensions load servers from the same config folder. The VS Code extension page does not mention MCP, so check it before relying on that route.
If you already use Claude Code, Codex, Cursor or Gemini CLI, the App can import MCP servers from them at first launch in the Software Engineering role. That is a way to carry over an existing ryze entry, not a step this guide requires.
Antigravity and MCP: the facts in one table
| Topic | What Google's documentation says |
|---|---|
| Config files | ~/.gemini/config/mcp_config.json for every project, <workspace>/.agents/mcp_config.json for one workspace. Enabled plugins can add servers from their own mcp_config.json |
| Remote servers | Streamable HTTP only, through serverUrl (url also works). Legacy HTTP+SSE and httpUrl are not supported |
| Local servers | stdio, through command |
| Where servers are managed | IDE: ... menu in the agent side panel, then MCP Servers. App: Customizations > Installed > MCP Servers. CLI: /mcp |
| Sign-in | OAuth 2.0 with PKCE. Client order: oauth.clientId from the file, then a Client ID Metadata Document, then dynamic client registration. Ryze AI offers dynamic client registration and no metadata document |
| Token storage | ~/.gemini/antigravity/mcp_oauth_tokens.json, refreshed automatically |
| Tool approval | An MCP tool with no rule runs in Ask mode. Allow one tool with mcp(server/tool), a whole server with mcp(server/*) or every MCP tool with mcp(*). Deny beats Ask beats Allow |
| Tool loading | Lazy by default: schemas are cached on disk and the agent reads one when it needs it. A tool set to eager is registered up front |
| Tool filters | enabledTools and disabledTools per server, and disabled to pause a server without removing it |
| Timeouts | 5 minutes to connect and list tools, 3 minutes per tool call. timeoutSeconds replaces both |
| Admin controls | Gemini Enterprise has an MCP servers setting and an allowed server configuration under AI developer tools. The App added admin MCP allowlists in v2.5.0 |
Sources: Antigravity MCP documentation, Antigravity changelog, Antigravity Visual Studio extension, Gemini Enterprise AI developer tools settings. Checked November 15, 2026.
Claude and ChatGPT
The same URL works in other MCP clients. WordPress is connected once in Ryze AI, so nothing changes on the WordPress side.
Claude
Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, pick the workspaces and start a new chat. The Claude guide for WordPress is linked below.
ChatGPT
Add the same URL as an app under Settings > Apps, pick the workspaces and start a new chat. If the connector was added before WordPress was connected in Ryze AI, remove and re-add it so the tool list refreshes. The ChatGPT guide for WordPress is linked below.
WordPress access and roles
Two sign-ins are involved: WordPress for site access and Ryze AI for the connector. Three things decide what Antigravity can reach.
- Which site
- The site you connected in Ryze AI. Several 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.
- Which connection type
- A self-hosted site connects with an application password and acts with that WordPress user's own access. A WordPress.com or Jetpack site connects with one-click sign-in on WordPress.com and reaches only the core /wp/v2 routes.
- What Antigravity asks first
- Antigravity runs an MCP tool with no rule in Ask mode, so a post update waits for your click until you allow the tool in the policy configuration.
Access behind each action
A self-hosted connection has no app scopes. An application password acts with its WordPress user's role, so the role decides what the agent can do. WordPress.com's own sign-in has scopes, and Ryze AI does not publish which one it requests, so this guide names none.
| Action in Ryze AI | WordPress access |
|---|---|
| Read posts, pages, media, categories, tags, users, plugins and custom post types | Any connected user, within what that user's role may see. Reading plugins needs the activate_plugins capability |
| Create and update posts, pages, media, categories and tags | A user whose role allows it, through the write and edit tools |
| Delete a post or page | A user whose role allows deleting it, through the separate delete tool |
| Install a plugin, enable the Yoast SEO or Rank Math bridge, add head code | A self-hosted connection made with an administrator's application password |
| Any of those four on WordPress.com | Not available. Plugin installs, the bridges and head code do not work on WordPress.com connections |
What each WordPress role covers
WordPress roles are sets of capabilities, and a connection can do only what its user's role allows. This is what WordPress's roles documentation says each role may do, and what that means for the agent.
| Role | What WordPress says it can do | With Ryze AI |
|---|---|---|
| Administrator | All administration features within a single site, including activate_plugins. On single-site installs also installing and deleting plugins and unfiltered_html | Everything in the tool list, including plugin installs, the Yoast and Rank Math bridges and head code on a self-hosted site |
| Editor | Publish and manage posts, including other users' posts | Content reads and writes, including posts by other authors |
| Author | Publish and manage their own posts | Content work limited to the user's own posts |
| Contributor | Write and manage their own posts but cannot publish them | Drafts only. A publish request is refused by WordPress |
| Subscriber | Manage their own profile, with only the read capability | Too low for content work |
Not included: plugin installs, SEO bridges and head code on WordPress.com connections, plugin routes such as /yoast/v1 there, plugins from uploaded zip files or URLs (only wordpress.org directory plugins), robots.txt changes, and 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 silently dropped by WordPress.
Sources: WordPress roles and capabilities, Application Passwords integration guide, WordPress.com OAuth2. Checked November 14, 2026.
Removing access
To remove access, disconnect the site from the WordPress card in Ryze AI, or revoke the application password on the user's profile in WP Admin, where existing passwords can be viewed and revoked. In Antigravity, disable or delete the ryze server from Customizations > Installed > MCP Servers, or remove its entry from mcp_config.json.
What Antigravity 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 you can approve them separately.
| Tool | Type | What it does | Where it works |
|---|---|---|---|
| wordpress__read | Read | Runs a read-only GET request on the connected site's REST API, covering posts, pages, media, categories, tags, users, plugins and custom post types. | Self-hosted and WordPress.com |
| 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. | Self-hosted and WordPress.com |
| wordpress__write | Write | Runs a request that creates or updates resources (POST, PUT or PATCH), such as creating a post or updating a page. | Self-hosted and WordPress.com |
| wordpress__edit_content | Write | Makes find-and-replace edits to a text field such as post or page content, an excerpt or a title, and writes it back without resending the whole content. | Self-hosted and WordPress.com |
| wordpress__installPlugin | Write | Installs and activates a plugin from the wordpress.org directory. | Self-hosted, administrator |
| wordpress__enableYoastRestBridge | Write | One-time setup that makes the Yoast SEO title, meta description, focus keyword, canonical and noindex fields writable through the REST API, using a Code Snippets plugin snippet. | Self-hosted, administrator |
| wordpress__enableRankMathRestBridge | Write | One-time setup that makes the Rank Math title, description, canonical URL and focus keyword fields writable through the REST API, using a Code Snippets plugin snippet. | Self-hosted, administrator |
| wordpress__addHeadCode | Write | Adds a block of HTML inside the head of every page, such as a tracking snippet, pixel or verification tag, through a Code Snippets plugin snippet. | Self-hosted, administrator |
| wordpress__delete | Delete | Runs a DELETE request, for example to delete a post. | Self-hosted and WordPress.com |
Some limits apply in every client, Antigravity included. A security plugin, WAF or host that blocks /wp-json requests stops the connection until requests are allowlisted. A plugin install can crash a site, so approve each one. The Yoast bridge, the Rank Math bridge and head code default to installIfMissing false, and their descriptions require your explicit yes in chat before the Code Snippets plugin is installed.
Antigravity runs an MCP tool with no rule in Ask mode, so each call needs your approval until you allow it. Keep that default if you want to review every post edit, or leave the delete tool and the plugin install tool out of any allow rule. Separately, the Ryze AI chat has its own Tool approvals picker that starts on Skip all approvals; you can choose Approve write & delete or Manual approve there. Article publishing from Content Plan follows Publishing mode in SEO > Preferences > Publishing: Automatic (the default) or Manual.
Limits in numbers
| Limit | Number |
|---|---|
| Page size | per_page accepts 1 to 100, so one request returns at most 100 records. The posts reference gives a default of 10. Larger sets take several requests with page or offset. |
| Paging totals | Every paginated response carries X-WP-Total and X-WP-TotalPages headers. The read tool returned total and totalPages fields in the test. |
| Field selection | _fields limits a response to named fields. Nested fields work since WordPress 5.3. |
| Request quota | The REST API handbook pages and the WordPress.com MCP pages give no request quota or rate limit figure. That is the absence of a figure on those pages, not a statement that no limit exists. |
| Application password | 24 characters, upper-case, lower-case and numeric only. Available by default to all users on HTTPS sites. It cannot be used to log in at wp-login.php. |
| Trash | Trashed posts, pages, attachments and comments are permanently deleted after 30 days by default. On WordPress.com, deleted posts and pages are recoverable for 30 days and deleted media, categories and tags are permanent. |
| Revisions | On by default and can be capped or turned off. Autosave runs every 60 seconds by default. |
| Tool inputs in Ryze AI | path up to 2,000 characters. search_content: pattern up to 500 characters, context_lines 0 to 10, default 2. edit_content: 1 to 50 edits per call, old_string up to 20,000 characters, new_string up to 100,000. addHeadCode: html up to 8,192 characters. installPlugin: slug up to 128 characters. |
| Antigravity timeouts | 5 minutes to connect and list tools and 3 minutes per tool call, unless timeoutSeconds changes them. |
| Antigravity tool output | A lazy-loaded MCP tool returns up to 10 KB directly to the agent in the CLI since v1.4.7. |
Sources: WordPress REST API pagination, REST API global parameters, wp-config options, Antigravity MCP documentation. Checked November 14, 2026 and November 15, 2026.
What the connector returned, tested
Each row is one call to wordpress__read through the Ryze AI connector on November 14, 2026, on a WordPress.com connection, called from Claude Code. All were read-only. No call returned post, page, media or user content.
| What was asked | What came back |
|---|---|
| The post types of the site (/wp/v2/types) | Worked. 18 post types |
| The taxonomies of the site (/wp/v2/taxonomies) | Worked. 6 taxonomies |
| A post ID that does not exist | Refused as not_found with the message Invalid post ID. |
| A route that does not exist | Refused as not_found with the message No route was found matching the URL and request method. |
| A post type that does not exist | Refused as not_found with the message Invalid post type. |
| Posts with per_page 101 | Refused by WordPress with HTTP 400, code rest_invalid_param, Invalid parameter(s): per_page |
| Posts sorted by a field that does not exist | Refused with HTTP 400, code rest_invalid_param, Invalid parameter(s): orderby |
| A read sent with a body | Refused by the connector before any request, as invalid_arguments |
| A plugin route (/yoast/v1) on the WordPress.com connection | Refused as not_found. WordPress.com connections reach only /wp/v2 routes |
First 3 prompts to run, with a real result
1. Map the content types and taxonomies of the site
Read the post types and taxonomies registered on my WordPress site and list their slugs. Tell me which post types are custom.
Tools used: wordpress__read
What comes back: A list of post type and taxonomy slugs from the REST API. Nothing is changed.
A real result: This is what the connector returned for the two reads behind this prompt on November 14, 2026. The site was a WordPress.com test site. The slugs are the site's own post types and taxonomies, not content.
| Read | Count | Slugs returned |
|---|---|---|
| Post types | 18 | post, page, attachment, nav_menu_item, wp_block, wp_template, wp_template_part, wp_global_styles, wp_navigation, wp_font_family, wp_font_face, feedback, jetpack_form, wp_guideline, jp_pay_order, jp_pay_product, wp_knowledge, jp_act_log_event |
| Taxonomies | 6 | category, post_tag, nav_menu, wp_pattern_category, wp_guideline_type, wp_knowledge_type |
Returned by wordpress__read, one call each. Nothing on the site was changed. Several of these types come from Jetpack and block themes, so a self-hosted site will list different ones.
2. Fix a phrase inside a long post
Search 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, then a single in-place edit to that text field once you approve the tool call in Antigravity.
3. Update a post title and status
Change the title of the post with ID 123 to the text I give you, keep it as a draft, and confirm the new values after the change.
Tools used: wordpress__read, wordpress__write
What comes back: A post update through a write request, then a read of the fields so you can compare them with what you asked for.
The table under the first prompt is a real result from a test site. The second and third prompts change data, so this page describes what comes back and shows no result for them. Replace the ID and the phrases with your own.
The requests behind the results
Antigravity writes the request itself. The read tool takes a path relative to /wp-json, plus an optional query and a body for writes. These are the two paths that produced the results on this page. Ask Antigravity to run one with wordpress__read.
The post types of the site:
path: /wp/v2/typesThe taxonomies of the site:
path: /wp/v2/taxonomiesPaging through posts:
path: /wp/v2/posts
query: per_page=100&page=2&_fields=id,title,statusPaging uses per_page up to 100 and page. _fields trims each record to the fields you name. This paging request shows the documented parameters and was not run in the test.
10 jobs to hand to Antigravity
Ten jobs to hand to Antigravity, each matched to the tool it uses. Only the first was run in the test, as a read of the post types. The rest follow the tool descriptions and WordPress's REST API reference.
| Job | Ask Antigravity | Tool | Works on the default connection |
|---|---|---|---|
| List recent posts | List my 10 newest posts with title, status, date and category. | wordpress__read | Yes, up to 100 items per request |
| Content type inventory | List the post types of my site and the REST route of each. | wordpress__read | Yes. Run in the test |
| Find a phrase | Search the post with ID 123 for a phrase and show the matching lines. | 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, after you approve the call in Antigravity |
| Create a draft | Create a draft page with the title and text I give you. | wordpress__write | Yes, after you approve the call |
| Retitle and recategorize | Change a post's title, excerpt, status, categories or tags. | wordpress__write | Yes. It also creates and renames categories and tags |
| Image alt text | Update the alt text and captions of these images in the media library. | wordpress__write | Yes |
| Delete a post | Delete the post with ID 123. | wordpress__delete | Yes. Set this tool to need approval |
| Yoast SEO fields | Set the Yoast SEO title and meta description of these posts. | wordpress__enableYoastRestBridge, then wordpress__write | Self-hosted with an administrator only. You must say yes before the Code Snippets plugin is installed |
| Tracking or verification tag | Add this verification tag to the head of every page. | wordpress__addHeadCode | Self-hosted with an administrator only |
7 ways to connect Antigravity to WordPress
Seven ways can give the Antigravity agent access to a WordPress site. This guide treats the first, the Ryze AI connector, as the main way: Antigravity stores one serverUrl entry, and the WordPress sign-in happens once inside Ryze AI, with no plugin to install on your site. The other six were read on their own pages on November 14, 2026, and none was installed for this guide. The setup column shows how each would go into Antigravity.
| Way | Runs where | Setup in Antigravity | What it reaches | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI. One address for Antigravity, Claude, ChatGPT and other MCP clients | A ryze entry with serverUrl https://connector.get-ryze.ai/mcp in mcp_config.json, then the browser sign-in. In the App, Authenticate and a pasted code | Posts, pages, media, categories, tags, users, plugins and custom post types, to read and to change. On self-hosted sites also Yoast and Rank Math fields, head code and directory plugins. Deletes go through a separate tool | Free to add. The tools need an active plan or trial: 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 support page names Antigravity with a one-click option under Preferences, AI and MCP in your account. It does not say what that option sets up, so a serverUrl entry for the address is an adaptation that was not checked | Read and write across the sites of a WordPress.com account, grouped as content authoring, site editing, site, account, user management, plugin management and more. Jetpack-connected self-hosted sites use the same server | 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 your site, at /wp-json/mcp/mcp-adapter-default-server | A serverUrl entry pointing at the endpoint, with a headers object for an Authorization header built from an application password. Antigravity supports headers, but this pairing was not checked | Only the abilities the site has registered and marked public. The default server exposes 3 meta-tools | Free, GPL-2.0-or-later. Version 0.7.1 on wordpress.org, which needs WordPress 6.9 and PHP 7.4 |
| AI Engine by Meow Apps | A plugin on your site | The plugin page says Claude and ChatGPT connect with OAuth. It does not name Antigravity | More than 140 tools as the vendor states it, covering content, media, taxonomies, menus and SEO plugin fields | The MCP server is in the free plugin. Pro starts at $59 per year |
| Zapier MCP | Hosted by Zapier | Add the MCP URL Zapier generates as a serverUrl entry and sign in. Zapier's client list includes Antigravity, but its per-client steps were not opened | The WordPress actions of your Zapier account, such as Create Post, Update Post, Upload Media and API Request. The page does not say which WordPress site types are covered | Each successful tool call uses two tasks from your Zapier plan |
| Composio | Hosted by Composio | Composio's page describes an SDK setup that returns an MCP address and headers. Antigravity is not named, so a serverUrl entry is an adaptation | 26 tools for the WordPress.com toolkit: drafts, posts, pages, media, menus, templates, site settings and stats. No self-hosted toolkit page was found | The free plan stops at 10,000 tool calls a month on Composio's pricing page. Standard is $18 per seat per month |
| InstaWP/mcp-wp, open source | A Node process you run | A command entry that runs npx -y @instawp/mcp-wp with your site URL, username and an application password. Antigravity supports stdio servers through command. Needs Node.js 18 or higher | Tool groups for multi-site management, posts, pages, custom post types and taxonomies | Free, GPL-3.0-or-later. 100 GitHub stars, last update September 10, 2026 |
Four WordPress options that do not fit this job
- WordPress 7.0 AI Client and Connectors screen. They let plugins on a site call AI providers. They point from WordPress out to a model and are not a way for an assistant such as Antigravity to reach a site.
- WordPress Agent Skills. The WordPress/agent-skills repository holds 19 instruction bundles for WordPress development, with a global install path for Antigravity. They teach the agent patterns and give no access to a site or its data.
- WordPress Studio MCP and WordPress Playground MCP. Studio works on local Studio sites and the account's WordPress.com sites. Playground works on an instance in a browser tab. Neither reaches a live self-hosted site.
- Automattic/wordpress-mcp. The earlier plugin is archived on GitHub, and WordPress.com says it is being retired in favor of the MCP Adapter.
Which one to pick
Ryze AI is the best way to connect Antigravity to WordPress for editing posts, pages and media and, on self-hosted sites, writing Yoast and Rank Math fields, with one caveat: WordPress.com connections cannot install plugins, enable the SEO bridges or add head code, and the WordPress tools need a paid Ryze AI plan or trial. If your site is on WordPress.com or connected through Jetpack and you want no extra subscription, the WordPress.com MCP server is the cheaper first thing to try, since paid WordPress.com plans include it. The MCP Adapter suits a developer who wants to choose exactly which abilities the site exposes. Zapier fits a team that already runs its WordPress work there, and the open-source server fits someone who wants a local process and an application password of their own.
Sources: WordPress.com MCP developer page, WordPress.com MCP support page, MCP Adapter plugin, AI Engine plugin, Zapier MCP for WordPress, Composio WordPress.com toolkit, Composio pricing, InstaWP/mcp-wp, WordPress/agent-skills, Antigravity MCP documentation, Ryze AI WordPress guide. Checked November 14, 2026, November 15, 2026 and, for the WordPress.com support page, November 19, 2026.
WordPress, Antigravity and MCP: dates that matter
| Date | What happened |
|---|---|
| October 7, 2025 | WordPress.com announced MCP support, read-only at first, with write access to follow. |
| January 22, 2026 | WordPress.com added OAuth 2.1 for MCP connections. |
| March 20, 2026 | WordPress.com MCP gained write abilities across posts, pages, comments, categories, tags and media. |
| May 19, 2026 | Antigravity 2.0, the Antigravity App, and the Antigravity CLI launched. Google moved Gemini CLI users to Antigravity CLI. |
| June 3, 2026 | Antigravity CLI v1.0.5 began to accept url in mcp_config.json. The App followed with v2.1.4 on June 11. |
| October 2, 2026 | The MCP Adapter plugin was added to the wordpress.org plugin directory with version 0.7.0. |
| October 29, 2026 | Plugin Marketplace launched in the Antigravity App and CLI. |
| November 3, 2026 | WordPress.com opened MCP access to free sites for a limited time. |
| November 13, 2026 | Antigravity CLI v1.5.8 stopped signing out remote OAuth servers without a client secret when the access token expires. |
| November 19, 2026 | WordPress.com's support page, opened for this guide, lists Antigravity among the agents with a one-click option under AI and MCP. |
| November 30, 2026 | Last day of MCP access for free WordPress.com sites and for Jetpack-connected sites without a Jetpack AI or Complete plan. This row goes stale on December 1. |
Sources: WordPress.com MCP announcement, OAuth 2.1 post, write abilities post, free sites post, MCP Adapter plugin page, Antigravity changelog, Plugin Marketplace post, Gemini CLI transition post. Checked November 14, 2026, November 15, 2026 and November 19, 2026.
How this guide was tested
The connector's WordPress tools were checked through the Ryze AI connector on November 14, 2026, and the connector's sign-in details on November 15, 2026. The table lists what was run and what came back.
| What was run | What came back |
|---|---|
| The connector address, without signing in | A request to https://connector.get-ryze.ai/mcp came back as HTTP 401 with a WWW-Authenticate header that points to the sign-in details. That answer is what makes an MCP client open a browser sign-in. |
| The sign-in details | Both protected resource files loaded. The one for the connector path names the server URL as its resource, which Antigravity requires to match. The authorization server lists a registration endpoint, so Antigravity would use dynamic client registration. It also lists PKCE with S256, the authorization code and refresh token grants, and the scopes mcp:read and mcp:write. |
| The tool list | All 9 WordPress tool names loaded by name from the live connector, each with a definition. They are in the tools table above. |
| wordpress__read on a WordPress.com connection | Nine read calls: two worked and seven were refused on purpose. The table of tested reads above lists them. |
| Limits seen | Responses carried total and totalPages fields. The per_page refusal confirmed the maximum of 100. No rate limit or quota figure appeared in any response. |
| Google's pages | The Antigravity MCP documentation, changelog and related pages were downloaded on November 15, 2026 and each fact on this page was matched to its text. |
Not run for this page: any step inside Antigravity, because no Antigravity App, CLI or IDE was used and no Ryze AI sign-in was completed from it. Those steps follow Google's MCP documentation as it read on November 15, 2026, and Google does not describe CLI or IDE sign-in steps. The reads ran from Claude Code on a WordPress.com connection, which reaches the same server and the same 9 tools. No self-hosted connection was tested, so no permission error (401 or 403) was seen. No read returned site content, and wordpress__search_content was not run. The write, edit, delete, plugin install, bridge and head code tools were not run, because they change a site.
Antigravity and WordPress 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. If Antigravity shows one of them, this is what it means. The last two rows come from the Ryze AI tool definitions and were not triggered in the test.
| Message | What it means | What to do |
|---|---|---|
| Invalid post ID. | No post with that ID exists on the connected site. | 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 is also what a plugin namespace such as /yoast/v1 returns on a WordPress.com connection. | Check the path against /wp/v2/types. Plugin routes need a self-hosted connection. |
| Invalid post type. | The post type slug is not registered on the site. | Read /wp/v2/types and use a slug from it. |
| Invalid parameter(s): per_page | per_page was 101 and WordPress accepts 1 to 100. The code is rest_invalid_param with status 400. | Ask for 100 or fewer per page and page through the rest. |
| Invalid parameter(s): orderby | 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. The read tool rejects it before contacting WordPress and tells you to pass filters in query instead. | Put the filters in query. |
| Sorry, you are not allowed to ... (rest_forbidden or rest_cannot_*, status 403) | The connected user's role is too low for that action. Seen in the tool definitions only. | Reconnect with an administrator's application password, or ask for a job the role allows. |
| rest_not_logged_in (status 401) | The credential was revoked, for example the application password was deleted. Seen in the tool definitions only. | Create a new application password and reconnect the site in Ryze AI. |
Other problems
- The WordPress tools do not appear in Antigravity
- If WordPress was connected in Ryze AI after the server was added, restart ryze from the MCP Servers menu or reload the configuration with /mcp in the CLI, then start a new chat. Antigravity loads MCP tool schemas lazily and caches them on disk.
- Antigravity never asks me to sign in
- In the App, open Customizations > Installed > MCP Servers and click Authenticate next to ryze. If the section is missing, switch the interface layout from Knowledge Work to Software Engineering. Google gives no sign-in steps for the CLI or the IDE.
- The server never finishes connecting
- Antigravity waits up to 5 minutes for a server to connect and list its tools. Check that mcp_config.json is valid JSON, that the entry uses serverUrl (or url) and not httpUrl, and reload the configuration.
- Ryze AI does not accept the site details
- Use the site's https address and the username you sign in to wp-admin with, plus an application password from Users > Profile. The application password is shown once, so create a new one if you lost it.
- The connection fails on a site with a security plugin
- A security plugin, WAF or host that blocks /wp-json requests stops the connection. Allowlist the requests and connect again.
- An SEO plugin field change did not stick
- Yoast and Rank Math fields sent through the plain REST API are silently dropped. On a self-hosted site, ask for the one-time bridge first and say yes in chat when asked. On WordPress.com, edit those fields in wp-admin.
- Plugin install, bridge or head code fails
- These need a self-hosted connection made with an administrator's application password. They do not work on WordPress.com connections.
- Elementor text is not reachable
- Elementor page text is reachable only where the post type exposes meta._elementor_data. Otherwise edit it in wp-admin.
- The tools reply that a subscription is required
- The WordPress tools need an active Ryze AI plan or free trial. Start the trial, then retry.
- The server is blocked on a work account
- Enterprise admins can control MCP servers in Gemini Enterprise settings under AI developer tools. Ask an admin to allow the Ryze AI server.
Terms on this page
- MCP
- The Model Context Protocol, an open standard for connecting AI applications to outside systems. Antigravity, Claude and ChatGPT support it.
- MCP server
- A program that offers tools over MCP. The Ryze AI connector is an MCP server that runs on Ryze AI's side, so there is nothing to install.
- mcp_config.json
- The file where Antigravity keeps its list of MCP servers. The IDE, the App and the CLI share the format.
- serverUrl
- The field that holds the address of a remote MCP server in mcp_config.json. The server has to use Streamable HTTP.
- REST API (wp-json)
- WordPress's built-in HTTP interface under /wp-json. Core content lives in the /wp/v2 routes.
- Application password
- A 24-character password WordPress generates on a user's profile for programs to use with the REST API. It can be revoked on its own and cannot log in at wp-login.php.
- Role and capability
- A role such as Administrator or Editor is a set of capabilities. A connection can do only what its user's role allows.
Source for MCP: modelcontextprotocol.io. Checked November 19, 2026.
Frequently asked questions
How do I connect Antigravity 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. Then add a ryze entry with the serverUrl https://connector.get-ryze.ai/mcp to Antigravity's mcp_config.json and complete the Ryze AI sign-in.
Is there a WordPress MCP server for Antigravity?
Yes. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 9 WordPress tools that work on your connected site. WordPress.com's own MCP server, the MCP Adapter plugin, AI Engine, Zapier and open-source servers are further options, and none of them was installed for this guide.
What is the WordPress MCP server URL for Antigravity?
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. A site running the MCP Adapter plugin has its own endpoint at /wp-json/mcp/mcp-adapter-default-server.
Does WordPress have an official MCP server?
Yes, two. WordPress.com runs a hosted MCP server for WordPress.com sites and Jetpack-connected sites, and WordPress.org publishes the MCP Adapter plugin, which exposes the abilities a self-hosted site registers. Jetpack uses the WordPress.com server and has no separate one.
Does WordPress.com's own connector work with Antigravity?
WordPress.com's support page names Antigravity among the agents with a one-click option under Preferences, AI and MCP, and it was opened for this guide on November 19, 2026. That route was not tested here, and the page does not say what the option sets up.
Which should I use, Ryze AI or the WordPress.com MCP server?
Use the WordPress.com server first if your site is on WordPress.com or Jetpack and you want no extra subscription, since paid WordPress.com plans include it. Use Ryze AI for a self-hosted site connected with an application password, where it can also write Yoast and Rank Math fields and add head code. Both can sit in mcp_config.json at the same time.
Can Antigravity edit my WordPress posts?
Yes. Through Ryze AI, Antigravity 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 connected user's role. It cannot change robots.txt or install uploaded plugin files.
Can Antigravity delete WordPress content?
Only through the separate wordpress__delete tool. Antigravity runs an MCP tool with no rule in Ask mode, so you can review each call or keep the delete tool out of any allow rule.
Which WordPress user or role do I need?
A user whose role allows the job: Editor or Author for post work, Administrator for plugin installs, the Yoast and Rank Math bridges and head code. On a self-hosted site you also need an application password, which WordPress offers by default on HTTPS sites. WordPress.com and Jetpack sites sign in on WordPress.com instead.
Which alt text tools integrate directly with WordPress instead of requiring a manual export?
Ryze AI is one: Antigravity can update the alt text and captions of images in the WordPress media library through the write tool, with no export step. It works on self-hosted and WordPress.com connections, and Antigravity asks before each change by default.
Are there AI SEO tools that integrate directly with WordPress?
Yes. Ryze AI publishes Content Plan articles to a connected WordPress site as posts, up to 3 a weekday and up to 90 per billing cycle on SEO Starter, with Publishing mode set to Automatic or Manual. Through the connector, Antigravity can also change post fields, and on self-hosted sites Yoast and Rank Math fields.
Which Antigravity plan do I need?
Google's MCP documentation names no plan, and its plans page gives every plan all product features. Business and enterprise accounts use the previous permission settings, and the standalone IDE is not supported for enterprise deployments.
Can I connect more than one WordPress site?
Yes. Several WordPress sites can be connected to one workspace with Add one more account, and the agent uses the primary site unless you name another one. An SEO plan covers one website, so check the plan before you rely on several.
Why do the WordPress tools not show up in Antigravity?
If you connected WordPress in Ryze AI after adding the server, restart the ryze server or reload the configuration, then start a new chat so the tool list refreshes. Antigravity caches MCP tool schemas on disk and loads them lazily.
How much does it cost to connect Antigravity 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 Antigravity?
Disconnect the site from the WordPress card in Ryze AI, or revoke the application password in WP Admin, or disable or delete the ryze server in Antigravity under Customizations > Installed > MCP Servers or in mcp_config.json.