Docker MCP Server vs Shadcn Ui MCP Server

A side-by-side look at the Docker MCP Server and Shadcn Ui MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Docker MCP Server logoDocker MCP ServerDeveloper Tools · Local subprocess (stdio)Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.59GoodAuth: not declaredShadcn Ui MCP Server logoShadcn Ui MCP ServerDeveloper Tools · Local subprocess (stdio)MCP server that gives AI assistants seamless access to shadcn/ui v4 components, blocks, demos, and metadata.72GreatAuth: api key required

Verdict: choose Docker MCP Server for developer tools work as a local process; choose Shadcn Ui MCP Server for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Docker MCP Server logoChoose Docker MCP Server when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like docker_container, docker_container_control, docker_compose.
Explore Docker MCP Server

Shadcn Ui MCP Server logoChoose Shadcn Ui MCP Server when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: MCP_TRANSPORT_MODE, MCP_PORT, MCP_HOST, MCP_CORS_ORIGINS, GITHUB_PERSONAL_ACCESS_TOKEN, UI_LIBRARY.
  • You want tools like get_component, get_component_demo, list_components.
Explore Shadcn Ui MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDocker MCP Server logoDocker MCP ServerShadcn Ui MCP Server logoShadcn Ui MCP Server
CategoryDeveloper ToolsDeveloper Tools
Quality signal59/100 · Good72/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedMCP_TRANSPORT_MODEMCP_PORTMCP_HOSTMCP_CORS_ORIGINSGITHUB_PERSONAL_ACCESS_TOKENUI_LIBRARY
Verified ownerCommunity listingCommunity listing
GitHub stars03,065
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools1010

Tools & capabilities

Docker MCP Server tools 10

  • docker_containerLists the containers of a project with their state, health and published ports, or measures with stats what one service consumes right now. A project name no container carries is refused with the names that exist, so an empty list means the host itself runs nothing under compose. Moving a container between states is docker_container_control.
  • docker_container_controlMoves one service between states — start, stop, restart — and reports where it stood before and where it stands now, with changed saying whether the call did anything at all. A stop that ran out of time comes back killed with its exit code, never as a clean stop. The whole stack at once is docker_compose_control.
  • docker_composeReads what the project declares: config for the resolved compose file, env for the variables with the file each came from. Both read files rather than a running process — a variable here is what was written down, not what the container now holds. What is actually running is docker_container.
  • docker_compose_controlBrings the stack up or takes it down, and reports the containers standing afterwards as read from the daemon, not as compose described them. A stack that half came up says so instead of passing for a success. Taking volumes down with it destroys their data and is refused without confirm.
  • docker_execRuns a command inside a service container and brings back its exit code, with stdout and stderr apart. exit_code null means the command never ran and reason says why; an empty stdout means it ran and said nothing. What destroys data is refused until the command carries # CONFIRMED-DESTRUCTIVE. Reading logs, asking a database and taking dumps have tools of their own.
  • docker_logsReads what a container printed, line by line: each line carries the stream that wrote it and its own time. An empty list means the window held nothing, not that the read failed, and lines dropped from the middle are counted rather than quietly lost. Narrow the window with since and until instead of raising the count.
  • docker_dbquery runs a statement against a database container, status asks the database about itself — version, size, uptime. PostgreSQL, MySQL/MariaDB, Redis, MongoDB and SQLite are spoken to through the client the image carries. A database that refuses answers with its exit code, not with a failed call. A statement that destroys data needs # CONFIRMED-DESTRUCTIVE.
  • docker_db_adminbackup takes a dump of a database container, restore fills the database from one. The answer names the file, its size and whether it was read back: a call that says done without naming a file of known size says nothing. Restore overwrites what is there and is refused without confirm — take a backup here first.
  • docker_healthservices says whether the containers answer their healthchecks, server whether this process is well, profiles which Docker hosts it was given. The word healthy means something different in each branch, so every answer explains its own verdict. A service that declares no healthcheck is said to have none, not counted as sick.
  • docker_resourceimages, volumes and networks list what a host holds; disk counts what they take, with unused bytes apart from the total. An empty list means asked and found nothing, which is not the same as never asked. What a running container consumes right now is docker_container with stats.

Shadcn Ui MCP Server tools 10

  • get_componentGet the source code for a specific shadcn/ui v4 component
  • get_component_demoGet demo code illustrating how a shadcn/ui v4 component should be used
  • list_componentsGet all available shadcn/ui v4 components
  • get_component_metadataGet metadata for a specific shadcn/ui v4 component
  • get_directory_structureGet the directory structure of the shadcn-ui v4 repository
  • get_blockGet source code for a specific shadcn/ui v4 block (e.g., calendar-01, dashboard-01)
  • list_blocksGet all available shadcn/ui v4 blocks with categorization
  • apply_themeApply a TweakCN theme preset to the project
  • list_themesList available tweakcn themes
  • get_themeGet details of a specific tweakcn theme

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Docker MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "docker-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@hypnosis/docker-mcp-server"
      ]
    }
  }
}

Shadcn Ui MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "jpisnice-shadcn-ui-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jpisnice/shadcn-ui-mcp-server"
      ],
      "env": {
        "MCP_TRANSPORT_MODE": "YOUR_MCP_TRANSPORT_MODE_HERE",
        "MCP_PORT": "YOUR_MCP_PORT_HERE",
        "MCP_HOST": "YOUR_MCP_HOST_HERE",
        "MCP_CORS_ORIGINS": "YOUR_MCP_CORS_ORIGINS_HERE",
        "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PERSONAL_ACCESS_TOKEN_HERE",
        "UI_LIBRARY": "YOUR_UI_LIBRARY_HERE"
      }
    }
  }
}

Frequently asked questions

Docker MCP Server is categorized under Developer Tools and uses a local stdio subprocess. Shadcn Ui MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Docker MCP Server for developer tools work and Shadcn Ui MCP Server for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Docker MCP Server has no declared pricing — check the project's own site. Shadcn Ui MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add docker-mcp-server and jpisnice-shadcn-ui-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Docker MCP Server has a quality signal of 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Shadcn Ui MCP Server has 72/100 (Great) with 3 views, 0 installs and 3,065 GitHub stars.