---
title: "What Is WebMCP, and Does a WordPress Blog Need It?"
url: https://hostmy.blog/what-is-webmcp/
date: 2026-10-21
modified: 2026-10-21
lang: en
author: "Aditya Sharma"
description: "WebMCP names two different things: a browser proposal for pages to offer tools, and a site manifest. Here is what each is for, and where it sits for a blog."
categories:
  - "RankReady"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2568-1024x538.jpg
word_count: 1360
---

# What Is WebMCP, and Does a WordPress Blog Need It?

For most WordPress blogs, no: WebMCP is not something you need. It is a proposed way for a web page to offer tools to an AI agent, and a blog's job is to be read, which it already does. That said, the name is used for two different things, and which one you mean changes the answer.

This post explains both, says what each is for, and ends with where it sits in the order of work for a blog. It is an explainer. It has no setup steps, and [the RankReady WebMCP page](/plugins/rankready/webmcp-wordpress/) and [its how-to guide](/docs/rankready/how-to-add-webmcp-wordpress/) cover the doing.

## Two things with one name

| Aspect | The browser proposal | A site manifest |
| ------ | -------------------- | --------------- |
| What it is | A proposed browser API, drafted by the Web Machine Learning Community Group | A file at a known address that lists what a site can give an agent |
| Where it runs | In the visitor's browser tab, in the page's own script | On your server, read as a normal request |
| What it offers | Tools a page registers, each with a name, a description, an input schema and a function | Named, read-only calls that return shaped data |
| Status | A Draft Community Group Report, not a web standard | A convention you can adopt today |
| What it suits | Pages with actions, such as forms, carts and booking | Sites with content to read |

The first is the proposal. The W3C community group's [draft report](https://webmachinelearning.github.io/webmcp/) describes it, and it states that it is not a W3C standard and is not on the standards track. The idea is that a page registers tools, and an agent calls them instead of scraping the screen and simulating clicks. The draft has changed shape more than once. Some write-ups give the API object as navigator.modelContext, and the current draft defines it on the document. The name is a sign of how early it is. Chrome has been reported to offer an early preview behind a flag, so check Chrome's own documentation for the current state before building on it.

The second is a manifest. RankReady serves one at a fixed address, /.well-known/mcp.json, that lists up to sixteen read-only calls, such as get-site-info and search-posts, depending on which resources you switch on. It runs on the server, and it is a different mechanism from the browser API, even though it borrows the name.

## What a page can usefully offer

The browser proposal pays off on pages where a person does something: fills a form, adds to a cart, picks a time. An agent calling a tool is faster and less error-prone than one working out where to click. A blog post has no such actions. Its content is text on a page, and the access question for it is answered by robots.txt and your firewall, as in [the five curl commands](/ai-crawler-test/).

If your WordPress site sells something, runs a booking form or takes sign-ups, the proposal is worth watching. If it publishes posts, the proposal has little to add.

## Does it help you get cited?

We found no evidence that either one affects whether an assistant cites you. Google's guide to generative AI in Search says you do not need new machine-readable files or special markup to appear in its AI features. It also tells owners who are weighing third-party AEO or GEO advice to review its guidance on evaluating third-party SEO advice. That is about Google, and other assistants are different. The honest position, which RankReady's own page takes, is that publishing a manifest does not make agents come. The realistic use is a person pasting your URL into a desktop agent tool because they already care about your site.

What gets a page cited is mostly unchanged: access, a page that can be read, and sentences worth quoting. The wider comparison is in [GEO vs SEO on WordPress](/geo-vs-seo-wordpress/), and a way to judge any such feature is in [AEO tools: what to measure, fix and skip](/aeo-tools-wordpress/).

## Where it sits in the order of work

| Step | Do this first | Then |
| ---- | ------------- | ---- |
| Access | Check that crawlers are not turned away by the host, firewall or robots.txt | Revisit after any security change |
| Readable pages | Check the text is in the HTML | Add structured data |
| Quotable writing | Short, direct sentences with the answer early | Keep content fresh |
| Extras | Only now consider a manifest or the browser proposal | Treat as an experiment, not a plan |

A manifest is cheap to add and cheap to leave out. Neither choice should come before the first three rows.

## How new this is

The first published version of the browser proposal appeared in August 2025, and it lists engineers from Microsoft and Google as authors. Since then it has been revised, and the object a page would use has changed. Some write-ups use navigator.modelContext, and the current draft puts it on the document. That is normal for a proposal, and it is a reason not to build anything permanent on it yet.

## What WebMCP borrows from MCP

The name comes from the Model Context Protocol, MCP, a standard way for an AI application to call tools that a separate server offers. In MCP, the client connects to a server and asks what it can do. WebMCP carries the same idea to the web: a page describes what it can do, and an agent in the browser calls it.

The difference is where the thing lives. An MCP server sits outside the page and is connected through the client's settings. The browser proposal sits inside the page and works only while the page is open.

## How to tell hype from substance

| Sign | What it suggests |
| ---- | ---------------- |
| It says exactly what it exposes and what it does not | Someone has thought it through |
| It admits that agents do not arrive on their own | It is honest about the evidence |
| It promises traffic or citations | Be careful |
| It presents a draft as a standard | Check the status of the specification yourself |
| It cannot be turned off cleanly | Treat it as a risk |

RankReady's own WebMCP page is an example of the first two. It lists the calls, says nothing in it writes, and says that publishing a manifest does not make agents come.

## What a cautious experiment looks like

If you are curious, treat it as an experiment with a small footprint. Try it on a staging copy first, read what it exposes, and keep anything private off. RankReady's defaults follow that approach: comments, users, media, installed plugins and settings are off, and nothing in the manifest can write. Turn on only what you would be happy to see published, because a manifest is public by design. Then fetch it the way a client would, and read it as a stranger.

## Questions to ask anyone selling it

`1. Which WebMCP do you mean: the browser proposal or a site manifest?
2. What exactly does it expose, and can I switch each part off?
3. Does anything it exposes let an agent change my site?
4. What evidence is there that agents use it?
5. What happens to my site if I remove it?`

A good answer to the last question is nothing. A feature that is cheap to add and cheap to remove is easy to try. One that is hard to remove should have to earn its place first.

## What it could change for a blog

If the browser proposal matures and browsers ship it, a blog could offer a few small tools, such as searching the archive, subscribing to the newsletter or finding posts by topic. Those are actions, and they are the kind of thing an agent could do for a reader. Whether readers will ask agents to do that is not known yet.

Until it is, the useful work for a blog is the earlier list: access, readable pages and sentences worth quoting.

## Where RankReady fits

RankReady includes the manifest side, off until you switch it on, and it does not need an MCP adapter or another plugin. Every call is read-only and returns only published, public content. It does not implement the browser proposal, and it does not promise that any agent will use it. It runs alongside Yoast, Rank Math, AIOSEO and SEOPress. The free [AI Readiness Checker](https://hostmy.blog/plugins/rankready/ai-readiness-checker/) shows what an assistant can reach on your site today.

If you could switch on one feature this week, would it be the one that gets you read, or the one that sounds like the future?