Best for
- Developers integrating browser access through MCP
- Users who can verify the npm package and replace the template placeholders
I
io.github.username/mcp-server-{{name}}
Community
An MCP server template for browser access
GitHub source repository ↗
24FMRS · D
The source confirms an active version 1.0.0 browser-access MCP server template with stdio, SSE, and Streamable HTTP options. It does not provide named tools, client compatibility, authentication details, or a precise permission list.
This entry is the default MCP server template in the UI-TARS-desktop repository and is described as providing browser-use access. It is configured for npm-based execution over stdio, SSE, and Streamable HTTP. The server name, repository URL, and npm identifier still contain {{name}} or username placeholders, so the source does not establish a concrete server identity or published package.
Tools
The tool list has not been reviewed yet.
Setup
Replace username and {{name}} in the manifest with actual values and verify that the corresponding npm package is available. The stdio transport runs the npm package directly. SSE and Streamable HTTP use npx, with port 8089 by default and endpoints /sse and /mcp respectively.
Fit and risk
Not for
- Users seeking a server with confirmed official ownership
- Workloads requiring a documented tool list, authentication model, or permission scope
Required permissions
- Browser access is required, but the specific permission scope is not described in the source
Risks and side effects
- The server identity, npm package, and repository URL remain template placeholders
- The actual scope of browser access is unspecified and should be reviewed before deployment
- The SSE and Streamable HTTP configurations use 127.0.0.1, so port conflicts may prevent startup
Troubleshooting
- Check that username and {{name}} placeholders have been replaced
- Verify that the npm package is published and correctly identified
- Check whether port 8089 is available or provide another port
- Use /sse for SSE and /mcp for Streamable HTTP
Use cases
Providing browser access to MCP-compatible clients
Testing transport configuration for a browser-oriented MCP server
Supported clients
Supported clients have not been confirmed yet.