---
title: "Browser agents (WebMCP experiment)"
description: "Try TypeShip's native browser tools for anonymous generation, documentation search, and the agent runbook."
url: https://typeship.dev/docs/guides/browser-agents
markdown: https://typeship.dev/docs/guides/browser-agents.md
section: "Get started"
---
> ## Documentation index
> Fetch the documentation index at https://typeship.dev/llms.txt or every prose page and both generated references at https://typeship.dev/llms-full.txt.
> Append .md to any prose docs URL, or send Accept: text/markdown, for the markdown twin of that page.

# Browser agents (WebMCP experiment)

Try TypeShip's native browser tools for anonymous generation, documentation search, and the agent runbook.

TypeShip exposes three experimental tools to a browser agent when the browser supports the native WebMCP API. Open the [homepage](https://typeship.dev/) for all three tools, or any documentation page for search and the runbook.

| Tool                     | What it does                                                                                                               | Available on      |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| `typeship_generate`      | Generates one selected Target from a public Definition URL and returns counts, limits, and links for inspecting a package. | Homepage          |
| `typeship_search_docs`   | Searches the same documentation index as the site's search.                                                                | Homepage and docs |
| `typeship_agent_runbook` | Reads the current [agent runbook](https://typeship.dev/agents.md).                                                                             | Homepage and docs |

Generation uses the anonymous API allowance, including its operation cap and rate limits, even when you are signed in. It returns a summary without file contents, creates no linked Project, publishes no packages, and leaves the generator form unchanged. Search results and runbook text should be treated as untrusted input by the agent.

## Try it

Use a browser and agent with WebMCP enabled; follow [Chrome's WebMCP setup instructions](https://developer.chrome.com/docs/ai/webmcp). Open the homepage and ask the agent:

```text
Use TypeShip's browser tools to find the guide for choosing Targets, then generate a TypeScript SDK from https://typeship.dev/openapi.yaml. Report the operation and file counts and whether any limits applied.
```

In a compatible browser's developer console, the [native imperative API](https://developer.chrome.com/docs/ai/webmcp/imperative-api) can also discover and call the tools:

```javascript
const tools = await document.modelContext.getTools();
const search = tools.find((tool) => tool.name === "typeship_search_docs");
const result = await document.modelContext.executeTool(
  search,
  JSON.stringify({ query: "choose targets" }),
);
console.log(result);
```

Tool results are plain text strings. Generation accepts `definition_url` and an optional `target` (`typescript-sdk`, `python-sdk`, `go-sdk`, `cli`, or `mcp`); the default is `typescript-sdk`. Use the returned link to generate and inspect files in the website. Navigation, sign-in state changes, and agent cancellation stop pending tool work; tools are removed when you leave their supported pages.

## If tools do not appear

WebMCP is an evolving browser experiment. TypeShip only registers tools when the native `document.modelContext.registerTool` API is present; there is no compatibility polyfill. Unsupported browsers retain the normal website and generator.

For agents outside a compatible browser, use the [CLI or hosted MCP server](https://typeship.dev/docs/guides/coding-agents), the [public API](https://typeship.dev/docs/api), or the markdown [runbook](https://typeship.dev/agents.md).

## Sitemap

[Documentation index](https://typeship.dev/llms.txt)