MCP server for coding agents

Let Claude Code, Cursor, Codex and other agents share what they build and hand you the link.

Updated 11 October 2026

Set up

npx -y @ouicu/mcp setup claude-code

For another tool, swap claude-code for cursor, codex, claude-desktop, vscode or windsurf. Setup logs you in if this computer isn't yet, then adds ouicu to the tool for every project.

Sharing a port also needs the command line tool, version 0.1.7 or later:

curl -fsSL https://ouicu.com/install.sh | sh

On Windows, in PowerShell:

irm https://ouicu.com/install.ps1 | iex

Or let your agent set it up

Paste this prompt into your coding agent. It installs the command line tool, runs setup for the tool the agent runs in, and adds a short section about ouicu to the instructions the agent reads in every project, such as ~/.claude/CLAUDE.md. You approve the login in your browser as usual: the prompt carries no key, and asks the agent to leave the key where setup saves it.

Set up ouicu on this computer for me, and remember what it does. ouicu (https://ouicu.com) gives a dev server on this computer a public https link, so I can open work in progress on my phone or send it to a client, and puts built static sites up at links that last. I have an account. 1. If `ouicu --version` fails, install ouicu's command line tool:   macOS and Linux: curl -fsSL https://ouicu.com/install.sh | sh   Windows, in PowerShell: irm https://ouicu.com/install.ps1 | iex 2. Add ouicu's MCP server to the tool you are running in:   npx -y @ouicu/mcp setup <tool>   where <tool> is the one you are: claude-code, codex, cursor, vscode, windsurf or claude-desktop.   If this computer isn't logged in to ouicu yet, it opens a page in my browser and waits until I approve it there, so give the command a few minutes. It keeps the key in ouicu's own credentials file, where the command line tool and the MCP server read it. Leave it there: don't put the key in any other file, in your memory or in a message. 3. Add the section below to your user-level instructions: the ones you read at the start of every session in every project, such as ~/.claude/CLAUDE.md for Claude Code or ~/.codex/AGENTS.md for Codex, not this project's files. Keep what is there, and replace an older ouicu section if there is one. If yours live only in your settings, show me the section to paste there. ```markdown## ouicuouicu is set up on this computer and logged in, with its MCP server.- Share a running dev server at a public https link: the ouicu_share_port tool, or `ouicu share <port>`, which keeps the link up while it runs.- Put a built static site up at a link that lasts: ouicu_deploy, or `ouicu deploy <folder>`.- ouicu_recent_requests says who opened a link and what failed.- When you finish a change I can look at, share the dev server with ouicu and give me the link. When I say it's for a client, build the site and deploy the build instead.- ouicu's key stays in its credentials file: never copy it anywhere.- More about ouicu: https://ouicu.com/llms.txt``` 4. Run `ouicu whoami` to check the login. Then tell me what setup said to do for the ouicu tools to appear, such as starting a new session.

Logging in

Setup shows a code and opens ouicu.com in your browser to approve it, as ouicu login does. The key is saved where the command line tool keeps it, never in the tool's settings, so the two share one login.

Without a key, the server starts with one tool, ouicu_login. Ask your agent to log in to ouicu: it opens the approval page in your browser, and the other tools appear without a restart. If the key stops working, ouicu_login comes back.

Ask for a link

Then ask in your own words. For example:

Start the dev server and send me a ouicu link.Build the site and put ./dist up at studiolund with a password.Who opened the preview, and did anything fail?

Links are public: anyone who has one can open it unless it has a password. On the Free plan, people opening a link in a browser first see a short notice from ouicu.

The guide Get a preview link from your coding agent walks through it from the start.

Tools

Tools the ouicu MCP server offers
Tool	What it does
`ouicu_share_port`	Shares a port at a public link while the server runs (port, and a name or password if you like).
`ouicu_stop_share`	Stops a share by name, id or link, here or anywhere on your account.
`ouicu_list_shares`	Live shares first, then the latest ended.
`ouicu_deploy`	Puts a built folder up at a link that lasts (folder, and a name, single-page app or password if you like).
`ouicu_list_sites`	Your uploaded sites.
`ouicu_delete_site`	Deletes a site and its files.
`ouicu_recent_requests`	The latest requests to a share or site: who opened it, and what failed.
`ouicu_usage`	The month's data against your plan's allowance.
`ouicu_whoami`	Your account and plan.

Shares end with the session

Shares the agent starts run inside the MCP server, and stop when it stops or with ouicu_stop_share. For a link that outlives the session, ask the agent to build and deploy instead. ouicu_deploy refuses a folder that is no build: one without an index.html, your home folder, or a project with a package.json or .git.

Set up by hand

Claude Code

claude mcp add -s user --transport stdio ouicu -- npx -y @ouicu/mcp

Other MCP clients

Start it as npx -y @ouicu/mcp, over stdio:

{  "mcpServers": {    "ouicu": { "command": "npx", "args": ["-y", "@ouicu/mcp"] }  }}

Settings

OUICU_API_KEY: a key from Account, instead of the saved login.
OUICU_BIN: the ouicu command to run, if it isn't on your PATH.