Skip to main content
Glama
fridzema

clockwork-mcp

by fridzema
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to clockwork-mcp

No user-submitted related servers found.

    Related Servers

    • Claude Memory

      AmmarJawad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides Claude Code with persistent memory across sessions, including session checkpoints, image persistence, and bidirectional sync with claude.ai projects.
      1
      MIT

    • mcp-sequel

      eukos
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Claude that connects to MySQL, MariaDB, and SQLite databases. Query your databases using natural language.
      3
      MIT

    • Database Tools for Claude AI

      elber-code
      A
      license
      B
      quality
      D
      maintenance
      MCP server that allows Claude AI to interact directly with MySQL databases, enabling query execution and table information retrieval through natural language.
      1
      2 npm
      4
      MIT

    • claude-engineering-coach

      nnhhoang
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server plugin for Claude Code that analyzes local AI session logs to provide coaching on coding patterns, tool usage, and productivity insights via tools and slash commands.
      1
      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

    B3.2/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools target distinct debugging aspects (e.g., queries, cache, logs, events), but slight overlap exists between analyze_slow_queries, get_queries, and get_query_stats, as well as between get_request and get_latest_request. Descriptions mitigate confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_*, analyze_*, list_*), making them predictable and easy to navigate.

    Tool Count3/5

    38 tools is high but acceptable for a comprehensive debugging server. However, two stub tools (get_xdebug_hotspots, get_xdebug_profile) are unnecessary and inflate the count.

    Completeness4/5

    The toolset covers most debugging needs (requests, queries, logs, cache, events, performance, etc.). Minor gaps include the missing Xdebug functionality indicated by stubs.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources