Skip to main content
Glama
ClockNext

ClockNext MCP Server

Official
by ClockNext
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ClockNext MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-token-saver

      Talap-creator
      A
      license
      A
      quality
      C
      maintenance
      Real-time Claude.ai subscription awareness for AI coding assistants. Surfaces live utilization, forecasts limits, gates expensive operations, and measures real per-task cost.
      5
      17 npm
      6
      MIT

    • Tallied

      connerj70
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables time tracking and invoicing through natural conversation with MCP clients like Claude or ChatGPT, allowing users to log work hours, query unbilled time, and draft invoices, with a minimal web app for settings, CSV import, and Stripe-powered billing.
      -
    • Subotiz MCP by Subotiz

      Subotiz MCPofficial

      Subotiz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage subscriptions, usage-based billing, payments, refunds, tax compliance, and invoicing to drive revenue growth.
      1
      MIT

    • Usage And Billing MCP Server

      BACH-AI-Tools
      A
      license
      C
      quality
      D
      maintenance
      Enables access to Usage and Billing APIs for managing accounts, products, meters, plans, and usage reporting. Supports operations like creating products/plans, reporting usage, and retrieving billing information.
      18
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 35 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: CRUD per entity plus usage verification/recording and docs helpers. The verify vs record usage pair is clearly separated as dry-run vs billed, and all list/get/create/update/archive tools are unambiguous for their entity.

    Naming Consistency5/5

    All tools follow a consistent clocknext_verb_noun pattern in snake_case (list_models, create_credit, archive_unit, etc.). Even compound names like bulk_import_customers and whoami fit the general style without mixing conventions.

    Tool Count2/5

    35 tools is well above the 25+ threshold for 'too many', even though the billing domain has many entity types. The number feels heavy and could be trimmed or split into focused sub-servers, especially given several entities have near-identical CRUD patterns.

    Completeness2/5

    Significant lifecycle gaps exist: customers have no update/archive/delete, purchases have only create (no list/get/update/cancel), and there are no tools for invoices or wallet transactions. The core setup and usage recording flows work, but managing subscriptions and customers over time is incomplete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources