Siteprint examples vs Clickup

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

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
Clickup logoClickupWorkplace & Productivity · Local subprocess (stdio)Premium AI integration. Tasks, lists, docs, folders, time. 50+ tools. Instant setup.49FairAuth: not declared

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

Which MCP server should you choose?

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

Clickup logoChoose Clickup when

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

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
S
Siteprint examples
Clickup logoClickup
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal39/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—53
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Siteprint examples tools

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

Clickup 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.

Siteprint examples

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

Clickup

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

Frequently asked questions

Siteprint examples is categorized under Workplace & Productivity and uses a remote HTTP/SSE transport. Clickup belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Siteprint examples for workplace & productivity work and Clickup 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.

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

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