
Uploadkit
io.github.drumst0ckPublished by GitHub account drumst0ckv0.3.1Updated Nov 3, 2026
UploadKit MCP — 40+ upload components, route scaffolds, BYOS setup, full docs search.
Overview
Local MCP server that gives AI coding assistants knowledge of the UploadKit React upload SDK: components, route scaffolds, BYOS setup and docs search.
- What you can do
- Browse, search and read UploadKit components with metadata and usage examples
- Get the right install command for your package manager
- Scaffold the Next.js route handler and the provider snippet for the root layout
- Get BYOS configuration for S3, R2, GCS or B2, plus an end-to-end Next.js quickstart
- Read catalog and quickstart resources
- When to use it
- Useful when building a Next.js or React app with UploadKit and you want the assistant to pick components, wire the provider and route handler, or set up bring-your-own-storage without pasting docs by hand.
- Requirements
- Runs locally over stdio via npx from the npm package @uploadkitdev/mcp; Node.js and network access to fetch the package are needed. No config, API key or environment variables are declared. A remote Streamable HTTP endpoint is also offered for clients that cannot spawn npx.
Installation
In SourceWeft
- Open Uploadkit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@uploadkitdev/mcp
[npm version] [Glama MCP score] [Awesome MCP Servers] [Official MCP Registry]
Model Context Protocol server for UploadKit — gives AI coding assistants (Claude Code, Cursor, Windsurf, Zed) first-class knowledge of the UploadKit SDK.
Your AI now knows:
- Every one of UploadKit's 40+ React components (name, category, inspiration, usage)
- How to scaffold the Next.js route handler
- How to wire
<UploadKitProvider>into the root layout - How to configure BYOS (Bring Your Own Storage) for S3, R2, GCS, or Backblaze B2
- Which install command to run for your package manager
No config. No API key. Runs local via npx.
Remote MCP
For clients that cannot spawn npx (ChatGPT custom connectors, Claude.ai web, Smithery), UploadKit also exposes a Streamable HTTP endpoint:
Same 11-tool surface, read-only, no auth. Full setup: https://docs.uploadkit.dev/docs/guides/mcp#remote-mcp
Install
Add this to your MCP client config.
Claude Code
…or run: claude mcp add uploadkit -- npx -y @uploadkitdev/mcp
Cursor
Settings → Features → Model Context Protocol → Add new MCP server:
Windsurf / Zed / Continue
Follow your editor's MCP docs. Command is always npx -y @uploadkitdev/mcp.
Tools
Resources
uploadkit://catalog— JSON of every componentuploadkit://quickstart— Next.js setup walkthrough
Example prompts once installed
"Add an Apple-style animated dropzone to this page."
"Set up UploadKit with Cloudflare R2 BYOS mode."
"What's the difference between
UploadProgressRadialandUploadProgressOrbit?"
"Create a route handler that accepts up to 4 images of 8MB each."
License
MIT
Source: packages/mcp/README.md at commit b8c3957
Tools
0Version history
1- v0.3.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts