This skill covers adding a remote MCP server and its tools to a web product, adding OAuth to it, and listing it in directories. It starts with one hosted endpoint proven by one real client, and builds packages or submissions only when the owner chooses them.
It sets the decisions to record first, the rules every change meets, and a seven-step build order from REST functions to publishing. Examples use Next.js, Supabase, Clerk and Netlify.
What You Get
- A decision table covering anonymous access, who may connect, what agents must never do, missing workspaces and the endpoint path
- Rules for tool copy, annotations, output schemas, a list-size budget and per-call logging
- A seven-step build order from REST functions to publishing from production
- Reference files for the route, the tools, directories, clients and the companion package
- A rule that a client counts as supported only after a recorded happy path
Common Use Cases
- Adding an MCP endpoint to a SaaS so outside agents can use it
- Adding OAuth sign-in to an MCP server with Clerk
- Preparing a listing for an MCP directory or registry
- Updating listings and the stdio package after a tool description changes
What Makes It Unique
It treats tool descriptions and instructions as product copy where every sentence is a claim, since directories score them and agents choose tools from them alone. It also puts authorization first because a tool is a route, and says a client another product verified is still unverified for yours.
Under The Hood
The skill is instructions and reference markdown, with no scripts. Following it, the agent writes route, tool and test code in the product, runs shell commands to build and test, calls the product’s own endpoint with a real MCP client, and checks which account the GitHub CLI is logged in as before any listing. It reads current directory pages on the web before each submission, and publishes a package or listing only on the owner’s go. Authentication follows the clerk-production and saas-authorization skills.