
Public listing and configuration home for serve — give anything on your machine a public HTTPS link
Public listing and configuration home for serve — give anything on your machine a public HTTPS link, from your agent. Implementation repository is private.
·
You already ask your AI to make things. Now ask it to share them.
you: "serve me this"
Claude: → https://lively-bison-4821.servelink.ccThat's the product. You say a sentence, and the thing you just made has a real URL — one you can text to a friend, drop into a Slack thread, or put on a slide. It works the same whether you built a Next.js app or asked for a sales deck, because serve doesn't care what the thing is. It only cares that you want someone else to see it.
serve is a hosted service. Create an account, log in once, and your links
live at *.servelink.cc.
About this repository. This is the public listing and configuration home for serve: the MCP registry manifest, the Claude Code plugin manifest, and the user documentation. serve is a commercial hosted service and its implementation repository is private. Everything you need to use serve is here or on npm — there is no build step, and nothing here needs compiling.
Every serve link is either live from your machine or kept alive on ours.
You don't choose up front, and you're never stuck with the choice. "Serve this so my teammate can watch while I work on it" gives you the first one. "Keep it up so they can read it tomorrow" gives you the second. Same link, same URL, one sentence apart.
That switch is the part people don't expect. Everywhere else, "let someone see what's on my laptop" and "put this on the internet" are two different products with two different setups, and moving between them is a project. Here they're two ways of phrasing the same request.
serve's real interface isn't the terminal. It's MCP, the protocol AI agents already speak, which means making a link isn't a task you go and do. It's something you mention. Your agent creates the link, tells you the URL, puts a password on it if you ask, and takes it down when you're finished. There's a CLI too, and it's a good one, but it's there for the times you'd rather drive manually.
This is also why serve isn't only for developers. If you can get Claude to build you a dashboard, you can get Claude to hand you the link to it. The skill it takes to share the thing is the one you already used to make it.
npm i -g @servelink/serve # npm is the primary channel
serve login # opens your browser to confirmThen tell your agent it exists. Anything that speaks MCP will do — Claude Code, Claude Desktop, Cursor, opencode:
{
"mcpServers": {
"serve": {
"command": "npx",
"args": ["-y", "@servelink/serve"]
}
}
}That's the whole setup. From here it's conversation: ask for a link, get a link.
If you installed globally with npm i -g, "command": "serve" with no args
works too and starts marginally faster.
Prefer Homebrew?
brew install servelink-swyftlabs/tap/serveOne account works across as many machines as you like.
This repository is also a Claude Code plugin marketplace, so you can skip the JSON:
claude plugin marketplace add servelink-swyftlabs/serve-mcp
claude plugin install serve@servelinkOr point Claude Code at a local clone while you try it:
claude --plugin-dir ./serve-mcpThe plugin ships the MCP server configuration in .mcp.json and
nothing else — no hooks, no agents, no code that runs on your machine beyond the
serve client itself.
None of these are commands. They're the kind of thing people actually say, and the agent works out the rest.
"Serve me this so I can check it on my phone."
"Put the deck somewhere my client can open it, and password-protect it."
"This link is going in an email, so make sure it still works next week."
"Take down everything I've got open."
"What am I sharing right now?"
From those, the agent decides whether the link should run from your machine or from ours, claims the subdomain, sets protection, and tells you what it did. If you've asked for something your plan doesn't cover, it says so rather than half-doing it.
lively-bison-4821 instead of a hash. On Pro you can ask for a specific one
and get goldenfish.servelink.cc.Underneath, it's QUIC end to end with per-stream flow control and real backpressure, and WebSocket upgrades that only report success once your local server has genuinely accepted the connection.
Two words worth pinning down, because the plans are built on them. A link is a URL you own. A tunnel is a link that's live right now. You can own any number of links on either plan; what the plans limit is how many run at once and how much traffic they carry.
| Free | Pro | |
|---|---|---|
| Price | $0 | $9.99/month |
| Links you own | Unlimited | Unlimited |
| Live at the same time | 3 | 10 |
| Largest single publish | 100 MB | 1 GB |
| Total stored | 1 GB | 50 GB |
| Transfer per month | 2 GB | 25 GB |
| Views on a published link | Unlimited* | Unlimited* |
| Password protection | — | Any link, any duration |
| Pick your own subdomain | — | Yes |
| Analytics | Opens | Opens, bytes, referrer, country |
| Publishes per hour / day | 30 / 100 | 300 / 1,000 |
* No per-link view cap and no per-viewer bandwidth quota. If traffic across the whole service ever threatens the monthly infrastructure budget, serve may pause new requests until it resets. Reaching a limit never deletes anything — your links and everything in them stay yours.
Tunnel tools move bytes, and a few of them gate or meter those bytes. None of them put a conversation in front.
| serve | ngrok free | Cloudflare Tunnel | Tailscale | |
|---|---|---|---|---|
| Public HTTPS URL for anyone | Yes | Yes | Yes | Funnel only¹ |
| Your agent drives it (MCP) | Yes | No | No | No |
| Hosts as well as tunnels | Yes | No | No | No |
| Stable subdomain, free | Yes | Paid | — | — |
| Streaming responses, free | Yes | Paid | — | — |
| Free tier with stated caps | Yes | Metered | Limited | — |
| Behind NAT, no open port | Yes | Yes | Yes | Yes |
¹ Tailscale gives you a private mesh — your own devices reaching one another. Handing a URL to somebody outside it needs Funnel, a separate feature.
The rows undersell it, though. Everywhere else, "let someone see my laptop" and "host this properly" are two different products you'd choose between. Here they're one link and a setting, and the setting is a sentence.
serve login runs an OAuth 2.0
device flow, and the relay only accepts links from a key that's already
yours.~/.serve/identity (mode 0600) that signs each registration and bind. A
subdomain belongs to that key, so nobody else can claim it or knock a live
tunnel offline — knowing your URL isn't enough.*.servelink.cc, it can
see tunneled traffic in plaintext. Don't tunnel production secrets or
anything you'd rather we weren't technically able to see. Published (hosted)
links are files you handed us on purpose, so the same applies to them by
definition.serve doctor tells you in one
command.serve doctorViewer → HTTPS → relay (QUIC edge, UDP 443)
│
▼
relay coordinator (hosted)
▲
│ QUIC streams (ALPN serve-tunnel/2)
│
your machine → localhost:PORTYour client registers with the hosted control plane and then dials out over UDP 443, which is why nothing needs an inbound port. Viewer requests and WebSockets map onto dedicated QUIC streams with end-to-end backpressure. Transport v2 is QUIC-only — no WebSocket fallback and no HTTP/2 downgrade — so a version mismatch fails loudly instead of quietly retrying.
README.md what you're reading
server.json MCP registry manifest (cc.servelink/serve)
.claude-plugin/ Claude Code plugin + marketplace manifests
.mcp.json MCP server configuration the plugin installs
docs/ user documentation
LICENSE proprietary noticeNo product source. The serve client is distributed as a signed binary through
npm and Homebrew; the relay, account API and worker are hosted components.
@servelink/serveservelink-swyftlabs/tap/serveProprietary — all rights reserved. See LICENSE. The documentation and manifests in this repository are published so that serve can be listed, installed and understood; that publication is not a grant of rights over the serve software or service.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add serve -- npx -y @servelink/serve{
"mcpServers": {
"serve": {
"args": [
"-y",
"@servelink/serve"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"serve","args":["-y","@servelink/serve"],"command":"npx"}'[mcp_servers.serve]
command = "npx"
args = ["-y", "@servelink/serve"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/serve to learn what the "serve" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npm i -g @servelink/servebrew install servelink-swyftlabs/tap/serve| Name | What it does |
|---|---|
account_status | Account-level state: plan, entitlement, and how much of the storage, transfer and publish allowance is used. Use this to check what the account may do or whether it is near a limit. For the links them |
create_viewer_grant | Create a single-use owner-browser bypass grant (Pro plan required) and return a bypass URL for the link. Use it to open a protected link in the browser without sharing the link's viewer credential; it |
doctor | Run self-diagnostics when a link is unreachable or a call fails: config and identity fingerprint presence, account API health, relay health, and outbound UDP 443 (QUIC) reachability, each reported as |
links | Inventory of every owned link (label) for the account, one record each: kind, URL, live/stale markers, protection status, last bound/viewer activity, and quarantine window. Use this to see what is cur |
list_tunnels | List all active tunnels in this manager with their ports, labels, public URLs, uptime, state, and last error. To inspect a single tunnel, use tunnel_status with its port or label. |
protect_link | Enable capability token and readable secret protection on an owned link (Pro plan required). Returns the share URL (with #cap=...) and the human-readable secret code. If label is omitted, the first ow |
release_link | Release (free) an owned link by label. Fails with remote_link while the label still has a published artifact; unpublish it with stop_remote first. Returns confirmation and the account's usage. |
renew_link | Rotate the capability token and secret code for a link (Pro plan required): fresh credentials are minted and the countdown restarts, and the previous credentials stop working immediately. If ttl is om |
revoke_link | Immediately revoke the active secret code and capability token for a link while keeping owner access intact. The link stays protected, so the old share URL and secret stop working; no new credentials |
serve | Publish a local resource to a public HTTPS URL. Pass path to serve a file or directory (auto-hosted, no separate server needed), or port to expose an already-running dev server. Set residency to "remo |
serve_file | Serve a local file or directory and get a public shareable URL. Pass the file or directory path to path to have it auto-hosted and tunneled. Use this when the user asks to share/serve a file, markdown |
stop_all_tunnels | Stop every active tunnel, revoking all public URLs. To stop a single tunnel, use stop_tunnel instead. |
stop_remote | Unpublish a remote link, deleting its stored artifact bytes immediately and returning the link to local residency. Use links to see published (remote) links. To stop a live tunnel, use stop_tunnel ins |
stop_tunnel | Stop (tear down) the tunnel for a local port or link label, revoking its public URL. Idempotent. To change a live tunnel's port or label, stop it here and then call serve again with the new settings; |
tunnel_status | Return the status of a single tunnel identified by its local port or its link label, including public URL, uptime, state, and last error. To see every active tunnel at once, use list_tunnels instead. |
unprotect_link | Clear protection on an owned link, returning it to public access. Use this to open up a protected link so anyone with the URL can view it. To keep the link protected but invalidate its current credent |
update_ttl | Change the protection duration (TTL) of an already-protected link (Pro plan required) without rotating its credentials. The link must currently be protected with an unexpired credential; expired prote |
Read live from the server on October 2, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/serve)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "serve" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.