
Autobrowserapproval Mcp
com.clauxel.autobrowserapprovalPublished by autobrowserapproval.clauxel.comOfficial publisherv1.0.0Updated Oct 28, 2026
A paid remote MCP for AI agent browser approval MCP, built to return verdicts, receipts, usage logs,
Overview
Paid hosted MCP endpoint that lets an AI agent request, record and export browser page approvals with receipts and usage logs.
- What you can do
- Request approval for a browser page and read the current session state
- Submit an approval result back to the service
- Export an approval receipt as audit-ready workflow evidence
- Return structured JSON responses and usage receipts for agent workflows
- When to use it
- For teams that need a recorded, auditable approval step before an AI agent acts on a browser page, and that are willing to pay for a hosted service rather than build approval tracking themselves.
- Requirements
- A remote Streamable HTTP MCP endpoint; no local package or runtime. A paid plan chosen on the product website and a bearer token issued there, sent in the Authorization header. Network access to the hosted endpoint.
Installation
In SourceWeft
- Open Autobrowserapproval Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.clauxel.autobrowserapproval%2Fautobrowserapproval-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"autobrowserapproval": {
"type": "http",
"url": "https://autobrowserapproval.clauxel.com/mcp"
}
}
}README
AutoBrowser Approval Cloud
Hosted MCP for AI agent browser approval MCP.
AutoBrowser Approval Cloud is a paid remote MCP endpoint for AI agent browser approval MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-ready workflow evidence for AI agents and coding teams.
Public Endpoints
- Website: https://autobrowserapproval.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25
- MCP endpoint: https://autobrowserapproval.clauxel.com/mcp
- Server card: https://autobrowserapproval.clauxel.com/.well-known/mcp/server-card.json
- Registry name:
com.clauxel.autobrowserapproval/autobrowserapproval-mcp
Access
This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.
Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.
Tools
request_page_approvalread_session_statesubmit_approval_resultexport_approval_receipt
Quick Start
- Open the website and choose a plan.
- Create or request an API token.
- Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
- Send JSON-RPC requests with the bearer token.
Useful Links
- Product page: https://autobrowserapproval.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25
- Pricing: https://autobrowserapproval.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r25#pricing
- Server card: https://autobrowserapproval.clauxel.com/.well-known/mcp/server-card.json
- MCP endpoint: https://autobrowserapproval.clauxel.com/mcp
Status
This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.
Source: README.md at commit cf9b5e5
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.