ChatPPT vs Clickup

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

ChatPPT logoChatPPTWorkplace & ProductivityModel Context Protocol (MCP) server for programmatic PowerPoint creation and editing45FairAuth: not declaredClickup logoClickupWorkplace & Productivity · Local subprocess (stdio)Premium AI integration. Tasks, lists, docs, folders, time. 50+ tools. Instant setup.49FairAuth: not declared

Verdict: choose ChatPPT for workplace & productivity work; 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?

ChatPPT logoChoose ChatPPT when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You want tools like deck_create, deck_import, deck_list.
Explore ChatPPT

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.

SpecChatPPT logoChatPPTClickup logoClickup
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal45/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars053
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools26Not listed

Tools & capabilities

ChatPPT tools 26

  • deck_createCreate a new blank presentation deck.
  • deck_importImport an existing PowerPoint file into the managed workspace and register its slides.
  • deck_listList all managed decks in the workspace.
  • deck_readRead metadata and slide/collection list for a deck.
  • deck_updateUpdate deck metadata (title) with optional optimistic revision check (`expectedRevision`).
  • deck_deletePermanently delete a deck and its `.pptx` file.
  • deck_validateRun diagnostic invariant checks across PPTX content and registry metadata.
  • slide_createAdd one or multiple slides in batch (supports `title` and `notes`).
  • slide_listList slides in presentation order with 0-based `position` indexes.
  • slide_readRead slide metadata and its element listing.
  • slide_renderRender a slide to a PNG image preview for visual feedback. Accepts an optional `width` in pixels, defaulting to `1280`, and returns an MCP `image` content item.
  • slide_updateUpdate slide title and speaker notes in batch.
  • +14 more on 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.

ChatPPT

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

Clickup

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

Frequently asked questions

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

ChatPPT has no declared pricing — check the project's own site. 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 chatppt and clickup-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, ChatPPT has a quality signal of 45/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.