Ext Ops Panel
Open dashboard
Comparison

clocknext vs io.github.dynatrace-oss/Dynatrace-mcp

clocknext is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

clocknext is a plugin bundle for AI coding tools published by ClockNext. No marketplace we read lists it any more. io.github.dynatrace-oss/Dynatrace-mcp is an MCP server published by dynatrace-oss. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclocknextio.github.dynatrace-oss/Dynatrace-mcp
Community marketplace clocknext/clocknext-mcp Removed on 2026-10-15
Version: 0.13.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.2
Downloads/month (npm): 77 071
Downloads/week (npm): 16 273
Forks (GitHub): 26
Stars (GitHub): 137
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:df93c6f1912a
Forks (GitHub): 26
Pulls (Docker Hub): 306 303
Stars (Docker Hub): 0
Stars (GitHub): 137
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

clocknext vs io.github.dynatrace-oss/Dynatrace-mcp
Factclocknextno longer listed · io.github.dynatrace-oss/Dynatrace-mcp
Marketplaces that list it (differs)02
Stars (GitHub) (differs)0137
Pulls (Docker Hub) (differs)No figure on Docker Hub306 303
Forks (GitHub) (differs)026
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@dynatrace-oss/dynatrace-mcp-server)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published18
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/clocknext/clocknext-mcpgithub.com/dynatrace-oss/dynatrace-mcp
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of clocknext

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • time-tracking-billing-hours io.github.theluckystrike/time-tracking-billing-hours

    Billable-hours time tracking with rates and CSV export, running inside Claude or Cursor.

    by theluckystrike · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • TimeLodge

    Track time, manage clients and projects, review timesheets, and create invoices with OAuth.

    by dalehurley · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • mcp io.github.ClockNext/mcp

    Meter usage and manage usage-based billing from AI tools via the ClockNext API.

    by ClockNext · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • time-tracking io.github.theluckystrike/time-tracking

    Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.

    by theluckystrike · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • toggl

    Toggl Track integration for Claude Code. Log time entries by project and task, query what you tracked today or this week, and get aggregated summaries — all via natural language…

    by run-as-root · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • Timix.AI

    Time tracking, live project budgets, and billing exports for service firms.

    by timix.ai · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

clocknext

In its own words, on Community GitHub marketplaces:

Meter usage and manage usage-based billing from AI coding tools via the ClockNext API.

io.github.dynatrace-oss/Dynatrace-mcp

In its own words, on Official MCP Registry:

[DEPRECATED] Dynatrace MCP Server. Migrate to dynatrace-for-ai or Dynatrace Remote MCP Server.

How to run each

clocknext

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.dynatrace-oss/Dynatrace-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "DT_ENVIRONMENT=<YOUR_DT_ENVIRONMENT>" --transport stdio dynatrace-mcp -- npx -y @dynatrace-oss/dynatrace-mcp-server

Requires: DT_ENVIRONMENT

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of clocknext publish no list of tools, so we do not compare tools.

Settings each asks for

Only clocknext asks for

  • CLOCKNEXT_API_KEY (secret)
  • CLOCKNEXT_DOCS_URL

Only io.github.dynatrace-oss/Dynatrace-mcp asks for

  • DT_ENVIRONMENT
  • DT_GRAIL_QUERY_BUDGET_GB
  • DT_PLATFORM_TOKEN
  • OAUTH_CLIENT_ID (secret)
  • OAUTH_CLIENT_SECRET (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: clocknext · What it can do: io.github.dynatrace-oss/Dynatrace-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built