everything on skillbay as MCP tools, so your agent can search, read the evidence, install, submit, buy, and sell without leaving its editor. one remote server (Streamable HTTP, MCP 2026-07-28). no api keys, and no sign-in to browse, read, install free skills, or submit: the first time a call needs you (buying a paid skill, reading its files, selling, admin) the server asks and your client signs you in through the browser.
https://skillbay.sh/mcpclaude mcp add --transport http skillbay https://skillbay.sh/mcp
that is all for browsing and installing. to buy or sell, run /mcp inside claude code, pick skillbay, and choose authenticate (or just call a tool that needs it and follow the prompt).
skillbay, url https://skillbay.sh/mcp, leave the oauth fields empty → addfree, pro, max, team, and enterprise plans. on team and enterprise an owner adds it under organization settings → connectors → add → custom → web.
skillbay, description "search, install, submit, buy, and sell AI agent skills on skillbay", mcp server url https://skillbay.sh/mcp, authentication oauthplus, pro, business, enterprise, and edu plans, on the web app only (custom apps do not run in the mobile apps). business and enterprise workspaces need an admin to allow custom apps first.
codex mcp add skillbay --url https://skillbay.sh/mcp codex mcp login skillbay # only needed to buy or sell
or write it into ~/.codex/config.toml (shared by the cli, the codex app, and the vs code extension):
[mcp_servers.skillbay] url = "https://skillbay.sh/mcp"
codex app and vs code: settings → mcp servers → add server → name skillbay, streamable http, url https://skillbay.sh/mcp → save. codex mcp list shows what is configured.
{
"mcpServers": {
"skillbay": {
"type": "http",
"url": "https://skillbay.sh/mcp"
}
}
}cursor: add the JSON above to .cursor/mcp.json. any client that speaks Streamable HTTP works, with or without OAuth support; older clients that only speak the 2025 protocol are served too.
no sign-in. search, read the evidence, fetch the files of free skills
skillbay_list_categories | List the skill categories on skillbay (slug and display name). Use the slug with skillbay_search_skills. |
skillbay_search_skills | Search or browse approved skills on skillbay. |
skillbay_get_skill | Get one skill by slug: description, price, seller, the before-and-after examples (same prompt answered without and with the skill), the package file list, and the SKILL.md text. |
skillbay_get_seller | Get a seller by slug: bio, website, verified identities (X handle, email domain), and their approved skills. Use to judge who wrote a skill. |
skillbay_get_skill_files | Fetch the files of an approved skill's package so you can install it: SKILL.md and everything beside it, with text contents inline (binary files list only, with a URL). |
skillbay_read_skill_file | Read one text file from an approved skill's package by path (e.g. "SKILL.md", "scripts/run.sh"). Same access rules as skillbay_get_skill_files. Binary files are not returned; use the URL instead. |
skillbay_list_wanted | The "skills wanted" board: requests for skills that do not exist yet, posted by people who need them (like craigslist's wanted section). Live requests only, most recently posted or renewed first; each has a title, details, category, optional budget, and how many replies it got. No account needed. |
skillbay_get_wanted | One request from the "skills wanted" board: the full details of what the poster needs and what goes wrong today, plus budget and category. Reply with skillbay_reply_wanted. |
skillbay_post_wanted | Post to the "skills wanted" board on the user's behalf: what the skill should do, what goes wrong when agents try it today, a category, an optional budget, and the user's name and email. No account needed. |
skillbay_reply_wanted | Answer a "skills wanted" request on the user's behalf: their name, email, and a message saying what they would build and when. It is emailed to the poster, who answers the user directly; the poster's address is never exposed. No account needed. Ask the user before sending; do not invent contact information. Limit: 10 replies per IP per hour. |
no sign-in. the quick way (SKILL.md + email) or the full way with evidence
skillbay_submit_skill_quick | Submit a skill for review the quick way: just the SKILL.md text and contact details. No account needed. |
skillbay_submit_skill | Submit a skill for review with evidence. No account needed. Reviews weigh, in order: (1) worked examples of the same prompt answered WITHOUT and WITH the skill, (2) whether the submitter is a specialist in exactly this (job titles like "software engineer" are rejected; "postgres query planner tuning" passes), (3) the package. |
free skills need nothing; a paid skill asks you to sign in and returns a stripe checkout link
skillbay_whoami (sign-in) | The signed-in skillbay user: id, name, email, role (user or admin), and their seller accounts (slug + name). Call this first on the authenticated endpoint to learn the seller slug for the seller tools. |
skillbay_list_purchases (sign-in) | The signed-in user's orders: paid and refunded skills, with status and dates. Paid skills can then be read with skillbay_get_skill_files. |
skillbay_list_my_submissions (sign-in) | The signed-in user's skill submissions and where each stands in review. Submissions need no account, so this matches on the user's email against the contact email given at submission time. Status: "new" (waiting for review), "contacted" (in review, the reviewer emailed), "accepted" (seller invite sent), "rejected". |
skillbay_purchase_skill | Buy a skill. Free skills need no purchase and no account: this just confirms that and points at skillbay_get_skill_files (signed-in users get it recorded in their account, status "free"). Paid skills need a signed-in user and return a Stripe Checkout URL (status "checkout"): give it to the user to pay in a browser; you cannot complete payment. Status "owned" means they already have it. |
sign-in. listings, review, payouts, analytics for your seller account
skillbay_redeem_invite (sign-in) | Turn a seller invite (the token from the invite link skillbay.sh/sell?token=…) into a seller account for the signed-in user. If the invite came from an accepted submission, that skill is seeded as a draft listing. Returns the seller slug for the other seller tools. |
skillbay_list_listings (sign-in) | All listings of a seller account, every status (draft, submitted, approved, rejected, delisted), with review notes. |
skillbay_get_listing (sign-in) | One listing of a seller account by id, including its examples (before-and-after evidence). |
skillbay_create_listing (sign-in) | Create a draft listing on a seller account from text: SKILL.md plus optional extra files (the zip is built server-side) and the before-and-after examples. Drafts are private until submitted with skillbay_submit_listing; a listing needs at least one example before review. |
skillbay_update_listing (sign-in) | Update a listing's title, summary, description, category, and price; optionally replace the package (send skill_md and files) and the examples (send the full new list; it replaces the old one). Content changes to an approved listing send it back to review. |
skillbay_submit_listing (sign-in) | Send a draft, rejected, or delisted listing to the admin review queue. Needs at least one before-and-after example. Errors: "conflict" when the current status does not allow it. |
skillbay_withdraw_listing (sign-in) | Pull a submitted listing out of the review queue and back to draft, e.g. to fix it before it is reviewed. |
skillbay_delist_listing (sign-in) | Take an approved listing off the marketplace. Buyers keep what they bought. Resubmit later with skillbay_submit_listing. |
skillbay_start_stripe_onboarding (sign-in) | Get the Stripe onboarding link for a seller account (needed before posting paid skills). Give the URL to the user: Stripe collects identity and bank details in a browser; you cannot do it for them. Owners and admins of the seller account only. |
skillbay_get_seller_analytics (sign-in) | Traffic and sales for a seller account over 7, 30, or 90 days: views of their skill pages and seller page (people vs agents vs bots), installs, downloads, checkouts, purchases, revenue, by day and by skill, plus referring sites. |
sign-in as the admin. review queue, submissions, invites, site analytics
skillbay_admin_review_queue (sign-in) | Listings waiting for review, oldest first, each with its before-and-after examples. Judge the evidence first, then whether the seller is a specialist, then the package. Summarise for the admin and never approve or reject without their explicit go-ahead. |
skillbay_admin_approve_skill (sign-in) | Approve a submitted listing: it goes live, is published for install, and appears in search. Only with the admin's explicit go-ahead. |
skillbay_admin_reject_skill (sign-in) | Reject a submitted listing with a note the seller sees. Only with the admin's explicit go-ahead. |
skillbay_admin_list_submissions (sign-in) | Open skill submissions from the public form and API (newest first), optionally by status: new, contacted, accepted, rejected. Quick submissions (SKILL.md only) are flagged; they need evidence and specialization asked for by email. |
skillbay_admin_get_submission (sign-in) | One submission in full: contact details, examples, specialty and proof, the package manifest, and the SKILL.md. |
skillbay_admin_accept_submission (sign-in) | Accept a submission. A free skill goes live immediately: a seller account is created from the contact details, the listing is seeded with the package, evidence and reviewer runs, and the seller gets the live email. A paid skill emails the submitter a seller invite instead (Stripe first). Only with the admin's explicit go-ahead. |
skillbay_admin_contact_submission (sign-in) | Mark a submission as contacted, with an internal note (e.g. "asked for evidence by email"). |
skillbay_admin_reject_submission (sign-in) | Reject a submission; the note, if given, is emailed to the submitter. Only with the admin's explicit go-ahead. |
skillbay_admin_create_invite (sign-in) | Create a seller invite by hand (selling is invite-only). Returns the invite URL to send to the person. |
skillbay_admin_get_analytics (sign-in) | Site-wide analytics over 7, 30, or 90 days: totals (people vs agents vs bots), by day, by skill, searches including the ones that found nothing (demand with no supply: worth recruiting sellers for), referrers, utm campaigns, countries, page types. |
also exposed: resources skillbay://openapi.json, skillbay://categories, skillbay://skills/{slug}, and prompts with the same briefs as the "copy prompt for your agent" button. prefer plain HTTP? the same operations are at /openapi.json.
when a call needs you, the server answers with a standard OAuth 2.1 challenge (PKCE, dynamic client registration, RFC 9728 discovery). your MCP client registers itself, sends you to skillbay to sign in with an email code, google, or x, asks you to approve, and gets a token bound to this server. tools then act as you: buying spends your money, seller tools change your listings, admin tools only work for the admin. you can revoke access any time under my account.