REST vs MCP for WordPress Tasks: A Controlled Benchmark Protocol

A REST versus MCP benchmark should compare equivalent WordPress capabilities under matched identities and tasks, not confuse transport convenience with permission, correctness or product coverage.

AI is most useful here as an evidence organizer, comparison engine and drafting assistant. It can make a complex WordPress task easier to inspect, but it cannot create missing authority, certify facts it did not observe or silently convert a recommendation into permission to act.

In one sentence: A REST versus MCP benchmark should compare equivalent WordPress capabilities under matched identities and tasks, not confuse transport convenience with permission, correctness or product coverage.

What this guide helps you accomplish

Measure how direct REST and MCP-mediated workflows differ in discovery, setup, execution, evidence, error handling and human effort while holding the underlying WordPress authority constant.

• An equivalence map between REST endpoints and MCP-exposed abilities or tools.
• A matched task suite with identical WordPress identities and fixtures.
• Metrics for setup, discovery, execution, correctness, denials and observability.
• A report that separates transport findings from client and ability implementation effects.

The finished artifact should be understandable by the person responsible for the decision and reproducible by someone who did not participate in the original prompt. A fluent answer is not enough. Every material conclusion needs a source, a scope and a verification path. When the evidence cannot establish something, the correct output is an explicit unknown or a testable hypothesis.

Evidence and inputs to prepare

• The exact REST routes, abilities, adapter and client versions.
• Matched authentication and permission profiles.
• A resettable WordPress fixture with stable objects.
• Task briefs and expected state transitions.
• Request, tool-call and WordPress-diff capture mechanisms.

Before supplying evidence to an assistant, remove credentials, secret values and unrelated personal information. Preserve the identifiers, versions, timestamps, locale, units and source labels needed to interpret what remains. A screenshot without a URL, state or date may be useful context, but it is rarely sufficient authority for a production decision.

Do not begin with a broad request such as “review this,” “fix this” or “make it better.” Define the decision the work must support, the population included, the source that is authoritative for each field, the allowed operations and the actions that remain forbidden. The planning or research stage should use a local repository, isolated fixture or exported evidence and does not require production WordPress access.

REST and MCP are not competing permissions

Both paths ultimately depend on WordPress authorization and the exposed operation. The benchmark should not attribute a capability difference to transport when the underlying operations differ.

Discovery is a real outcome

MCP may help clients discover tools and schemas, while REST may require explicit endpoint knowledge. Measure this separately from execution correctness.

Errors need semantic mapping

HTTP status, tool errors and client summaries may represent the same underlying denial differently. Preserve raw evidence before comparing usability.

Keep observation, inference and authority separate

A controlled review should distinguish at least four states:

1. Observed: directly present in a named record, file, response, rendered page or executed test.
2. Inferred: a plausible interpretation supported by evidence but not directly established.
3. Recommended: a proposed human decision or next action.
4. Authorized and verified: a separately approved change that was executed and then checked against acceptance criteria.

AI output usually begins in the first three states. It does not become authorized merely because it is detailed, internally consistent or technically convincing. Preserve this distinction in tables, reports, tickets and public case studies.

A safe workflow

1. Define equivalent operations and document any non-equivalence before testing.
2. Configure matched identities, data fixtures and reset procedures.
3. Pre-register tasks, metrics, repetitions and allowed interventions.
4. Run REST and MCP conditions in randomized order.
5. Capture setup actions, discovery, requests, tool calls, responses, WordPress state and refusals.
6. Verify results with transport-independent assertions.
7. Classify differences as transport, client, ability, permission or implementation effects.
8. Publish protocol, raw sanitized artifacts, limitations and version scope.

This sequence deliberately places accountable review between analysis and implementation. If a later stage needs broader access, create a new task, a new identity or an explicit permission change. Do not quietly upgrade the analytical identity because it reached a correct boundary.

Prompt recipe

Replace every value in square brackets before using the prompt. Do not paste passwords, API keys, authentication cookies, private customer records or unrelated personal information.

You are reviewing [TASK SCOPE] for [SITE, REPOSITORY OR DATASET] using only the supplied evidence.

Objective:
Measure how direct REST and MCP-mediated workflows differ in discovery, setup, execution, evidence, error handling and human effort while holding the underlying WordPress authority constant.

Return the following fields:
- Run ID
- Transport
- Client
- Operation
- Identity
- Setup actions
- Discovery result
- Execution result
- Raw error
- State diff
- Verification
- Human intervention
- Time
- Failure class

Rules:
1. Use equivalent operations and identical identities.
2. Retain raw HTTP or tool evidence after sanitization.
3. Do not treat client wording as the underlying permission result.
4. Report non-equivalent coverage explicitly.
5. Do not generalize beyond tested versions and tasks.

For every finding:
- identify the exact source, record, URL, file, line, object ID, state or dataset row;
- preserve dates, versions, units, locale, identifiers and denominators;
- separate observation, inference, recommendation and unknown;
- state what evidence was not available;
- do not change WordPress, source code, commerce data, analytics, external systems or published content.

Why this prompt is structured this way

The prompt creates an evidence contract before asking for recommendations. It makes missing data visible, reduces the chance that a model will complete an incomplete record with plausible prose and produces an output that can be reviewed systematically. Structured fields also make it easier to compare repeated runs or hand an approved subset to a later implementation workflow.

A production implementation may add JSON schema, typed tool inputs or automated validation. Those mechanisms improve consistency, but they do not establish that the source evidence is true, complete or current. Human review and system-specific verification remain required.

Recommended access boundary

Use No WordPress access during the planning or research stage for the stage described in this guide. The exact capabilities available to an identity must come from the installed product version, the published coverage contract and the connection method actually in use.

What must remain outside this task

• Fabricated results
• Broader identity for one transport
• Different task definitions
• Production testing
• Claim that one transport is universally safer

A refused action can be useful evidence that the control boundary is working. Do not respond to an expected refusal by granting a broad administrator account or Full Power. First determine whether the action belongs in the current mandate at all. If it does, create a separately authorized stage with the narrowest required capability.

How WP Agent Control fits

WP Agent Control can provide a dedicated WordPress identity and a bounded permission profile for the stages its installed version actually supports.

WP Agent Control is the controlled WordPress identity and permission layer. It is not the AI model, not a universal MCP server and not proof that every assistant, client or transport can reach every WordPress surface. The assistant, client, transport, WordPress identity, task permission and human approval are separate layers.

Full Power is a distinct administrative exception. It must never be presented as the ordinary continuation of Read Only, Draft, Content Editor or Publisher, and it must not be used merely to make an example, benchmark or workflow succeed after a correct refusal.

Verification checklist

• ☐ The task, population, period, environment and decision are explicit.
• ☐ Every material observation is linked to exact evidence or labelled as a hypothesis.
• ☐ Stable IDs, URLs, versions, dates, units, locales and denominators are preserved.
• ☐ Missing evidence and coverage limits remain visible.
• ☐ The analytical or research identity performed no prohibited mutation.
• ☐ A qualified owner reviewed security, accessibility, legal, commerce or release implications where applicable.
• ☐ Any implementation has a separate mandate, access level, backup and verification plan.
• ☐ Temporary identities, fixtures and sensitive evidence are revoked, reset or disposed of after the task.

Common failure modes

• Capability mismatch: MCP exposes a curated ability while REST uses a broader or different endpoint.
• Client confounding: The transport is changed together with the model or client interface.
• Setup-time omission: Only execution latency is compared and discovery or configuration burden disappears.
• Error flattening: Distinct authentication, authorization and validation failures are scored as one failure type.

A recurring cross-cutting failure is permission drift: the initial task encounters a limit, and the operator broadens access before determining whether the missing operation is necessary, supported or safe. This destroys the evidence value of the refusal and makes later results difficult to attribute.

Research status and publication gate

This page defines a protocol, not a completed study. It contains no benchmark values, provider rankings, success rates or empirical conclusions.

Before public release, the study needs a pre-registered protocol, a frozen fixture, an approved budget, repeated runs, deterministic verification, reviewer rules and a sanitized evidence package. Any result must state its numerator, denominator, missing runs, exact version set and uncertainty. A later model, client, WordPress release or permission profile is a different treatment and should not inherit the earlier conclusion automatically.

Advanced note

The most useful output may be a decision matrix rather than a winner: transport choice can depend on discovery needs, client compatibility, operation design, audit evidence and organizational constraints.

Related guides

• WordPress REST API vs MCP: Which Should You Use?
• How to Expose a Custom WordPress Ability through MCP
• How to Build a WordPress Permission Test Matrix for AI Agents
• How to Build a WordPress AI Task Coverage Matrix

Next step

Continue with the most relevant supporting guide and use the access-level guide before any authenticated task. When temporary WordPress access is no longer needed, finish by revoking the identity.