{
  "markdown": "# serve\n\n**You already ask your AI to make things. Now ask it to share them.**\n\n[![smithery badge](https://smithery.ai/badge/servelink/servemcp)](https://smithery.ai/servers/servelink/servemcp)\n\n```\nyou:      \"serve me this\"\nClaude:   → https://lively-bison-4821.servelink.cc\n```\n\nThat's the product. You say a sentence, and the thing you just made has a\nreal URL — one you can text to a friend, drop into a Slack thread, or put on\na slide. It works the same whether you built a Next.js app or asked for a\nsales deck, because serve doesn't care what the thing is. It only cares that\nyou want someone else to see it.\n\n**serve is a hosted service.** Create an account, log in once, and your links\nlive at `*.servelink.cc`.\n\n> **About this repository.** This is the public listing and configuration home\n> for serve: the MCP registry manifest, the Claude Code plugin manifest, and the\n> user documentation. serve is a commercial hosted service and its\n> implementation repository is private. Everything you need to *use* serve is\n> here or on npm — there is no build step, and nothing here needs compiling.\n\n---\n\n## A link can live in two places\n\nEvery serve link is either **live from your machine** or **kept alive on\nours**.\n\n- **Live from your machine.** The link points at whatever is running on your\n  computer right now. Change a heading and the person holding the link sees\n  the new heading. Close your laptop and the link goes quiet. (Under the hood\n  this is a tunnel; your agent opens it for you.)\n- **Kept alive on ours.** We hold a copy on serve's servers. Your laptop can\n  be shut, asleep, or in a bag at the airport, and the link still opens.\n\nYou don't choose up front, and you're never stuck with the choice. \"Serve\nthis so my teammate can watch while I work on it\" gives you the first one.\n\"Keep it up so they can read it tomorrow\" gives you the second. Same link,\nsame URL, one sentence apart.\n\nThat switch is the part people don't expect. Everywhere else, \"let someone\nsee what's on my laptop\" and \"put this on the internet\" are two different\nproducts with two different setups, and moving between them is a project.\nHere they're two ways of phrasing the same request.\n\n## You never operate it — your agent does\n\nserve's real interface isn't the terminal. It's MCP, the protocol AI agents\nalready speak, which means making a link isn't a task you go and do. It's\nsomething you mention. Your agent creates the link, tells you the URL, puts\na password on it if you ask, and takes it down when you're finished. There's\na CLI too, and it's a good one, but it's there for the times you'd rather\ndrive manually.\n\nThis is also why serve isn't only for developers. If you can get Claude to\nbuild you a dashboard, you can get Claude to hand you the link to it. The\nskill it takes to share the thing is the one you already used to make it.\n\n## Quick start\n\n```bash\nnpm i -g @servelink/serve     # npm is the primary channel\nserve login                   # opens your browser to confirm\n```\n\nThen tell your agent it exists. Anything that speaks MCP will do — Claude Code,\nClaude Desktop, Cursor, opencode:\n\n```json\n{\n  \"mcpServers\": {\n    \"serve\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@servelink/serve\"]\n    }\n  }\n}\n```\n\nThat's the whole setup. From here it's conversation: ask for a link, get a link.\n\nIf you installed globally with `npm i -g`, `\"command\": \"serve\"` with no `args`\nworks too and starts marginally faster.\n\nPrefer Homebrew?\n\n```bash\nbrew install servelink-swyftlabs/tap/serve\n```\n\nOne account works across as many machines as you like.\n\n## Claude Code plugin\n\nThis repository is also a Claude Code plugin marketplace, so you can skip the\nJSON:\n\n```bash\nclaude plugin marketplace add servelink-swyftlabs/serve-mcp\nclaude plugin install serve@servelink\n```\n\nOr point Claude Code at a local clone while you try it:\n\n```bash\nclaude --plugin-dir ./serve-mcp\n```\n\nThe plugin ships the MCP server configuration in [`.mcp.json`](.mcp.json) and\nnothing else — no hooks, no agents, no code that runs on your machine beyond the\n`serve` client itself.\n\n## Things you can just ask for\n\nNone of these are commands. They're the kind of thing people actually say, and\nthe agent works out the rest.\n\n> \"Serve me this so I can check it on my phone.\"\n\n> \"Put the deck somewhere my client can open it, and password-protect it.\"\n\n> \"This link is going in an email, so make sure it still works next week.\"\n\n> \"Take down everything I've got open.\"\n\n> \"What am I sharing right now?\"\n\nFrom those, the agent decides whether the link should run from your machine or\nfrom ours, claims the subdomain, sets protection, and tells you what it did. If\nyou've asked for something your plan doesn't cover, it says so rather than\nhalf-doing it.\n\n## What you get\n\n- **Links you own for good.** A link is yours from the moment you make it —\n  never recycled, never evicted, never expired to free up room. Reconnect a\n  week later and it's the same URL, so a tab someone left open still works.\n- **Names you can read out loud.** Every link gets something like\n  `lively-bison-4821` instead of a hash. On Pro you can ask for a specific one\n  and get `goldenfish.servelink.cc`.\n- **A password whenever you want one** (Pro), on any link, lasting an hour or a\n  month. Revoke it and the people already looking are out immediately.\n- **Real applications, not just static files.** Streaming responses,\n  server-sent events, WebSockets, big downloads, and the fifteen-odd parallel\n  requests a modern page fires the moment it loads.\n- **It works from wherever you are.** Your machine dials outward, so home NAT,\n  office firewalls, and hotel WiFi are all fine. No inbound port, no router\n  settings, nothing to ask IT for.\n- **A free tier with actual numbers in it** — 2 GB of transfer a month and 3\n  live links at once — rather than a meter that surprises you later.\n\nUnderneath, it's QUIC end to end with per-stream flow control and real\nbackpressure, and WebSocket upgrades that only report success once your local\nserver has genuinely accepted the connection.\n\n## Free vs Pro\n\nTwo words worth pinning down, because the plans are built on them. A **link**\nis a URL you own. A **tunnel** is a link that's live right now. You can own any\nnumber of links on either plan; what the plans limit is how many run at once\nand how much traffic they carry.\n\n| | Free | Pro |\n|---|---|---|\n| Price | $0 | $9.99/month |\n| Links you own | Unlimited | Unlimited |\n| Live at the same time | 3 | 10 |\n| Largest single publish | 100 MB | 1 GB |\n| Total stored | 1 GB | 50 GB |\n| Transfer per month | 2 GB | 25 GB |\n| Views on a published link | Unlimited\\* | Unlimited\\* |\n| Password protection | — | Any link, any duration |\n| Pick your own subdomain | — | Yes |\n| Analytics | Opens | Opens, bytes, referrer, country |\n| Publishes per hour / day | 30 / 100 | 300 / 1,000 |\n\n\\* No per-link view cap and no per-viewer bandwidth quota. If traffic across\nthe whole service ever threatens the monthly infrastructure budget, serve may\npause new requests until it resets. Reaching a limit never deletes anything —\nyour links and everything in them stay yours.\n\n## How serve compares\n\nTunnel tools move bytes, and a few of them gate or meter those bytes. None of\nthem put a conversation in front.\n\n| | serve | ngrok free | Cloudflare Tunnel | Tailscale |\n|---|---|---|---|---|\n| Public HTTPS URL for anyone | **Yes** | Yes | Yes | Funnel only¹ |\n| Your agent drives it (MCP) | **Yes** | No | No | No |\n| Hosts as well as tunnels | **Yes** | No | No | No |\n| Stable subdomain, free | **Yes** | Paid | — | — |\n| Streaming responses, free | **Yes** | Paid | — | — |\n| Free tier with stated caps | **Yes** | Metered | Limited | — |\n| Behind NAT, no open port | **Yes** | Yes | Yes | Yes |\n\n¹ Tailscale gives you a private mesh — your own devices reaching one another.\nHanding a URL to somebody outside it needs Funnel, a separate feature.\n\nThe rows undersell it, though. Everywhere else, \"let someone see my laptop\" and\n\"host this properly\" are two different products you'd choose between. Here\nthey're one link and a setting, and the setting is a sentence.\n\n## Security, and one thing you should know\n\n- **Your device is bound to your account.** `serve login` runs an OAuth 2.0\n  device flow, and the relay only accepts links from a key that's already\n  yours.\n- **Every request is signed.** Your machine holds an Ed25519 key at\n  `~/.serve/identity` (mode 0600) that signs each registration and bind. A\n  subdomain belongs to that key, so nobody else can claim it or knock a live\n  tunnel offline — knowing your URL isn't enough.\n- **Revocation is fast.** Revoke a device in the dashboard and new binds stop\n  immediately; live tunnels drop as the revocation reaches the relay.\n- **The relay terminates TLS.** This is the one we'd rather you heard from us:\n  because serve's relay presents the certificate for `*.servelink.cc`, it can\n  see tunneled traffic in plaintext. Don't tunnel production secrets or\n  anything you'd rather we weren't technically able to see. Published (hosted)\n  links are files you handed us on purpose, so the same applies to them by\n  definition.\n- **QUIC-only, UDP 443, no fallback.** If your network blocks outbound UDP,\n  serve fails clearly instead of degrading. `serve doctor` tells you in one\n  command.\n\n## Documentation\n\n- [Getting started](docs/getting-started.md) — the walkthrough, from install to\n  your first link\n- [CLI reference](docs/cli.md) — every command, its flags, and config precedence\n- [MCP tools](docs/mcp.md) — all seventeen, and what their results carry\n- [Preview modes](docs/preview-modes.md) — production vs HMR, and how to read a\n  WebSocket failure\n- [Troubleshooting](docs/troubleshooting.md) — or just run `serve doctor`\n\n```\nViewer → HTTPS → relay (QUIC edge, UDP 443)\n                    │\n                    ▼\n           relay coordinator (hosted)\n                    ▲\n                    │ QUIC streams (ALPN serve-tunnel/2)\n                    │\n          your machine → localhost:PORT\n```\n\nYour client registers with the hosted control plane and then dials **out** over\nUDP 443, which is why nothing needs an inbound port. Viewer requests and\nWebSockets map onto dedicated QUIC streams with end-to-end backpressure.\nTransport v2 is QUIC-only — no WebSocket fallback and no HTTP/2 downgrade — so a\nversion mismatch fails loudly instead of quietly retrying.\n\n## What's in this repository\n\n```\nREADME.md              what you're reading\nserver.json            MCP registry manifest (cc.servelink/serve)\n.claude-plugin/        Claude Code plugin + marketplace manifests\n.mcp.json              MCP server configuration the plugin installs\ndocs/                  user documentation\nLICENSE                proprietary notice\n```\n\nNo product source. The `serve` client is distributed as a signed binary through\nnpm and Homebrew; the relay, account API and worker are hosted components.\n\n## Links\n\n- Website — [servelink.cc](https://servelink.cc)\n- npm — [`@servelink/serve`](https://www.npmjs.com/package/@servelink/serve)\n- Homebrew — `servelink-swyftlabs/tap/serve`\n- Support — [serve@servelink.cc](mailto:serve@servelink.cc)\n\n## License\n\nProprietary — all rights reserved. See [LICENSE](LICENSE). The documentation and\nmanifests in this repository are published so that serve can be listed,\ninstalled and understood; that publication is not a grant of rights over the\nserve software or service.\n\n\n\n\n\n",
  "bytes": 11431,
  "sha": "ca4ef8d5c8fcae443fa2f22fb07a316cbd169500a7801e8f8c029742b35561a0",
  "repo_slug": "servelink-swyftlabs/serve-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_cc_servelink_serve_34d3fc88/readme"
}