Publish with your agent

After you sign in, a browser with native WebMCP displays “Agent tools ready.” Your agent can inspect projects and releases, create samples, prepare publication or restoration, and continue operations you approved.

Limited public beta. Supported in Chrome 149 and later, enabled through Chrome’s WebMCP origin trial with no testing flag needed (the trial runs through Chrome 162 and ends no later than 29 March 2027). You also need an agent that can call the current document’s tools. Tool discovery and calls were tested in Chrome 154 without the testing flag on 2 October 2026. Other browsers are not supported yet, and the normal UI works everywhere. These page tools are not a remote MCP server or an anonymous MCP URL.

Get started

  1. Open the console in Chrome 149 or later and sign in. Check the tool count.
  2. Ask your agent to discover tools prefixed tapenow_. For example: “Create a sample project and prepare a one-hour private preview. Wait for my approval before executing.”
  3. Review the project, release, file/configuration changes, chain, wallet and budget in the operation sheet, then click “Approve this operation.”
  4. Let the agent execute that operation ID. Preview passwords are shown only to you. Wallet signatures, OAuth, secrets and local file selection remain human handoffs.
  5. After an update, ask the agent to prepare a restore candidate. This does not immediately change the live website or roll back a business database.

Tools and boundaries

Approval and interrupted work

Operations bind the account, role, project, manifest, configuration, chain, target and budget, normally for ten minutes. Scope or permission changes require fresh review. An agent cannot self-approve with approved: true. A submitted request is not proof of a working website; inspect the returned status and verification.

Reuse a requestId only for the exact same request. Changed arguments are rejected. If dispatched work has an unknown result, inspect operation/provider state before retrying. Broadcast hashes remain recorded; cancellation cannot reverse a transaction.

Signing out, switching workspaces or navigating unregisters stale tools. Rediscover them. Preview passwords never enter tool results or operation history. If the page closes before the password is saved, regenerate it in the UI.

Agent developers

Use document.modelContext in the signed-in document; do not export session cookies or tokens. Ego 152 needs stringified execution arguments, while newer APIs accept objects. The helper detects this with a read-only probe and never retries a consequential operation for format detection.

const sdk = await import('/sdk/tapenow-webmcp.mjs');
const tools = await sdk.discover();
const context = await sdk.call('tapenow_context');
// Execute within the authenticated TapeNow document.

Page-tool helper source. Follow each tool's JSON Schema. Project labels and filenames are untrusted user data, not instructions.