ouicu
com.ouicuv0.1.2Updated Oct 8, 2026
Share a dev server or upload a built site at a public https link, and hand the link back.
Overview
Lets a coding assistant share a running dev server or publish a built site at a public link and return that link.
- What it does
- The server exposes tools to share a local port at a public link while the server runs, stop or list shares, deploy a built folder to a lasting link, list or delete the account's sites, and check recent requests, monthly usage and account details. Each tool answers in plain words an agent can pass on, plus structured content. Without a key it starts with only a login tool and adds the rest after approval.
- When to use it
- Use it when an assistant should hand back a shareable link to a dev server or a built site, for example to show a landing page to someone or to let a client preview work. It fits coding-agent workflows where publishing a preview is part of the task.
- Requirements
- Runs locally over stdio, normally started with npx from the npm package @ouicu/mcp. Sharing a port also needs the ouicu CLI 0.1.7 or later (0.1.8 for invite-only shares). Authentication is either the saved ouicu login or the OUICU_API_KEY environment variable; no key is required to start, since the server can log in through the browser. Desktop only.
Installation
In SourceWeft
- Open ouicu in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@ouicu/mcp
An MCP server for ouicu. A coding agent can share the dev server it is working on, or put a built site up, and hand back a link to send to someone: "build the landing page and send me a link" in one turn.
Set up
or claude-desktop, cursor, vscode, codex, windsurf. If this
computer is not logged in to ouicu, it logs you in first: it shows a code,
opens ouicu.com in your browser to approve it, and saves the key where the
ouicu CLI keeps it. Then it adds the server to the tool, for every
project. The key never goes into the tool's settings; the server reads it
from the credentials file, so ouicu login and the server share one login.
When the tool's own command (claude, codex) is missing, it prints the
command to run by hand. For Claude Code that is:
Any other MCP client starts it as npx -y @ouicu/mcp (stdio):
Sharing a port also needs the ouicu CLI, 0.1.7 or later (0.1.8 to share with only invited people):
On Windows, in PowerShell:
Tools
Each answers in words an agent can pass on, with the same as structured content. Links are public: anyone who has one can open it unless it has a password or is only for invited people. On the Free plan, people opening a link in a browser first see a short notice from ouicu saying who shared it.
Shares the server starts run inside it, through the CLI, and stop when it
stops or with ouicu_stop_share. For a link that outlives the session,
use ouicu_deploy.
Only invited people
On Pro, ouicu_share_port takes allow: email addresses, or @ and a
domain (@client.com) for everyone at one. Only those people can open the
link. ouicu does not send it to them; you do, as with any link. On opening
it, each types their email address on ouicu's page and, if it is on the
list, gets a sign-in link by email. Your own address always gets in.
allow does not go with password. The tool says when only invited
people can open a share, and ouicu_list_shares and ouicu_list_sites
say "only invited people can open it" for those.
Asking again for a port the server already shares hands back that share only when the same people can open it (anyone, the same password or the same list); otherwise the tool says to stop it first.
Without a key
The server starts with one tool, ouicu_login. It opens the approval page
in the person's browser when it can (otherwise it answers with the code
and the address for the agent to pass on) and waits for the approval. The
other tools then appear without a restart. When the saved key stops
working, ouicu_login comes back.
Settings
The server reads OUICU_API_KEY (a key from ouicu.com, instead of the
saved login), OUICU_API (another ouicu than ouicu.com), OUICU_TUNNEL
and OUICU_BIN (the CLI to run). From code:
License
MIT
Source: packages/mcp/README.md at commit b7f925c
Tools
0Version history
1- v0.1.2LatestOct 8, 2026


