MCP Servers Are Changing How We Build: WP Astro MCP and the Future of AI-Powered Development

WordPress MCP Adapter 0.7.1, the official Astro docs MCP server, Studio and the 2026-07-28 spec: setup steps, limits and common mistakes, checked 15 Nov 2026.

Diagram of an MCP hub connecting WordPress (MCP Adapter 0.7.1) and Astro (docs search) for the post on MCP servers for WordPress and Astro

An MCP server is a small program that tells an AI assistant what it can do on a system and lets it do it, using one shared protocol instead of a custom integration per tool. For WordPress and Astro work in November 2026, that means three different things: the official Astro docs server (read-only documentation search), the WordPress MCP Adapter 0.7.1 (a way to let an assistant act on a live site through the Abilities API), and project-specific servers such as our own WP Astro MCP, which moves content from WordPress into an Astro site. This guide, checked on 15 November 2026, covers what each one does, how to set it up, and where it stops.

The title still names WP Astro MCP because that is where this post started in March. The landscape around it has moved a lot since then, so most of what follows is about the official pieces. We are one of the teams that maintains a server in this space, so we mark where our view is not neutral.

What is the Astro MCP server?

The Astro MCP server is the official documentation server run by the Astro team at https://mcp.docs.astro.build/mcp. It lets an AI assistant search the current Astro docs instead of answering from stale training data. It is free, hosted remotely, and needs nothing installed on your machine. The Build with AI page in the Astro docs describes it as backed by the kapa.ai API and speaking Streamable HTTP.

We called the endpoint directly on 15 November 2026 and asked it for its tool list. It returns exactly one tool, search_astro_docs, which takes a single query string and searches the official docs. That is the whole surface.

It helps to be plain about what that means. The Astro docs server does not touch your project, run your build, read your config or deploy anything. It answers questions like “how do I configure a content collection with the glob loader” using the real documentation. It is a reference lookup, nothing more. If you were hoping for an “Astro MCP” that edits your Astro project, that does not exist as an official product; your coding assistant already edits files, and the docs server only keeps its API knowledge current.

How do I set up the Astro docs MCP server?

Add the URL to your client as a remote HTTP server. The Astro docs list the commands and config for each client, and the one most developers want is Claude Code.

Checked on 15 November 2026.

claude mcp add --transport http astro-docs https://mcp.docs.astro.build/mcp

For clients that read a JSON file, the documented manual entry for Streamable HTTP is:

{
  "mcpServers": {
    "Astro docs": {
      "type": "http",
      "url": "https://mcp.docs.astro.build/mcp"
    }
  }
}

If your client cannot speak Streamable HTTP, the docs give a local proxy variant that runs npx -y mcp-remote https://mcp.docs.astro.build/mcp over stdio. Windsurf is the client the page singles out as needing that proxy. Cursor and VS Code have one-click install links on the docs page, and Claude.ai or Claude Desktop use a custom connector with the same URL.

After connecting, test it with a question that has a checkable answer, such as “using the Astro docs, what is the current way to define a content collection?” Then open the docs page it cites and compare. The Astro docs themselves say to review and test generated code, and we agree with that advice.

What does the WordPress MCP Adapter do?

The WordPress MCP Adapter is the official plugin that exposes a WordPress site to MCP clients. Its WordPress.org listing says it bridges the Abilities API to the Model Context Protocol, with HTTP and STDIO transports. It adds no AI features of its own. What an assistant can actually do comes from abilities: single actions that WordPress core or a plugin registers, such as “get site info” or “create a draft”.

The current release is 0.7.1, dated 15 October 2026 in the plugin changelog. The readme lists Requires at least: 6.9, Requires PHP: 7.4 and Tested up to: 7.1. WordPress 6.9 matters because that is the first release that includes the Abilities API. For context, the current stable WordPress is 7.1.4.

Three details from the changelog shape how you use it today:

  • Version 0.7.0 serves exactly two MCP schema revisions, 2025-11-25 and 2026-07-28. Clients that propose older revisions still connect and are served through the 2025-11-25 schema.
  • Version 0.7.0 deprecates bundling the adapter inside your own plugin. You install the adapter plugin and declare Requires Plugins: mcp-adapter in your plugin header.
  • Version 0.7.1 caps stored session initialization data at 4 KiB. Clients that were affected need to reconnect once.

Out of the box, a client connecting to the default server sees three tools: mcp-adapter/discover-abilities, mcp-adapter/get-ability-info and mcp-adapter/execute-ability. List, read details, run. The assistant discovers your site’s abilities through those rather than receiving one tool per ability. That design keeps the tool list short, which is the same idea our own WP Astro MCP uses in router mode.

How do I connect an AI assistant to my WordPress site?

You need WordPress 6.9 or newer, the MCP Adapter active, HTTPS on the site, and a WordPress user with a sensible role. The adapter’s site-owner guide walks through it, and the steps below follow it.

  1. Install and activate the plugin: wp plugin install mcp-adapter --activate, or use Plugins, Add New in wp-admin.
  2. Create an Application Password under Users, Profile for the account the assistant will use. WordPress shows it once.
  3. Point your client at https://your-site.example/wp-json/mcp/mcp-adapter-default-server, using the Site Address (URL) from Settings, General.
  4. Ask the assistant to list the abilities it can use. An empty list still means the connection works.

For Claude Code, the guide shows a direct HTTP connection with a Basic auth header. Build the base64 value from username:application-password.

Checked on 15 November 2026.

printf 'your-username:xxxx xxxx xxxx xxxx xxxx xxxx' | base64 | tr -d '\n'

claude mcp add --transport http my-wordpress-site \
  https://example.com/wp-json/mcp/mcp-adapter-default-server \
  --header "Authorization: Basic PASTE_THE_BASE64_HERE"

Desktop clients that read a JSON config go through the @automattic/mcp-wordpress-remote helper, which turns the client’s STDIO calls into HTTP requests to your site:

{
  "mcpServers": {
    "my-wordpress-site": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://example.com/wp-json/mcp/mcp-adapter-default-server",
        "WP_API_USERNAME": "your-username",
        "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}

On a local site with WP-CLI there is a third route that needs no password: the client launches wp --path=/path/to/site mcp-adapter serve --server=mcp-adapter-default-server --user=admin as a subprocess. Run that as an administrator only on a machine you control, because the assistant then acts with that user’s full permissions.

For a wider look at the options, including when to skip MCP altogether, see our post on four ways to connect an AI agent to WordPress. For client-side setup with Codex and Claude, our MCP tools setup guide covers the config files in detail, so we do not repeat them here.

How do I expose my own plugin feature as an MCP tool?

Register an ability, mark it public, and give it a permission callback. The Abilities API is core WordPress since 6.9: you register with wp_register_ability() on the wp_abilities_api_init hook, and any custom category on wp_abilities_api_categories_init before that. WordPress core registers three abilities of its own, core/get-site-info, core/get-user-info and core/get-environment-info, and two categories, site and user, that you can use straight away.

This minimal read-only example counts drafts. We ran php -l on it; it has not been run against a live site in this post, so test it on staging.

Checked on 15 November 2026 against WordPress core and the adapter’s Creating Abilities guide.

add_action( 'wp_abilities_api_init', function () {
	wp_register_ability(
		'attowp-demo/count-drafts',
		array(
			'label'               => 'Count draft posts',
			'description'         => 'Returns how many posts are currently drafts.',
			'category'            => 'site',
			'output_schema'       => array(
				'type'       => 'object',
				'properties' => array(
					'drafts' => array( 'type' => 'integer' ),
				),
			),
			'execute_callback'    => function () {
				return array( 'drafts' => (int) wp_count_posts()->draft );
			},
			'permission_callback' => function () {
				return current_user_can( 'edit_posts' );
			},
			'meta'                => array(
				'public'      => true,
				'annotations' => array(
					'readonly'    => true,
					'destructive' => false,
					'idempotent'  => true,
				),
			),
		)
	);
} );

Three rules are easy to miss. Exposure is opt-in, so an ability without meta.public (or meta.mcp.public) stays invisible to MCP. Every ability must declare a category that is already registered, or wp_register_ability() returns null and, with WP_DEBUG off, fails without any visible error. And the adapter turns a name like my-plugin/my-tool into my-plugin-my-tool when it appears as an MCP tool, because slashes are not valid in MCP tool names.

For a longer walkthrough, we wrote up a working example of adding abilities to a plugin and a note on deciding which abilities an AI client can see in WordPress 7.1.

What is WordPress Studio’s MCP server for?

Studio’s MCP server lets an AI agent create, start, stop and work on local WordPress sites that run in the Studio desktop app. It is a separate thing from the MCP Adapter: the adapter exposes one live site’s abilities, while Studio’s server manages the local development environment itself.

According to the Studio MCP documentation (updated 11 November 2026), the easy path is Settings, then MCP, then Connect next to your agent app. Claude Code, ChatGPT (Codex), Cursor and Grok Build are listed. The manual entry runs the Studio CLI over stdio:

{
  "wordpress-studio": {
    "command": "studio",
    "args": ["mcp"]
  }
}

Claude Code users can run claude mcp add wordpress-studio -- studio mcp instead. The docs list creating sites, running WP-CLI commands and taking screenshots, plus working with both local and WordPress.com sites. Requirements include the Studio CLI (bundled with the plugin route, separate for manual setup) and Node.js 22 or later for the Claude Code plugin. Image generation needs a WordPress.com login. The page does not state usage limits, so we cannot give you any.

Our take: Studio is the safest place to let an agent experiment, because the site is local and disposable. Build and test your abilities there before you connect anything to production.

What changed in the 2026-07-28 MCP specification?

The 2026-07-28 revision makes MCP stateless. Protocol-level sessions and the Mcp-Session-Id header are gone, the initialize handshake is removed, and every request carries its own protocol version and client capabilities. Servers must also implement a new server/discover call that advertises supported versions, capabilities and identity. The official changelog lists these under “Major changes”.

The other changes that matter to anyone building or running a server:

  • The HTTP and SSE transport, deprecated since protocol version 2025-03-26, is reclassified as Deprecated. Use Streamable HTTP. SSE stream resumability (the Last-Event-ID header) is removed from Streamable HTTP too, so a broken response stream loses the in-flight request and the client re-issues it.
  • Roots, Sampling and Logging are deprecated. They keep working during a deprecation window of at least twelve months.
  • Server-initiated requests such as elicitation move to a multi round-trip pattern: the server returns an input_required result and the client retries with answers.
  • List results must carry ttlMs and cacheScope so clients can cache them.
  • Experimental tasks move out of the core protocol into an official extension.
  • Dynamic Client Registration is deprecated in favour of Client ID Metadata Documents.

For a WordPress site owner, the practical effect is small today. MCP Adapter 0.7.0 and later speak both 2025-11-25 and 2026-07-28, and wp mcp-adapter list --protocol=2026-07-28 counts the components available under the newer revision. If your client is older, it still connects through the 2025-11-25 schema. For a plugin author, the one thing to do is stop bundling the adapter and stop writing code that assumes a session. Our MCP protocol explainer covers how the protocol works end to end, so this post sticks to the differences.

What is WP Astro MCP, and where does it fit?

WP Astro MCP is an open-source MCP server (MIT licence, github.com/vapvarun/wp-astro-mcp) that adds an Astro frontend to a WordPress site. It reads content through the WordPress REST API, converts it to Markdown, generates an Astro 6 project and can push the result to GitHub. WordPress stays the CMS where editors write; Astro becomes the public delivery layer. We build it, so weigh this section accordingly.

The version on GitHub is 3.3.0 and the repository was last pushed in September 2026. The README now counts 57 tools (the March version of this post said 55). It splits them by job:

Group

Tools

What it does

Site management

9

Register a site, detect SEO plugin, ACF, WooCommerce and post types, set export options

Content extraction

13

Fetch posts, pages, custom post types, taxonomies, authors, menus and media

Transform

6

Convert to Markdown, handle shortcodes, preview quality

Output and media

7

Scaffold Astro, write content, generate redirects, rewrite media URLs

GitHub

6

Init repo, commit, push, deploy config for Vercel, Netlify or Cloudflare

Content generation

7

Plan, start, resume, retry and validate large exports

Content sync

8

Detect changes, pull only what changed, remove deleted posts, schedule syncs

Setup wizard

1

Guided flow from site to deployed frontend

Its default router mode exposes three meta-tools (wp_astro_run, wp_astro_help, wp_astro_describe) plus 11 promoted tools, 14 in all. Setting WP_ASTRO_MODE=full exposes all 57. Installation is a clone, npm install and npm run build, then a Claude Code entry that runs node /path/to/wp-astro-mcp/dist/index.js. The README asks for Node.js 20 or newer and a WordPress Application Password.

Its real limits, from its own README:

  • It works best with standard Gutenberg or classic editor content. Pages built with Elementor, WPBakery or Divi lose layout structure in conversion, and the README says to expect manual cleanup.
  • Credentials sit in plain text in config/sites.json. It is gitignored and the README recommends chmod 600, but there is no encryption layer.
  • It requests whatever site.url you configure, with no allowlist, so only register sites you trust.
  • It is a one-maintainer project, not an official one. If you need long-term support, plan for that.

It also solves a different problem from the official servers. The Astro docs server improves what your assistant knows. The MCP Adapter lets an assistant act on a live WordPress site. WP Astro MCP automates one specific project, a headless migration, and does it through the REST API rather than through abilities. You can use all three together without conflict.

Which MCP server should I use for which job?

Pick by what you want the assistant to do, not by which server is newest. This table sums it up.

Job

Server

Acts on

Main limit

Get correct Astro answers

Astro docs MCP

Nothing, it only searches docs

One tool, search_astro_docs. Cannot read your project

Let an assistant manage a live WordPress site

WordPress MCP Adapter 0.7.1

Your site, as the connected user

Only public abilities. Web apps like claude.ai cannot connect yet

Build and test on a disposable site

WordPress Studio MCP

Local Studio sites

Needs the Studio app and CLI, Node.js 22+ for the Claude Code plugin

Move WordPress content to Astro

WP Astro MCP

Your WordPress REST API and a local Astro project

Weak on page-builder layouts. Plain-text credentials in a config file

If you are deciding whether Astro in front of WordPress is the right architecture in the first place, that is a separate question from MCP, and one tool does not answer it. Start with the problem you have (speed, editor workflow, hosting cost), then see whether a headless build solves it.

Common mistakes people report

These are the recurring problems we found in the adapter’s issue tracker and docs on 15 November 2026. On the Astro side the one trap to know is client support: Windsurf cannot use the streaming HTTP entry and needs the proxy variant. Each is paraphrased and linked.

  1. Connecting, then finding nothing to do. The assistant sees three tools and an empty ability list. The site-owner guide explains that only abilities marked public are reachable, so you need a plugin that registers some. Fix: add or enable a plugin with abilities, or register your own. Source: MCP Adapter site-owner guide.
  2. A 404 or rest_no_route on the endpoint. Users have reported it after updating (issue 367, opened 3 October 2026, still open when we checked). The guide’s checks: plain permalinks do not serve /wp-json/ (use ?rest_route=), missing rewrite rules need a permalink re-save, a source-code install lacks files the plugin needs, and another plugin can turn the default server off.
  3. 401 Unauthorized with correct credentials. Some Apache setups strip the Authorization header before WordPress sees it, and Application Passwords do not appear at all on sites without HTTPS. Source: the same site-owner guide.
  4. Trying to connect claude.ai or ChatGPT in the browser. The guide states plainly that web apps connect through OAuth, WordPress core has no OAuth server, and the adapter adds none, so they cannot connect on their own today. An OAuth request is open as issue 436. Use a desktop client or the WP-CLI route.
  5. Silent ability registration failures. A missing or unregistered category makes wp_register_ability() return null with only a debug-mode notice. Turn on WP_DEBUG on staging while you build. Source: the adapter’s Creating Abilities guide.
  6. Constant approval prompts for read-only calls. Because the generic execute-ability tool is annotated destructive, some clients ask for confirmation even for reads. It is proposed as issue 431 and open at the time of checking. Do not respond by auto-approving the tool; it also covers writes.

What can MCP servers not do?

An MCP server gives an assistant reach, not judgment. Whatever the assistant can call, it can call wrongly. The 2026-07-28 spec itself says tool annotations should be treated as untrusted unless they come from a trusted server, and that hosts must get user consent before invoking a tool.

A short list of limits we apply on our own sites:

  • Use a dedicated low-role user. Every adapter action runs with that user’s permissions, so an Editor connection cannot do what an Editor cannot do. Create one Application Password per client so you can revoke one without touching the rest.
  • Treat write abilities as production changes. The adapter guide says abilities change a live site the same way wp-admin does. Try them on staging, keep backups.
  • Do not let docs servers stand in for testing. The Astro docs server improves accuracy; it does not guarantee a working build.
  • Keep credentials out of repos. Config files with Application Passwords belong outside version control. Revoke and regenerate on any leak.

Frequently asked questions

Is there an official Astro MCP server?

Yes, but it is a docs-search server at https://mcp.docs.astro.build/mcp. It exposes one tool, search_astro_docs. It does not edit or build your Astro project.

Which MCP Adapter version is current?

0.7.1, released 15 October 2026 per the plugin changelog. It requires WordPress 6.9 or newer and is tested up to WordPress 7.1.

Do I need the MCP Adapter to use WP Astro MCP?

No. WP Astro MCP reads content through the standard WordPress REST API with an Application Password. The adapter is a separate way of letting an assistant act through abilities.

Is SSE still supported by MCP?

The older HTTP and SSE transport is Deprecated in the 2026-07-28 specification and scheduled for removal under a policy with a minimum twelve-month window. New servers should use Streamable HTTP.

Can I connect the adapter to ChatGPT or claude.ai in a browser?

Not on its own today. Those apps need an OAuth sign-in, and neither WordPress core nor the adapter provides one. Desktop clients with an Application Password, or WP-CLI on a local site, work.

Where should I test first?

On a local or staging site. WordPress Studio’s MCP server is built for exactly that, and it keeps the experiment away from live content.

Where we land

MCP servers are useful, and the official pieces are now clear enough to use without guesswork: the Astro docs server for accurate answers, the MCP Adapter plus abilities for acting on WordPress, and Studio for a safe workbench. Our own WP Astro MCP covers a narrower job, the move to a headless Astro frontend, and has the limits listed above.

Start small. Connect the docs server (one command), install the adapter on a staging site, register one read-only ability, and watch what the assistant does with it. Everything else builds on that loop. For protocol background, read our MCP protocol explainer next.

Varun Dubey

Written by

Varun Dubey

Varun Dubey runs Wbcom Designs, the WordPress studio he founded in India in 2009. He has spent sixteen years building on WordPress and BuddyPress, shipping client work and products such as Reign, BuddyX, Jetonomy and MediaVerse, and has been putting Claude and OpenAI workflows into production since 2023. He writes up what the studio learns along the way.

More about Varun

No comments yet