Clickup vs PhoneScreen

A side-by-side look at the Clickup and PhoneScreen 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 declaredPhoneScreen logoPhoneScreenWorkplace & Productivity · Remote HTTP/SSERun hourly hiring from your AI assistant: score resumes, screen candidates by phone, review interviews, and check references.69GreatAuth: oauth 2.0

Verdict: choose Clickup for workplace & productivity work as a local process; choose PhoneScreen 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

PhoneScreen logoChoose PhoneScreen when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore PhoneScreen

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClickup logoClickupPhoneScreen logoPhoneScreen
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal49/100 · Fair69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars52—
Directory activity 2 views 0 installs 0 upvotes 3 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.

PhoneScreen 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"
      ]
    }
  }
}

PhoneScreen

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "phonescreen": {
      "url": "https://app.phonescreen.ai/mcp"
    }
  }
}

Frequently asked questions

Clickup is categorized under Workplace & Productivity and uses a local stdio subprocess. PhoneScreen belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Clickup for workplace & productivity work and PhoneScreen 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. PhoneScreen is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 phonescreen 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 52 GitHub stars. PhoneScreen has 69/100 (Great) with 3 views, 0 installs and 0 GitHub stars.