Topic · 5 items
MCP
This page gathers news about MCP (Model Context Protocol), the protocol that lets an AI agent use a service's tools and data. I follow the MCP servers shipped by CMSs and platforms (WordPress, Shopify, Webflow), the developer tools that plug into them, and the security questions they raise. It's for teams deciding what to open up to an agent, and how.
Follow this topic By RSS, in your feed reader
WordPress aims for MCP and OAuth in core for 7.3
Connecting an AI agent to WordPress may soon no longer mean copying an application password around: on October 28, Jason Adams from the WordPress AI team proposed four workstreams, laid out during 7.2 and targeted at 7.3. MCP Adapter, the plugin that exposes WordPress to agents over the MCP protocol, would be hardened and then brought into core; a baseline set of abilities (the actions WordPress exposes to agents) would cover common tasks; OAuth would let site owners authorize an agent and later revoke it. This is a proposal, subject to the usual core review, not a decision.
Next step
In the meantime, give each agent a dedicated account with the lowest role that works, and a separate, revocable application password per tool. Before opening MCP access, list the site's public abilities: MCP Adapter only checks that the user is logged in and has the read capability, so the real access control lives in each ability.
The proposal tackles the right problem. Until it ships, the REST API remains the most reliable way to put an agent to work, and it's the one we favor in-house.
AI agents on WordPress: the REST API succeeds where MCP Adapter still fails
If you hand WordPress maintenance to an AI agent, the access channel matters as much as the agent: the independent WordPress Agent Benchmarks, started by Andy Peatling, ran 21 small-business requests (launch, upkeep, migration) through Claude Code and Codex in October, each one twice on the same site. Through the REST API with an application password, 33 of 42 runs succeeded; through MCP Adapter alone, none did, for lack of abilities (the actions WordPress exposes to agents), since core only ships three, all read-only. Even so, WooCommerce 11.3, in beta since October 26 and due November 10, removes its /wp-json/woocommerce/mcp endpoint (it will return 410) in favor of MCP Adapter, served at /wp-json/mcp/mcp-adapter-default-server.
Next step
If an MCP connection still uses the old WooCommerce endpoint, switch it to /wp-json/mcp/mcp-adapter-default-server before 11.3 ships on November 10, and revoke the old REST keys it relied on. To put an agent to work today, give it the REST API with an application password instead.
The tooling isn't mature enough yet, even though the WordPress AI team has made abilities its priority. For now, nothing beats the REST API: it's the approach we favor internally.
An AI agent can now analyze an application's memory leaks
For a single-page application (SPA) whose memory keeps growing during a session, chrome-devtools-mcp 1.12.0, the MCP server that gives an AI agent access to Chrome DevTools, can analyze a heap snapshot (a snapshot of the JavaScript memory heap) without a connected browser since October 22, with paginated results. The release also runs independent tool calls in parallel, hot-reloads its configuration with --watchConfig and masks WebSocket headers in its logs. On the DevTools side, the Memory panel now flags unused closure variables kept alive by a shared V8 context, sorted by memory impact.
Next step
Take a heap snapshot in the Memory panel, have your agent analyze it through this server, then check its findings with the Objects retained by contexts filter.
Webflow's MCP server, a way out of the ecosystem
Webflow's MCP server lets an AI agent, with the user's permissions, read and write elements, styles and classes, components, variables, pages and SEO settings, CMS collections and items, assets and forms. On October 15 it gained read access to Analyze, Optimize and AEO Analytics data. Webflow pitches it as a building tool; some users report using it the other way round, to inventory a site and rebuild it elsewhere.
Next step
Before moving a site off Webflow, have an agent inventory the page structure, styles and CMS collections, then rebuild the dynamic parts on the new platform. The official export only gives you the CMS as data and leaves forms broken.
With no complete export, the tool designed for building in Webflow becomes the most serious way out of it. For a client who wants to stay in control of their site, it's one more point in favor of reversibility.
Shop MCP: Shopify opens its catalog and Shop Pay to any agent
Since October 13, the mcp.shop.com MCP server lets an AI agent search over a billion products in the Shopify catalog, build a cart and pay with Shop Pay, using the UCP protocol. Search needs no key; a purchase only goes through once the buyer confirms the total and payment method. Orders land in the store's admin like any other, and there are no webhooks yet.
Next step
If you're building a shopping agent, start from this server rather than store-by-store integrations. On the merchant side, make product pages, variants and attributes complete: that's all the agent will read from your store.
A huge opportunity for the platform's merchants: their products become buyable from any agent, with no integration to build, nothing to sign up for, and no announced extra cost. The only work required is the same work that already helps search: complete, accurate product pages.