tablaze
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tablazeOpen example.com, check the title says 'Example Domain', then close the tab"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Give your agent a browser it can work with. Tablaze connects Codex and other MCP clients to Chromium through eight focused tools. Inspect a page, fill a form, extract a result, and check that the task actually succeeded.
Built with Playwright. Browser sessions stay running between calls; your MCP client supplies the reasoning. No additional model API key required.
See it work
A real MCP SDK client searches for a stay in Lisbon, verifies five outcomes, then encounters a replaced button and recovers with a fresh observation. The recording shows actual tool responses and browser captures.

Observe the form → Fill · select · check · search → Verify the result
Reproduce the recording · Inspect the full trace
Related MCP server: hronaut
Get started
Requires Node.js 20+, npm and Git. This is a developer preview; npm publication is pending, so install from source:
git clone https://github.com/SweetDianDian/tablaze.git
cd tablaze
npm ci
npm run build
node dist/cli.js setupFor installed Chrome, skip setup, run node dist/cli.js doctor --channel chrome, and append --channel chrome to the Codex command below. This launches a separate browser session.
On Linux, use npx playwright install --with-deps chromium in place of setup to install the browser and system dependencies.
Connect Codex
From the cloned directory, register the built server:
codex mcp add tablaze -- "$(node -p 'process.execPath')" "$PWD/dist/cli.js"
codex mcp get tablazeThen ask Codex:
Use Tablaze to open https://example.com, read the heading and links, verify that the title contains “Example Domain”, then close the session. Report the result of the checks.
Complete Codex setup covers desktop configuration, browser selection and troubleshooting. Other MCP clients can launch the same node /absolute/path/to/tablaze/dist/cli.js command over stdio.
A small loop, with useful controls
Capability | What it gives your agent |
Warm sessions | Keep page state between calls. Temporary, isolated browser contexts by default; explicit CDP attachment for an existing profile. |
Compact observations | Full or incremental snapshots with element refs, text budgets and visible truncation. |
Guarded actions | Check snapshot revisions and DOM targets before input. Re-observe when a target changes. |
Ordered batches | Send up to 20 actions in one call, with completed, failed and skipped steps. Stops on error; earlier effects remain. |
Explicit verification | Check the resulting URL, title, text, field values, visibility and element counts. |
Eight tools
Tool | Use it to |
| Open a page and receive its first snapshot. |
| Observe the page, changes or a selected frame. |
| Click, fill, press, select, check, scroll or wait. |
| Test explicit assertions against the current page. |
| Read text, links or tables. |
| Capture a JPEG screenshot. |
| Inspect owned sessions. |
| Close a session and release its resources. |
Explore the project
Guide | Inside |
Copyable configuration, tool arguments and troubleshooting. | |
Reference lifetime, batch semantics, browser modes and current limits. | |
Reproduce the local workload and inspect every raw sample. | |
Real browser, SDK and Codex results, with their measured scope. | |
Data handling, resource ownership and private reporting. | |
Build the npm tarball and source archive. |
Ubuntu CI on Node 20 and 22 passed the build, browser/MCP tests and package inspection. To check a source checkout yourself, run npm test; use npm run bench for the separate local benchmark.
Contribute
Bring a reproducible browser case, improve a guide, or send a focused fix. Open an issue · Submit a pull request · Read the contribution guide
This server cannot be deployed
Maintenance
Related MCP Connectors
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Hyperbrowser MCP — wraps the Hyperbrowser AI-agent browsing API
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to operate an isolated local Chromium browser through MCP, with semantic snapshots, ref-based actions, search, research, crawling, and CDP access.Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a persistent local browser with live tabs, navigation, interaction, inspection, and state management through MCP.5-
- AlicenseNot gradedqualityCmaintenanceProvides a headless Chromium browser through MCP, enabling AI agents to browse JavaScript-rendered pages, search the web, capture screenshots, extract tables and data, and run stateful multi-step interactions like clicking, typing, and form submission.1,236,914 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to control and inspect a live Chrome browser via MCP, including performance tracing, network and console debugging, screenshots, and reliable Puppeteer-based automation.1,026,016 npmApache 2.0