In-depth architectural comparison of the Docker MCP and Uniswap Tx Builder 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
Docker MCP
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Uniswap Tx Builder MCP
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Docker MCP if you need specialized Developer Tools tools running via a local process. Choose Uniswap Tx Builder 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 Docker MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Docker MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Uniswap Tx Builder MCP belongs to Developer Tools using local stdio subprocess. Select Docker MCP when you need capabilities focused on developer tools and Uniswap Tx Builder MCP when you require tools for developer tools.
Build an ERC-20 `approve(spender, amount)` tx — e.g. the NFPM before `build_mint`/`build_increase`, or Permit2 before a Permit2-paid `build_swap`. `amount: "max"` for an unlimited allowance.
build_wrap
Wrap native ETH → WETH via the Universal Router (`WRAP_ETH`).
build_swap
Exact-in single-hop `tokenIn` → `tokenOut` swap via the Universal Router; with `wrapWei` (tokenIn = WETH9) it wraps native ETH first and sweeps the remainder, with `unwrapOut` (tokenOut = WETH9) it unwraps the output to native ETH — in the same tx either way. Pass `sender` and the default Permit2 p…
get_swap_quote
Read-only.** Quote an exact-in single-hop swap via Uniswap v3 QuoterV2 — the live `amountOut` a `build_swap` with the same params would get, plus `amountOutMin` (after `slippageBps`) ready to feed straight into `build_swap`.
plan_position
Read-only.** Turn a human price range + human amounts into aligned ticks + wei amounts for `build_mint`. Reads token decimals over RPC.
get_pool_state
Read-only.** Live pool state (tick, sqrtPriceX96, human price, spacing); optional ±pct range suggestion (rounded inward) and live-ratio `amount0Desired`/`amount1Desired` from wallet balances.
get_positions
Read-only.** List every position NFT a wallet holds (token0/1, fee, tick range, liquidity, tokens owed) via the NFPM's ERC-721 enumeration.