A
licenseNot graded
qualityD
maintenanceMCP server for UploadThing that lets AI assistants upload, list, and delete files on UploadThing's CDN via natural language. Runs as a Cloudflare Worker for always-on serverless access.
16 npm
MIT
Uploadkit
by drumst0ck
Related Servers
Alternatives to Uploadkit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceOfficial MCP server for Rendobar. Lets AI agents run serverless media processing and upload local files.983 npm1MIT
- AlicenseNot gradedqualityCmaintenanceOfficial MCP Server for GPT-5.6 Sol Coding & Reasoning API. Connects extended reasoning capabilities directly into Claude Desktop, Cursor, and Windsurf.MIT
BlazingCDN-MCPofficial
AlicenseAqualityBmaintenanceOfficial MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Cloud Storage and Video CDN2959 npm2MIT- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables users to query any Mintlify-powered documentation site directly from Claude. It leverages Mintlify's AI Assistant API to provide RAG-based answers and code examples for various platforms like Agno, Resend, and Upstash.30 npm18MIT
- FlicenseAqualityDmaintenanceThis MCP server enables interactive chat with AI models via the Anthropic API, supporting document retrieval and command-based prompts.2-
TDQS
A4.6/5.0
Scored across 12 tools
Disambiguation4/5
Most tools are clearly distinct: docs tools (list/search/get), component tools (list/get/search), and scaffolding tools each target a distinct resource+action. The main overlap is get_quickstart versus the scaffold_route_handler + scaffold_provider + get_install_command trio (and get_byos_config emitting handler code similar to scaffold_route_handler), but the descriptions explicitly guide when to prefer each.
Naming Consistency5/5
All twelve names use snake_case with a consistent verb_noun pattern (scaffold_*, get_*, list_*, search_*, transform_*). Verbs map predictably to action semantics: list = enumerate, search = fuzzy discovery, get = fetch one, scaffold = generate file content.
Tool Count5/5
Twelve tools sit comfortably in the ideal 3-15 range, and each covers a discrete capability (docs discovery/fetch, component discovery/fetch, install/scaffold helpers, BYOS config, image transform). Nothing feels redundant or missing.
Completeness4/5
Strong lifecycle coverage for a dev-enablement server: documentation (list/search/get), component catalog (list/search/get), setup scaffolding (install, route handler, provider, quickstart), BYOS config, and image transforms. A minor gap is there is no tool to scaffold a full component file or handle actual upload/delete operations on stored files, but these are largely workable via get_component usage snippets and the docs.
Maintenance
ActivityMaintained
ResponsivenessLimited data