Skip to main content
Glama
rize-io

rize-mcp-server

Official
by rize-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to rize-mcp-server

No user-submitted related servers found.

    Related Servers

    • ATimeLogger MCP Server

      Mrquj
      A
      license
      A
      quality
      B
      maintenance
      A standalone MCP server that exposes the ATimeLogger REST API to Claude Desktop/Code over stdio, enabling activity tracking (start/stop/pause/log), reports/history, and activity type management.
      8
      52 npm
      1
      MIT

    • cairnos

      akramlam
      A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server for CairnOS, a local-first productivity app. Exposes 13 tools that let Claude read and write the same local SQLite "brain" the app uses — create and update tasks, projects, reminders, ideas, and notes; classify natural-language brain dumps; and query overdue/today tasks and project context.
      36 npm
      MIT

    • clio-mcp

      ToddHebebrand
      F
      license
      B
      quality
      C
      maintenance
      A standalone MCP server that enables Claude Desktop to manage Clio legal practice matters, documents, billing, and more via ~46 tools, with secure OAuth and audit logging.
      46
      -

    • routine-mcp

      rskmanz
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      11 npm
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 28 tools

    Disambiguation5/5

    Each tool targets a specific entity and action (e.g., client, project, task, session), with clear scope. No two tools have overlapping purposes; even the many 'get' tools are differentiated by the resource they retrieve.

    Naming Consistency5/5

    All tools follow a consistent `verb_entity` pattern in snake_case (e.g., `create_client`, `get_clients`, `stop_session_timer`). No mixing of conventions.

    Tool Count4/5

    28 tools is on the high side, but each covers a distinct operation across multiple entities (clients, projects, tasks, sessions, time entries, categories). The count feels appropriate for a comprehensive time-tracking server.

    Completeness4/5

    CRUD operations exist for clients, projects, and tasks. Session management includes start, stop, extend, and current session tracking. Queries cover time entries by entity, categories, apps/websites, and summary. Minor gaps: no delete or update for sessions, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources