Playwritermcp MCP

What playwritermcp-mcp MCP server does

The playwritermcp-mcp MCP server connects an MCP client to Playwriter Session Cloud, a hosted service for AI agent browser MCP sessions. Its interface is exposed as structured JSON tools rather than as source code that runs locally. The available operations cover opening a session, running stateful snippets, reading the current page state, and exporting a session log.

The service is intended for workflows where an agent or coding team needs a remote browser-session endpoint. The product documentation also describes public server metadata, token-based access, usage receipts, and audit-ready workflow evidence. The repository itself is not the production implementation; it serves as public documentation and a directory-submission reference.

How it works

The hosted MCP endpoint is available at https://playwritermcp.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint using Streamable HTTP. Production calls must include a bearer token in the Authorization header:

Authorization: Bearer <token>

The service exposes four tools:

• session_open opens a browser MCP session.
• run_stateful_snippet runs a snippet while retaining session state.
• read_page_state reads page state from the active session.
• export_session_log exports the session log.

The service also publishes a server card at https://playwritermcp.clauxel.com/.well-known/mcp/server-card.json, which can provide machine-readable server metadata to compatible tooling.

Setup and configuration

To use the playwritermcp-mcp MCP server, first visit the product website and select a plan. Create or request an API token, then configure an MCP client that supports remote Streamable HTTP servers with the published endpoint. Include the token as a bearer credential on JSON-RPC requests.

The README does not specify an environment variable configuration, local installation command, or package to run. No private production source is included in the repository. Unauthenticated browser visits to the MCP path return a JSON error rather than internal service details, so a valid token is required for production use.

Tools and capabilities

session_open provides the entry point for a browser MCP session. After a session is available, run_stateful_snippet supports code execution that preserves session state, while read_page_state retrieves the page state for inspection. export_session_log makes the session log available outside the active interaction.

Together, these tools support remote browser-session workflows that need both active state and a record of what occurred. The service documentation identifies usage receipts and workflow evidence as part of the hosted product, but it does not describe the internal format or fields returned by each tool.

Limitations and notes

The playwritermcp-mcp MCP server is a paid remote service, so access depends on a product plan and an issued token. It is not presented as a local server, and the repository does not contain the private production source. The documentation names Streamable HTTP support as a client requirement but does not list specific MCP clients.

The available material also does not define browser compatibility, session quotas, pricing details, token lifetime, or the exact schemas for tool inputs and outputs. Check the product page and server card for current service information before integrating it into a production workflow.