Clickup vs Jira MCP

A side-by-side look at the Clickup and Jira MCP 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 declaredJira MCP logoJira MCPWorkplace & ProductivityFeature-rich MCP for controlling Jira through LLM clients. Safe for corporate environments.31EmergingAuth: not declared

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

Jira MCP logoChoose Jira MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You have the keys it needs: JIRA_API_TOKEN, JIRA_AUTH_TYPE.
Explore Jira MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecClickup logoClickupJira MCP logoJira MCP
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal49/100 · Fair31/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedJIRA_API_TOKENJIRA_AUTH_TYPE
Verified ownerCommunity listingCommunity listing
GitHub stars528
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.

Jira MCP 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"
      ]
    }
  }
}

Jira MCP

No confirmed install command for Jira MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Clickup is categorized under Workplace & Productivity and uses a local stdio subprocess. Jira MCP belongs to Workplace & Productivity and uses an install path we have not confirmed yet. Pick Clickup for workplace & productivity work and Jira MCP 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. Jira MCP has no confirmed install command yet — follow its own setup instructions.

Clickup has no declared pricing — check the project's own site. Jira MCP 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 clickup-2 and jira-mcp 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. Jira MCP has 31/100 (Emerging) with 0 views, 0 installs and 8 GitHub stars.