Ts Core vs Coolify

Two MCP servers from our cloud infrastructure ranking, compared on live data - updated nightly, never sponsored.

Bottom line · 2026-08-25

Ts Core records more monthly package installs (51,396 vs 25,205); both are actively maintained, with commits inside the last month.

How they differ in kind

Ts Core focuses on: Agent-native TypeScript framework for building MCP servers. Coolify focuses on: Manage Coolify from Claude, Cursor, or any MCP client: 44 consolidated tools for deploying, debugging, and operating your self-hosted PaaS in plain English. Environment-variable extraction: Ts Core yielded no variables extracted; Coolify yielded 2 variables.

What each one does

Ts Core

Agent-native TypeScript framework for building MCP servers. Build tools, not infrastructure. Declarative definitions with auth, multi-backend storage, OpenTelemetry, and first-class support for Bun/Node/Cloudflare Workers. It runs locally over stdio via the published package.

From the project's README.

Coolify

Manage Coolify from Claude, Cursor, or any MCP client: 44 consolidated tools for deploying, debugging, and operating your self-hosted PaaS in plain English. It runs locally over stdio via the published package.

From the project's README.

14 signals, side by side

Signal Ts Core Coolify
Monthly installs 51,396 25,205
GitHub stars 148 560
Last commit 2026-08-21 2026-08-22
Releases · last 90 days 10+ 10+
In the registry since Mar 2026 Feb 2026
Registry versions 130 15
Documented tools not extracted - see README not extracted - see README
Env vars extracted none extracted - see README 2
Runs local (stdio) local (stdio)
Endpoint auth local only local only
Maintenance actively maintained actively maintained
License Apache-2.0 MIT
Language TypeScript TypeScript
Category rank #4 of 141 #3 of 141

Environment variables found in the READMEs

These are extracted names, not a requiredness check. Project docs may mark them optional or require other setup.

Ts Core

No environment variables were extracted from the README setup. Check the project documentation for other authentication or configuration steps.

Coolify

  • COOLIFY_BASE_URL
  • COOLIFY_ACCESS_TOKEN

Which one, for what

Derived from the signals above, not hands-on testing.

Pick Ts Core if…

  • → measured package adoption matters - 51,396 monthly installs
  • → category standing - #4 of 141 maintained cloud infrastructure servers

Pick Coolify if…

  • → category standing - #3 of 141 maintained cloud infrastructure servers

Who's behind them

Ts Core - cyanheads: 125 MCP servers tracked, 124 maintained, 1,730 combined stars. Full record.

Coolify - stumason: 2 MCP servers tracked, 2 maintained, 582 combined stars. Full record.

Not sold on either?

The next-ranked cloud infrastructure servers we track:

Quick answers

Is Ts Core better than Coolify?

Package installs favor Ts Core: 51,396 monthly installs to 25,205. Coolify still ranks #3 of 141 maintained cloud infrastructure servers. Data as of 2026-08-25; we haven't hands-on tested either.

Can I use Ts Core and Coolify together?

Yes - MCP clients accept multiple servers in one config, so you can enable both cloud infrastructure servers side by side. If their tools overlap, keep the one whose toolset fits to keep your agent's tool list lean.

What environment variables do their READMEs document?

Ts Core: no environment variables extracted from the README setup; Coolify: 2 environment variables extracted from the README setup. Extraction does not rule out other authentication or configuration steps; check each project's current documentation.

Keep exploring: best cloud infrastructure servers · TypeScript servers · all comparisons · every server

Methodology: package-usage signal = npm/PyPI installs (last month, platform APIs) · maintenance = commit recency + release cadence (GitHub) · tool lists and environment-variable names extracted from each project's README · endpoint auth from our own nightly probes. We haven't hand-tested these servers; everything here is data as of 2026-08-25.