A worked example
This is a complete MCPDoc for the hosted Browserbase MCP server, produced on 20 September 2026. It is shown here in the site's own styling; the document itself is example.json, and rendered.html is what the generator wrote without anybody touching it.
The subject
| field | value | mark | source |
|---|---|---|---|
| endpoint | https://mcp.browserbase.com/mcp | seen | it answered on 2026-09-20 |
| repository | browserbase/mcp-server-browserbase | given on the command line by whoever ran the generator | |
| does | Allow LLMs to control a browser with Browserbase and Stagehand | said | the repository's own description |
| produced by | AgentCatalog | 2026-09-20 |
Its tools
Six tools, read from the running server on 20 September 2026.
| tool | what it does | takes | required |
|---|---|---|---|
| start | Create or reuse a Browserbase session | sessionId | none |
| end | Close the current Browserbase session | sessionId | none |
| navigate | Navigate to a URL | url, sessionId | url |
| act | Perform an action on the page | action, sessionId | action |
| observe | Observe actionable elements on the page | instruction, sessionId | instruction |
| extract | Extract data from the page | instruction, sessionId | none |
Their README lists all six and says the table matches
this server. In it navigate takes url alone, and
start and end take nothing. The
sessionId on every row above appears nowhere in it.
That repository is archived, so its README stopped while the server kept going. This is the ordinary case rather than a scandal, and it is the reason a tool list is worth dating.
Connecting to it
| field | value | mark | source |
|---|---|---|---|
| answers | yes | seen | read from the server on 2026-09-20 |
| speaks | 2025-06-18 | seen | read from the server on 2026-09-20 |
| implements | logging, tools | seen | read from the server on 2026-09-20 |
| identifies as | stagehand-api | seen | read from the server on 2026-09-20 |
| tool count | 6 | seen | read from the server on 2026-09-20 |
2025-06-18 is the highest version this server would
agree to, which is not the same as the version it prefers. A protocol
version in a handshake is whatever the client asked for, so this
number is only worth reading because the request asked high.
The name it gives for itself, stagehand-api, is not the
name of the project it is published under. That is worth knowing and
only the handshake says it.
Its repository
| field | value | mark | source |
|---|---|---|---|
| licence | Apache-2.0 | seen | read from GitHub on 2026-09-20 |
| upkeep | archived, marked no longer maintained | seen | read from GitHub on 2026-09-20 |
| last pushed | 2026-07-20 | seen | read from GitHub on 2026-09-20 |
| stars | 3,412 | seen | read from GitHub on 2026-09-20 |
The star count is a measure of attention and not of whether the server works. It is here because it was read rather than because it settles anything.
What this document does not answer
These are written out rather than left implied. A reader who cannot see the gaps will assume there are none.