Feature request Add support for GET /api/v2/tickets/{id}/time_entries (time tracking)

[pmoisontech]

Description

The Freshservice REST API exposes time-tracking entries per ticket
through GET /api/v2/tickets/{id}/time_entries, but this endpoint is
not currently wrapped by the MCP server. As a result, none of the
time tracked by agents on tickets is reachable through the MCP.

Use case

• Reporting on time spent per ticket / per agent / per category.
• Workload and SLA analysis on long-running tickets.
• Building automated digests of activity on tickets handled by a given
  agent or group.

Today the only workaround is to open each ticket manually in the
Freshservice UI, which does not scale and is not usable from an
agentic workflow.

Proposed tool

A new tool, for example:

list_ticket_time_entries(ticket_id: int) -> list[TimeEntry]

returning at least the following fields per entry:

• id
• agent_id
• time_spent (formatted as HH:MM)
• executed_at
• billable
• note
• created_at
• updated_at

Optionally, a companion tool to create a time entry
(create_ticket_time_entry) would also be useful for agentic flows
that need to log work done by Claude on a ticket.

API reference

Freshservice API — Time Entries

Out of scope

This issue only covers the read endpoint. Create / update / delete on
time entries can be tracked separately if needed.