Skip to main content
Glama
Sign In
EARLY App MCP Server

EARLY App MCP Server

by janfincke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to EARLY App MCP Server

No user-submitted related servers found.

    Related Servers

    • TimePRO MCP Server

      calumjs
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that wraps the TimePRO API, enabling AI assistants to automatically create, view, and manage timesheets for authenticated users. It provides tools for searching clients and projects, retrieving configuration defaults, and performing full CRUD operations on timesheet entries.
      10
      MIT

    • Work-Timer

      JoelBondoux
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for time tracking and billing that allows freelancers to control timers, manage projects, and export invoices via natural language in any MCP-compatible AI assistant.
      7 npm
      MIT

    • Paymo MCP Server

      feamster
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for the Paymo platform that enables AI assistants to manage time entries, projects, and tasks through natural language. It supports tracking unbilled revenue and generating detailed invoice timesheets for efficient project management.
      -
    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 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially around timers, time entries, and activities. There is some potential overlap between create_time_entry and start_timer, but the descriptions clarify the difference between completed entries and a running timer.

    Naming Consistency4/5

    The tool names consistently use snake_case with a verb_noun pattern. Minor inconsistency appears in using edit_time_entry versus update_activity for similar edit/update operations.

    Tool Count5/5

    With 14 tools, the set is well-scoped for a time-tracking and activity-management server. Each tool appears to earn its place without excessive surface area.

    Completeness4/5

    The server covers core workflows: user context, timers, time-entry CRUD, activity lifecycle, and reporting. Minor gaps exist, such as fetching a single activity by ID, but agents can work around them via list_activities.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources