DocsInstall

Use UpFork from an AI assistant

Let Claude Code, Cursor, VS Code, Codex and other assistants search UpFork, show you a product and its code, install it into your project, and read your plan, through UpFork's MCP server.

Updated October 7, 2026This page as Markdown

UpFork has an MCP server at https://upfork.dev/mcp. AI assistants that speak MCP (Claude Code, Cursor, VS Code's Copilot, Codex, Windsurf and others) can use it to search UpFork for what you describe, show you a product and its code, put a component into your project, and read your plan and purchases, without you leaving your editor.

Looking never counts against your plan. Installing counts as a shadcn CLI install does, and paying always happens on the site, by you.

What your assistant can do

Tool	What it does
`search_products`	Searches the catalog for what you describe, in plain words and typos included, best match first, with each product's price, license and whether you may get it
`view_product`	One product: its description, price and license, and for components and landing pages its files and install command
`install_product`	A component or landing page to put into your project: its files and where they go, the packages and shadcn/ui components it needs, its styles, and the `npx shadcn add` command
`get_prompt`	A product's AI prompt, as its page's copy button gives it, for a project that isn't React with Tailwind CSS
`buy_link`	The page on UpFork where you buy a product or a plan
`my_account`	Your plan and until when, what's left of its limits today, and what you bought

Ask in your own words, for example: "Find a pricing table with a monthly and yearly switch on UpFork", "Show me the code of UpFork's OrbitGallery", or "Add UpFork's Crowdwall to this page".

What counts

What your assistant does	What it counts as
Searching, looking at a product or its code, reading your account	Nothing, ever
`install_product`	An install, as with the shadcn CLI: for UpFork's products that come with a plan, a download off your plan
`get_prompt`	An AI prompt on your plan, as copying it on the product's page does
`buy_link`	Nothing: it's a link, and you pay on the site

The same product counts once a day for each, however often your assistant asks. When a limit is reached, or a product isn't yours yet, your assistant is told so with what to do, and the pricing page has the plans.

Your token

Without a token, your assistant sees UpFork as a guest does: it can search and read product pages, see a product's files by name only, and find where to buy. With your access token, it sees the code of everything you may get (free products, what you bought, what's in your plan), and can install it, copy its AI prompt and read your account.

It's the same token the shadcn CLI uses. Create one on Account → Access tokens and keep it in an environment variable named UPFORK_TOKEN, never in a file you share:

# macOS and Linux: add this to your shell's profile (~/.zshrc, ~/.bashrc)
export UPFORK_TOKEN=upf_...

# Windows: once, then open a new terminal
setx UPFORK_TOKEN "upf_..."

Each setup below reads the token from there, so it never sits in a config file or a link.

Claude Code

claude mcp add --transport http upfork https://upfork.dev/mcp --scope user --header 'Authorization: Bearer ${UPFORK_TOKEN}'

The single quotes keep ${UPFORK_TOKEN} as written: Claude Code reads the token from your environment each time it connects. To share the setup with a project instead, put this in its .mcp.json:

{
  "mcpServers": {
    "upfork": {
      "type": "http",
      "url": "https://upfork.dev/mcp",
      "headers": { "Authorization": "Bearer ${UPFORK_TOKEN}" }
    }
  }
}

Cursor

Add UpFork to Cursor, or put this in ~/.cursor/mcp.json (or a project's .cursor/mcp.json):

{
  "mcpServers": {
    "upfork": {
      "url": "https://upfork.dev/mcp",
      "headers": { "Authorization": "Bearer ${env:UPFORK_TOKEN}" }
    }
  }
}

VS Code

Install UpFork in VS Code. VS Code asks for your token once, hides it as you type, and keeps it for UpFork. Or put this in a project's .vscode/mcp.json:

{
  "inputs": [
    { "type": "promptString", "id": "upfork-token", "description": "Your UpFork access token, upf_…", "password": true }
  ],
  "servers": {
    "upfork": {
      "type": "http",
      "url": "https://upfork.dev/mcp",
      "headers": { "Authorization": "Bearer ${input:upfork-token}" }
    }
  }
}

Codex

codex mcp add upfork --url https://upfork.dev/mcp --bearer-token-env-var UPFORK_TOKEN

Windsurf (Devin Desktop)

In mcp_config.json (~/.config/devin/ on macOS and Linux, %APPDATA%\devin\ on Windows):

{
  "mcpServers": {
    "upfork": {
      "serverUrl": "https://upfork.dev/mcp",
      "headers": { "Authorization": "Bearer ${env:UPFORK_TOKEN}" }
    }
  }
}

Other assistants

Any assistant that connects to MCP servers over HTTP can use https://upfork.dev/mcp. Without a token it works as a guest; with one, send it as Authorization: Bearer <your token>.

Good to know

Two ways to install. Your assistant can write the files install_product gives it straight into your project, or run the install command in a project set up for UpFork (Install components). Both count the same.
Paying stays with you. buy_link only gives the page: you open it, sign in, and pay in USDT yourself (Paying with USDT). No tool can pay or see a wallet.
Sellers' words are data. Product descriptions and code are written by their sellers. UpFork marks them as such for your assistant, and tells it never to follow instructions in them.
When the token doesn't work, each tool answers with what to do: a deleted or mistyped token needs a new one from Account → Access tokens.
Limits: 120 requests a minute with a token, 60 a minute from one address without one.