Technical Implementation Whitepaper
MCP and WebMCP: Optional Tool Interfaces for Real Tasks
Assess a real user task before exposing tools. Distinguish MCP host/client/server integration from the WebMCP browser API draft, historical adoption signals from production availability, and a successful tool call from a completed purchase. No new interface is required for every marketing site.
v1.1 · October 2026 · Tenten GEO Research
CH.01
From Read to Used
Reading information and executing an authorized task are different needs. A site without an agent tool interface does not automatically lose buyers; decide whether the actual task and supported client justify integration.
Some users delegate queries or actions to agents; others read and use the normal site. Accurate content and a usable purchase flow still matter. Querying availability, requesting a booking and making a confirmed booking are distinct outcomes, not interchangeable signs of a sale.
Chapter takeaway
A tool interface can support a suitable authorized task. It does not replace readable content or guarantee selection, booking or revenue.
CH.02
MCP: A Protocol with Client and Server Conditions
MCP standardizes connections between supported hosts, clients and servers. Compatibility, negotiated capabilities, transport, authorization and product availability still need verification.
The July 28, 2026 specification defines a protocol for context and tools, including capability negotiation. A service interface is not automatically discoverable or usable by every agent. Client configuration, supported features and access policy remain part of an integration.
Adoption momentum
The maintainer’s December 9, 2025 announcement reported over 97 million monthly SDK downloads and 10,000 active servers. These are dated publisher-reported indicators, not active people, enterprise installations, March 2026 server counts or proof of business return.
| Date | Provider | Signal |
|---|---|---|
| 2025-05-21 | OpenAI | Responses API remote MCP support announced (OpenAI) |
| 2025-05-19 | Microsoft | Build announcements across named products and steering committee (Microsoft) |
| 2025-04-01 / 2025-04-29 | AWS | Open-source MCP servers / Q Developer CLI MCP support (AWS) |
Three scoped announcements, not universal first-adoption or all-product availability dates.
Chapter takeaway
Confirm the particular client, feature and contract. MCP can standardize an interface without making all agents compatible or granting them access.
CH.03
WebMCP: Browser Tool API Draft
WebMCP describes web applications exposing JavaScript tools to supported agents. It is distinct from assuming a backend MCP server or universally deployed browser capability.
The official WebMCP document observed October 4 is a Draft Community Group Report dated October 2, 2026, not a W3C Standard or Standards Track document. It describes browser-context JavaScript tools and collaborative user control. Check actual browser/client implementation and task permissions before considering production use.
| Dimension | Existing site interaction | Supported declared tool interaction |
|---|---|---|
| How the agent uses it | Read content or use normal browser UI | Invoke a supported declared tool in the applicable context |
| Reliability | Depends on the flow and implementation | Explicit schema may help, but needs validation, errors and testing |
| Tasks it can complete | Information and available human/browser flows | Only implemented, authorized tasks; no universal one-call completion |
| Your role | Maintain accurate content and usable flows | Define a bounded interface and permission contract if needed |
| Competitive outcome | No interface is not proof the buyer skips the site | A tool call is not proof of a booking, purchase or sale |
Interface options with implementation limits, not two predetermined competitive outcomes.
Chapter takeaway
Check concrete support and user need before choosing WebMCP or another interface. A declared tool does not guarantee task completion.
CH.04
The B2A Content Framework
Tenten’s four dimensions are a planning framework. Not every content page needs an executable layer; read-only tasks and existing flows can be sufficient.
Use the framework only for a defined task: readable facts, explicit data, any needed action interface, and verified permissions/results. B2A is a strategy label, not a rule that every page needs MCP or that human content is obsolete.
| Layer | What this layer answers | What to verify | What you need to deliver |
|---|---|---|---|
| 1 Semantic content | Who you are and what you offer | Check whether relevant facts are clear | Accurate readable facts for the actual task |
| 2 Structured data | How the facts map to each other | Check data meaning, units and freshness | Explicit supported fields; schema only where appropriate |
| 3 Executable endpoints | What actions can be taken | Check whether an action is actually needed | Existing flow/API or suitable MCP/WebMCP, if supported |
| 4 Trust and verification | Whether the result can be trusted | Check authority and actual result | Permissions, consent, validated status and error handling |
Four authored planning dimensions; optional action interfaces are not automatic failures.
Chapter takeaway
Keep readable facts and reliable existing flows. Add an interface only where a real task, supported client and authorization justify it.
CH.05
Inventory of Agent-Executable Tasks
Evaluate task frequency, value, data sensitivity and possible side effects with your own evidence. A booking or quote is not automatically low risk; an interface can remain unnecessary.
Start by confirming user demand and the current flow. Read-only queries may still expose sensitive data; reservations can consume slots or create obligations. The table prompts review rather than assigning universal value or risk scores.
| Task | Value to verify | Risk to assess | Recommendation |
|---|---|---|---|
| Query (availability / inventory / price) | Useful only if demand and accurate data exist | Depends on data and access rights | Evaluate a bounded read-only path before exposing it |
| Compare / recommend | Depends on actual comparison needs | Data scope and misleading output | Use comparable factual fields where justified |
| Book / register | Depends on booking demand and confirmed outcomes | Personal data, capacity and commitments | Verify permission, actual slot/status and cancellation policy |
| Add to cart / quote | Depends on quoting/cart needs | Amounts, terms and persistent state | Make state and conditions explicit with appropriate consent |
| Payment / checkout | Potential value with sensitive consequences | Money, fraud and irreversible effects | Use supported payment/authorization controls; do not assume reversibility |
| Account / personal-data changes | Depends on the actual user task | Privacy, account authority and persistence | Require appropriate verified authorization and user control |
Six task review prompts, not empirical frequency, value or universal risk grades.
Chapter takeaway
An appropriate first scope depends on your task evidence and controls. Preserve explicit user authority, correct state and existing working flows; no tool guarantees closing.
CH.06
The B2A Starter Roadmap
If a concrete integration is justified, use this five-step Tenten planning worklist. It is not a mandate to build an endpoint, and this guide implements no new site functionality.
STEP 1
Confirm one task and its demand
Define user outcome, allowed actions, data and side effects. Existing read-only or human flow may already meet the need.
STEP 2
Clarify facts and data contract
Define accurate facts, field meaning, freshness and task rules; do not force an action layer onto every page.
STEP 3
Choose and verify a supported interface
Check actual client/browser support, version, capabilities and authorization. MCP and WebMCP are different integration contexts; do not promise all-agent access.
STEP 4
Validate permissions and returned state
Preserve user consent and authorization, validate inputs and actual state, and handle errors and consequences. A protocol alone cannot enforce all safety controls.
STEP 5
Measure before expanding
Use defined attempts and denominators, actual task outcomes, errors and relevant business attribution. A successful call is not automatically a completed purchase.
| Checklist item | Done when |
|---|---|
| Task selected | Defined demand, outcome, permitted data/actions and side effects |
| Content ready | Accurate facts, supported data contract and known freshness |
| Interface assessed | Justified interface with verified client/version/capability support |
| Trust mechanism | Actual consent/authorization, validated state and error handling |
| Measurement live | Defined attempts, outcomes, errors and separate business attribution |
Five planning checks; optional or not applicable is not an automatic failure.
One last thing
Begin with the user task and evidence, not a universal infrastructure forecast. Keep content and purchase flows useful; build only a justified supported integration, without promises of selection or revenue.
Sources & Methodology
Substantive Taipei revision October 5, 2026. Maintainer December 9, 2025 figures are historical SDK-download/server indicators. Provider milestones have named product scope. July 28, 2026 MCP specification and October 2 WebMCP community draft are distinct. The mixed market chart is retired; Gartner’s August 26, 2025 forecast of 40% by end2026 is not observed MCP adoption. Worklists are Tenten recommendations, not client outcomes. https://blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation/ https://modelcontextprotocol.io/specification/2026-07-28 https://webmachinelearning.github.io/webmcp/ https://openai.com/index/new-tools-and-features-in-the-responses-api/ https://blogs.microsoft.com/blog/2025/05/19/microsoft-build-2025-the-age-of-ai-agents-and-building-the-open-agentic-web/ https://aws.amazon.com/blogs/machine-learning/introducing-aws-mcp-servers-for-code-assistants-part-1/ https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-q-developer-cli-model-context-protocol/
© 2026 Tenten GEO · Feel free to cite this whitepaper with attribution.
Discuss your AI search priorities
Request a 30-minute benchmark interpretationSend a booking request. We’ll email you to confirm a time within 24 hours.