Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Share a dev server or upload a built site at a public https link, and hand the link back.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
OUICU_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ouicu": {
"command": "npx",
"args": [
"-y",
"@ouicu/mcp"
],
"env": {
"OUICU_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add ouicu --env OUICU_API_KEY=your-value -- npx -y @ouicu/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ouicu": {
"command": "npx",
"args": [
"-y",
"@ouicu/mcp"
],
"env": {
"OUICU_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ouicu": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ouicu/mcp"
],
"env": {
"OUICU_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain ouicu.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: OUICU_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 30 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
npx -y @ouicu/mcp setup claude-code
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:
claude mcp add -s user --transport stdio ouicu -- npx -y @ouicu/mcp
Any other MCP client starts it as npx -y @ouicu/mcp (stdio):
{
"mcpServers": { "ouicu": { "command": "npx", "args": ["-y", "@ouicu/mcp"] } } }
Sharing a port also needs the ouicu CLI, 0.1.7 or later (0.1.8 to share with only invited people):
curl -fsSL https://ouicu.com/install.sh | sh
On Windows, in PowerShell:
irm https://ouicu.com/install.ps1 | iex
| Tool | What it does |
|---|---|
ouicu_share_port | Shares a port at a public link while the server runs (port, name?, password?, allow?) |
ouicu_stop_share | Stops a share by name, id or link, here or anywhere on the account |
ouicu_list_shares | Live shares first, then the latest ended |
ouicu_deploy | Puts a built folder up at a link that lasts (directory, name?, spa?, password?) |
ouicu_list_sites | The account's 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 the plan's allowance |
ouicu_whoami | The account and plan |
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.
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.
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.
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:
import { createServer } from "@ouicu/mcp";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
await createServer().connect(new StdioServerTransport());
MIT