What is the key difference between CCXT and Pipeworx?

CCXT belongs to the Developer Tools category with local stdio execution, while Pipeworx belongs to the Developer Tools category with local stdio execution.

How do I install CCXT or Pipeworx in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are CCXT and Pipeworx free or paid?

CCXT operates under a Free / Open Source model (No auth required). Pipeworx operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

CCXT lists 0 tools with 0 views and 43,907 GitHub stars. Pipeworx lists 0 tools with 0 views and 0 GitHub stars.

Can I use both CCXT and Pipeworx together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

CCXT vs Pipeworx

In-depth architectural comparison of the CCXT and Pipeworx MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

CCXT

Developer Tools · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Pipeworx

Developer Tools · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose CCXT if you need specialized Developer Tools tools running via a local process. Choose Pipeworx if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose CCXT when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore CCXT Details

Choose Pipeworx when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Pipeworx Details

Feature & Specification Comparison

Specification	CCXT Developer Tools	P Pipeworx Developer Tools
Summary	Official CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets	Live data gateway for AI — 3,300+ tools across 750+ sources, with citations
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

CCXT Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Pipeworx Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

CCXT Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ccxt": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Pipeworx Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pipeworx": {
      "command": "npx",
      "args": [
        "-y",
        "pipeworx"
      ]
    }
  }
}

Frequently Asked Questions

CCXT is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Pipeworx belongs to Developer Tools using local stdio subprocess. Select CCXT when you need capabilities focused on developer tools and Pipeworx when you require tools for developer tools.

More alternatives to CCXT More alternatives to Pipeworx Developer Tools category hub