In-depth architectural comparison of the Shadcn Ui MCP Server and Docweave MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Shadcn Ui MCP Server
Developer Tools · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Docweave MCP
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Shadcn Ui MCP Server if you need specialized Developer Tools tools running via a local process. Choose Docweave MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Shadcn Ui MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS, GITHUB_PERSONAL_ACCESS_TOKEN, UI_LIBRARY.
MCP server that gives AI assistants seamless access to shadcn/ui v4 components, blocks, demos, and metadata.
Generate and read PDFs for AI agents: a generatepdf tool (HTML, a URL, or a template + JSON → PDF) and a readpdf tool (a PDF → text/markdown). Run locally with npx @docweave/mcp or use the hosted streamable-HTTP endpoint. Chromium-rendered, priced per document.
Category & Scope
Tools & Capabilities Breakdown
Shadcn Ui MCP Server Tools (10)
get_component
Get the source code for a specific shadcn/ui v4 component
get_component_demo
Get demo code illustrating how a shadcn/ui v4 component should be used
list_components
Get all available shadcn/ui v4 components
get_component_metadata
Get metadata for a specific shadcn/ui v4 component
get_directory_structure
Get the directory structure of the shadcn-ui v4 repository
get_block
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Shadcn Ui MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Docweave MCP belongs to Developer Tools using local stdio subprocess. Select Shadcn Ui MCP Server when you need capabilities focused on developer tools and Docweave MCP when you require tools for developer tools.