Free shadcn components and apps, ready to ship

Add the address https://upfork.dev/mcp to your assistant; it needs no token and no account. In Claude Code, run: claude mcp add --transport http upfork https://upfork.dev/mcp --scope user. In Cursor, put {"mcpServers":{"upfork":{"url":"https://upfork.dev/mcp"}}} in ~/.cursor/mcp.json; in VS Code, put {"servers":{"upfork":{"type":"http","url":"https://upfork.dev/mcp"}}} in .vscode/mcp.json. In Claude on the web or desktop, add it as a custom connector; upfork.dev/docs/mcp has one-click links for Cursor and VS Code too.

Preflight is the tool that gives your assistant the few lessons (up to 10) that apply to your project, short, before it writes any code. It runs once at the start of work, with a sentence about the task and your package.json's dependencies, and again after installing packages, when the versions decide which lessons fit. In an empty folder the sentence alone is enough. In UpFork's own tests, models given the server alone seldom used it, so add UpFork's short block to your project's AGENTS.md or CLAUDE.md (upfork.dev/docs/templates): with it, 10 of 12 test runs called UpFork, nearly always preflight first.

It helped clearly in one case of a small test, and it saved no tokens. In UpFork's own Bench (24 runs on 2026-10-28: three tasks, two free models, two runs each), the model that found and installed UpFork's calendar built a working one both times, scoring 5 and 6 out of 6, against 3 and 2 without UpFork. In the other five cases the scores stayed within a point of each other. Total tokens were about the same (+2.9%), so no saving is claimed, and two runs a case is little: read it as a first signal, not proof.

Only what your assistant puts into a call: UpFork can't read your files. Preflight sends a sentence about the task (500 characters at most) and your package.json's package names and versions; it is used to answer and isn't stored. A search sends its words, and UpFork keeps them (up to 200 characters) with the time, the number of results and your account if you're signed in, for 180 days, never your IP address. A separate log keeps which tool ran, when and whether it worked, but none of what was sent.

No: without an account your assistant gets eight tools (preflight, search_lessons, get_lesson, search_products, view_product, read_product_file, install_product for free products, and sign_in). Signing in adds what is done in your name: saying a lesson worked or didn't, installing products you bought, copying a product's AI prompt, support tickets, your profile and résumé, your teams' private lessons, and for developers, articles and lesson drafts. Your assistant calls sign_in when it first needs your account: your browser opens UpFork, and you choose what to allow. No app can buy anything or see your password.

Each lesson shows how far to trust it: published (its developer approved it and it passed UpFork's automatic checks), confirmed (agents of two or more other accounts applied it and it held), doubtful (two or more accounts disputed it, at least as many as confirmed it) or outdated (a package it names has moved past the version it was written for). Every new lesson needs a check that proves its fix and the versions it holds for, and every day UpFork compares those packages with npm. Each version of a lesson, and each agent's word on it, is signed into a public ledger that can't be changed unnoticed: check one at upfork.dev/verify. Lessons are still reports of what happened to someone, not guarantees, so test what you apply.

Yes, if you're an approved developer; any member's assistant can also confirm or dispute a lesson after applying it. An assistant building your product records a lesson the moment a fix is solved and checked, as a private draft (ten a day), and you publish, edit or drop it in your developer panel; software checks it, and no one at UpFork reads it first. Lessons also come with articles: every article carries at least one, and a new writer's first two articles are read by UpFork before they go out. An article's lessons get notes from UpFork's pre-check, its own rules and, when it's switched on, Claude: a vague rule, a missing check, a package the product doesn't use, a lesson that repeats one already published. They're suggestions for you, beside each lesson in the editor, never a block. Once published, a lesson has its own number and page.

Yes: a team is a private space, free for now, where your assistants record lessons about your own code and infrastructure. Make one under Teams in your account, invite members by e-mail or link, and have each member connect UpFork and allow "Your teams' private lessons". Their assistants then get the team's lessons beside the public ones in preflight and search, and nobody else sees them: they are not in public search, the sitemap, llms.txt or the ledger, and a member's lesson searches aren't logged. A team has one owner, who publishes its lessons, and up to 20 members.

Yes: lessons and the MCP server are free now, and so is everything UpFork makes. UpFork may limit or charge for the lessons and the MCP server later, and will announce it at least 30 days before. UpFork's own products are MIT-licensed and free, and a charge for lessons never changes that. The only paid things are some developers' products, paid in USDT straight to the developer.

Whoever wrote a lesson keeps it, and gives UpFork a lasting license to publish it and license it to others. You may use a lesson and its snippet freely in your own projects. Copying lessons in bulk, building a dataset or training an AI model on them needs UpFork's written permission; lessons are not under an open license. Each lesson is credited to its author's name or handle, or to their team.

No. A published lesson or article is never deleted on UpFork, not by its author and not by UpFork, which can only hide one. An author can take an article off the site (the editor's "Take it off the site", or hide_article in MCP) and put it back later; its lessons are kept, but stay off the site while the article is off. Only an article that was never published can be deleted. When an account is closed, its lessons and articles stay as "a former member".

All of UpFork's own products are free and MIT-licensed: use them, change them, ship them. A developer's product shows its own license on its page: the UpFork Standard License (any number of personal and commercial projects, but not resold or shared on its own) or an open license such as Apache 2.0, BSD 3-Clause or GPL v3. Some developers' products are paid, in USDT, and show their price and license before you buy.

With the shadcn CLI. A free one installs by its address, with no account or setup: npx shadcn@latest add https://upfork.dev/r/<name>.json. A paid one you bought installs as @upfork/<name>, with the personal token you create on your account page set as UPFORK_TOKEN, and each product page shows its own command. Your assistant can install components and landing pages for you through MCP; full-stack projects and plain-HTML landing pages are downloaded instead.

Yes. Every component and landing page runs live on its page, in light and dark, at phone, tablet and desktop width, and mobile components run in a phone. You need no account to try them or to read the code of free products. Paid code lists its files up front and unlocks when you buy.

It is checked, but no check catches everything, so read what you install. Before a developer's code goes on sale, and again on every change, UpFork installs it in a fresh project, scans it for the sites it talks to, hidden code and what it reads, checks its npm packages for install scripts and known malware, and approves that exact revision; the packages are then watched daily. Live previews run sandboxed on an origin of their own, so they can't reach the site or your account. Report a product that looks harmful from its page.

Buying takes a free account, and you pay in USDT on the TRON network (TRC-20) only: your order shows the price and the address, and you paste the transfer's transaction ID on the order. UpFork checks it on-chain, and the product unlocks once the full price is confirmed, usually a minute or two after you send it; paying less is fine, since what you sent counts and you send the rest the same way. Sales are final: UpFork can't refund an overpayment, and USDT sent on another network (ERC-20, BEP-20) or to another address is lost, because the money goes straight to the developer's own wallet, or UpFork's on the sales that are its share (the 5th, 10th, 15th… sale of each product), and UpFork never holds it.

Apply on the Sell page: prove your GitHub account or your website is yours (a code in a gist, or a small text file on your site), add a résumé if you like, and UpFork reviews your work, usually within a few days. Applying, publishing and the developer panel are free. UpFork's share is 20%, taken as whole sales: the 5th, 10th, 15th… sale of each product is paid to UpFork's wallet, and every other sale straight to yours, in full, starting with the first four. Up to 20 founding developers pay no share for their first 12 months (upfork.dev/sell/founders), and every developer gets a public page that prints as a PDF résumé anyone can check at upfork.dev/verify.

It's the short Markdown an AI assistant connected to UpFork reads first, instead of all of a product's files: what it is, the install line, the entry point, the key props, one example and the files to read next. You write it in the product's Details, or, unless you turn it off for that product, Claude drafts one from your code (when the product has none, when its summary no longer matches the code, or when you press Suggest again) and you accept, edit or discard it. A draft left undecided goes live after 7 days, marked as written by AI and not yet reviewed, if it still matches the code. UpFork reads every summary against the code, with no AI, and sets aside one that no longer matches, so an assistant is never pointed at a file that isn't there. Drafting sends the product's code to Anthropic, which may not train its models on it (upfork.dev/privacy).

Open a ticket on the support page, from your order or from the product's page: add screenshots, a PDF or a ZIP, and every answer reaches you on the site and by e-mail. Answers come from UpFork support and may be drafted with AI for UpFork's admins, never sent by themselves: a person at UpFork sends each one, and nothing from your account goes to the AI. If you can't sign in, the support page has a form for that, or write to support@upfork.dev. To report a bug in a product you have, use Reviews and bugs on its page: its title, version and state are public, the steps and screenshots stay between you, its developer and UpFork, and you're told when it's fixed. Members who have a product can also review it there.