WEBMCP / PRODUCT ADOPTION AND ANALYTICS

Help customers get more from your product. Understand their needs.

A customer describes what they want to do, and an agent helps them do it in your application. With AGO and WebMCP, make your features easier to use and learn from completed journeys to improve your product.

Find your first use case Explore the benefits

FROM CUSTOMER NEED TO PRODUCT INSIGHT

Your customer wants to get something done

“Show me this month’s overdue invoices.”

The agent acts in your application

The right list, with the right filters

Your customer finds the information they need to continue their work.

Your team learns from the journey

A use case to track: overdue invoices
A journey to measure: finding the list
An idea to test: a more direct route

Illustrative example. Validate these ideas against your usage data. No financial action is taken.

Feature adoptionCustomer autonomyProduct insights

POTENTIAL BENEFITS

Help customers discover your product’s value through use

Every assisted journey can help your customer move forward and give your team an opportunity to improve the experience.

Help customers discover features

The customer describes their goal. The agent points them to the relevant feature and helps them use it, including features they did not know existed.

Track: first use and repeat use

Build customer autonomy

Finding a document, setting up a view or preparing a report: recurring tasks become journeys to simplify, with the potential to reduce requests for help.

Track: completed tasks and support requests

Inform product priorities

Connect needs expressed to your AGO agent with actions and obstacles. You can distinguish a feature that is hard to find from a need your product does not yet meet well.

Track: recurring needs and friction points

WHAT WEBMCP ENABLES

Customers can ask for an outcome inside your application

WebMCP lets a compatible agent use the actions you allow in your product: finding information, filtering a list or preparing a form. AGO helps you make these journeys accessible and measurable.

“Prepare my monthly report.”

The agent opens the right screen and prepares the filters. Your customer can check the result and continue working, even if they are still learning your interface.

Example of a journey to implement in your application.

UNDERSTAND YOUR PRODUCT BETTER

Connect needs, actions and outcomes

Analytics become useful when they help your team decide what to simplify, explain or build.

NEEDS

What are customers trying to do?

With your AGO agent, analyze recurring requests and the words customers use. They can reveal a need that your menus do not make obvious.

FRICTION

What stops them moving forward?

Connect attempted actions to their results. An interrupted journey or repeated errors give your product team something concrete to investigate.

DECISIONS

Which improvements make a difference?

Compare journeys before and after a change: task completion, time to reach a result, feature usage and requests for support.

For external agents using WebMCP, tracking covers exposed actions and their results. Their private conversations remain inaccessible. Collection and dashboards are configured with your analytics.

AN ADOPTION BENCHMARK

The first experience matters for retention

The opportunity for your team: help customers reach their first useful result. That is a concrete goal for a journey assisted by an agent.

69%

of the strongest products in seven day activation also ranked among the strongest in three month retention, according to Amplitude’s 2025 report.

Amplitude, Product Benchmark Report 2025, pp. 13 and 30

Study of over 2,600 companies, using data from September 2023 to September 2024. An observed correlation, with no measurement of a WebMCP or AGO effect.

AGO EXPERTISE / AGENTIC IN THE BROWSER

Our browser experience is built into the SDK

We have spent months building the foundations that let an agent act inside an application. Our open source SDK makes that work inspectable: navigation, page state, business functions and WebMCP integration.

Explore the code on GitHub See examples for each framework

@useago/sdkReact / Vue / Angular / JavaScriptApache 2.0

useAgoNavigation

Move between screens

The agent uses your router. For WebMCP, a page change waits for the destination’s tools to register before returning control, so the journey can continue on the right screen.

Read the navigation code

useAgoPageState

Read and update page state

Filters, sorting and visible data become accessible to the agent. The SDK validates values and can wait for loading to finish before returning updated data.

Read the page state code

defineFunction

Call your business logic

Describe a function and its parameters. It runs in the browser and returns its result to the agent. You choose which functions to share through WebMCP.

Read the functions documentation

ONE FUNCTION, TWO WAYS IN

Your actions become WebMCP tools

Enable the SDK bridge to expose your functions to agents in compatible browsers. They remain available to your own AGO agent.

The example exposes the page title as a readable value. In your product, the same mechanism can read a list or call your existing functions.

For sensitive actions, add confirmation in your application or exclude the function with webmcp: false. External calls do not go through the AGO agent’s approval mechanism.

Read the bridge documentation

webmcp.js

import { AgoClient } from "@useago/sdk";

const client = new AgoClient({
  baseUrl: "https://playground.api.useago.com",
  agent: "generic-guide",
  webmcp: true,
});

client.registerFunction({
  name: "readPageTitle",
  description: "Read the current page title.",
  parameters: { type: "object", properties: {} },
  handler: () => ({ title: document.title }),
  webmcp: { annotations: { readOnlyHint: true } },
});

JavaScript example running in the browser, connected to the public demo agent. WebMCP stays inactive when the browser does not support it.

Code, tests and tools to verify how it behaves

A tested tool lifecycle

The bridge tests cover tool registration and removal, page transitions and function errors.

Inspect the WebMCP tests

Diagnostics inside the browser

The development panel shows registered functions, the agent’s context and a log of calls and their results.

Explore the development panel

Test integrations without network calls

createMockClient lets you simulate agent events and verify journeys in your application’s tests.

Explore the testing tools

The events behind your analytics

WebMCP calls emit the same invocation and result events as your AGO agent’s functions. Connect them to the product metrics described above.

Place this excerpt after creating the client. Console logging is for diagnostics; configure analytics collection with your own tool.

Explore the full SDK integration

events.js

client.on("function:invoke", ({ functionName }) => {
  console.log("Action called", functionName);
});

client.on("function:result", ({ error }) => {
  console.log("Outcome", error ? "error" : "success");
});

FAQ

Assess the opportunity for your product

What benefits can we expect?

Better feature discovery, more tasks completed independently and a clearer view of friction. The impact on activation, retention or support depends on your product and the journeys you choose. We measure it in a pilot before expanding.

Does this help customers understand the product?

The agent connects a goal expressed by the customer to the features that can achieve it. Customers discover their value in a concrete situation. You can then measure whether they reuse those features and whether they still need help.

What can we learn from analytics?

Requests to your AGO agent shed light on expressed needs. Actions and results help analyze usage and obstacles. For an external agent using WebMCP, only calls to exposed actions and their results are observable, not its private conversation. Tracking connects to your analytics.

Do we need to wait for every browser to support WebMCP?

You can start with your AGO agent embedded in the application. WebMCP access activates in compatible environments. Your team prepares the same journeys for both ways of accessing your product.

How do we keep control of important actions?

You choose which actions are accessible. For sensitive operations, we plan confirmation within your application or exclude them from actions available to external agents. WebMCP calls do not go through the AGO agent’s approval mechanism, so your application’s controls remain essential.

Technical references verified on September 15, 2026

AGO SDK WebMCP proposal

Which journey should be easier for your customers?

Let’s choose a first use case and the metrics that will show its value for your customers and your team.

Find your first use case