Clickup vs Siteprint examples

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

Clickup logoClickupWorkplace & Productivity · Local subprocess (stdio)Premium AI integration. Tasks, lists, docs, folders, time. 50+ tools. Instant setup.49FairAuth: not declared
S
Siteprint examplesWorkplace & Productivity · Remote HTTP/SSE
Website designs as DESIGN.md: real Siteprint exports of Linear, Stripe, Ramp and Cal.com.39FairAuth: no auth required

Verdict: choose Clickup for workplace & productivity work as a local process; choose Siteprint examples for workplace & productivity over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Clickup logoChoose Clickup when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
Explore Clickup

S
Choose Siteprint examples when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Siteprint examples

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClickup logoClickup
S
Siteprint examples
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal49/100 · Fair39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars53—
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Clickup tools

No tool names declared yet. Check the project README from the listing page.

Siteprint examples tools

No tool names declared yet. Check the project README from the listing page.

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.

Clickup

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "clickup-2": {
      "command": "npx",
      "args": [
        "-y",
        "@taazkareem/clickup-mcp-server@latest"
      ]
    }
  }
}

Siteprint examples

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "siteprint-examples": {
      "url": "https://siteprint.app/mcp/"
    }
  }
}

Frequently asked questions

Clickup is categorized under Workplace & Productivity and uses a local stdio subprocess. Siteprint examples belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Clickup for workplace & productivity work and Siteprint examples for workplace & productivity.

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.

Clickup has no declared pricing — check the project's own site. Siteprint examples is listed as free. Auth: no auth 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 clickup-2 and siteprint-examples as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Clickup has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 53 GitHub stars. Siteprint examples has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.