What the ouicu MCP server does
The ouicu MCP server connects coding agents to a site running on a developer's computer or to a locally available production build. It can make a development server reachable through a public HTTPS address, or upload the built site and return its address to the agent and developer.
This fits workflows where a teammate, client, or other reviewer needs to open an in-progress website without running the project locally. A reserved name can keep a consistent address for a client, while access controls described by the service include a password or a list of invited people. The service can also notify you by email when someone opens a shared site, and the last version can remain available while the laptop sleeps.
How it works
Install or invoke the @ouicu/mcp package through npx, then configure it for the MCP client you use. After setup, you can ask the agent in ordinary language for a link. For example, an instruction to build a gallery and provide an ouicu link allows the agent to share the development server or upload the resulting build, depending on the workflow.
The resulting address uses HTTPS and can be opened from a phone or another computer. The service handles web pages over HTTP and WebSockets. It is not intended as a general TCP tunnel, video delivery system, or download service.
Setup and configuration
The documented setup command is:
npx -y @ouicu/mcp setup claude-code
Replace claude-code with cursor, codex, vscode, windsurf, or claude-desktop when configuring one of those clients. The repository identifies the package as @ouicu/mcp, and the service is also listed in the official MCP Registry as com.ouicu/mcp.
The repository contains a separate @ouicu/sdk package for Node.js programs. That SDK requires Node 20 or later and accepts an OUICU_API_KEY when creating its client, but that variable is documented for the SDK example rather than as a required MCP server setting.
Tools and capabilities
The ouicu MCP server supports agent-driven workflows for:
- Sharing a running local development server.
- Uploading a built website.
- Returning the public share URL to the agent.
- Making web pages available over HTTP and WebSockets.
The accompanying SDK adds programmatic operations for sharing a port, uploading a built site, listing shares and sites, and checking who opened them. The README does not provide individual MCP tool names or schemas, so integrations should rely on the package's current MCP documentation for exact tool details.
Limitations and notes
ouicu is designed for web pages rather than arbitrary network services. The README specifically excludes TCP, video, and downloads. Availability, plans, and usage limits are documented separately by the service. This repository is a snapshot of packages developed in the main repository, so implementation history here may not represent every current upstream change.