Skip to main content
Glama

Server Details

Projects, tickets, time and budgets for agencies: book time, work on tickets, draft invoices.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
docket.rocks

TDQS

A3.5/5.0

Scored across 36 tools

Disambiguation4/5

Most tools target a distinct resource+action (stopwatch control, ticket lifecycle, time entries, reporting), and the descriptions explicitly cross-reference siblings (e.g. reschedule_ticket vs update_ticket vs close_ticket) which defuses many would-be collisions. The main fuzzy pair is financial_summary vs revenue_forecast — both are year-scoped, admin-only, and report invoices/quotations/revenue — plus the cluster of time-reporting tools (list_time_entries, my_activity, my_week) that an agent could confuse at a glance.

Naming Consistency4/5

Nearly everything is snake_case verb_noun (create_ticket, log_time, update_stopwatch, search_customers), and the my_* family is used coherently as a personal-view prefix. A handful of noun-only names break the pattern — financial_summary, revenue_forecast, project_budgets, team_capacity — but they remain readable and predictable.

Tool Count2/5

36 tools is well past the point where an agent can hold the surface in mind, and several capabilities are split into fine-grained variants (six stopwatch tools, three reporting tools on hours). The domain is broad enough that most tools earn their place, but the set would be easier to use consolidated (e.g. one stopwatch tool with an action, or merged reporting tools).

Completeness3/5

Ticket lifecycle and time tracking are essentially complete (create/get/update/close/reopen/comment/reschedule, plus full time-entry and stopwatch CRUD). Gaps appear elsewhere: projects can be read and budgeted but never created or edited, and the entire accounting surface (list_invoices, list_quotations, financial_summary, revenue_forecast) is read-only with no way to create or record anything, which will dead-end agents asked to do invoicing work.

Publisher details

Operator
Evernow
Operator website
https://evernow.io
Vendor relationship
First-party
Privacy policy
Not provided
Trust center
Not available
Restrictions
Not available

Available Tools

36 tools
book_stopwatchBook a stopwatchA
Destructive
Inspect

Books one of the user's stopwatches as a time entry and removes the stopwatch. Duration defaults to the stopwatch's suggestion (rounded up to the next 15 minutes); the ticket to the one on the stopwatch.

Inputs: stopwatch_id (required), date, ticket_id, service_id, +2 more.

close_ticketClose a ticketA
Idempotent
Inspect

Closes a ticket (moves it to the board's done column), as the close button in docket does — followers are notified.

Inputs: ticket_id (required).

comment_on_ticketComment on a ticketAInspect

Adds a comment by the user to a ticket, as plain text (blank lines separate paragraphs). The ticket's followers are notified as for any comment.

Inputs: text (required), ticket_id (required).

create_ticketCreate a ticketAInspect

Creates a ticket in a project the user can open, assigned to the user unless asked otherwise. Optional: a description (plain text), start and end date, priority. It lands in the project's backlog, as a ticket made in docket does.

Inputs: title (required), project_id (required), end_date, priority, +3 more.

delete_time_entryDelete a time entryA
Destructive
Inspect

Deletes one of the user's own time entries. This can't be undone.

Inputs: time_entry_id (required).

discard_stopwatchDiscard a stopwatchA
Destructive
Inspect

Deletes one of the user's stopwatches without booking its time. This can't be undone.

Inputs: stopwatch_id (required).

financial_summaryFinancial summary (accounting dashboard)B
Read-onlyIdempotent
Inspect

The accounting dashboard's figures for a year: open, paid and overdue invoices, the pipeline (confirmed quotations not yet paid), order confirmations (and confirmed quotations whose order confirmation isn't sent yet), revenue per month (paid, plus the open invoices and the confirmed quotations not invoiced yet) and quotations by status. Net amounts. Admins only, as in docket.

Inputs: year.

get_contextWho am I in docketA
Read-onlyIdempotent
Inspect

Returns the connected user (name, role, default service), the workspace, its country and the currency its amounts are in, today's date and time zone, and what this connection may do.

Inputs: no named parameters.

get_docRead a help articleA
Read-onlyIdempotent
Inspect

One of docket's help articles in full, as Markdown, by its slug (from search_docs).

Inputs: slug (required), language.

get_projectProject detailsA
Read-onlyIdempotent
Inspect

Details of one project: customer, status, deadline, open/closed tickets, progress (% of tickets closed) and how much of its budget is used. The budget itself only when the user may see it in docket.

Inputs: project_id (required).

get_ticketTicket detailsB
Read-onlyIdempotent
Inspect

Details of one ticket: title, description text, status, priority, dates, assignees, its project — and the latest comments (newest first), to tell where it stands.

Inputs: ticket_id (required), comments.

list_invoicesList invoicesA
Read-onlyIdempotent
Inspect

Invoices by status — e.g. the overdue ones (published, unpaid and past their due date: the invoice date plus the customer's or the workspace's payment term, as in docket's billing cycle) — optionally for one customer, with net and gross amounts. PMs and admins only.

Inputs: limit, status, customer_id.

list_quotationsList quotationsA
Read-onlyIdempotent
Inspect

Quotations by status — e.g. the ones sent to a customer and not confirmed yet — with net and gross amounts and totals. PMs and admins only.

Inputs: limit, status, customer_id.

list_servicesList servicesA
Read-onlyIdempotent
Inspect

The services (kinds of work, e.g. Design, Development) time can be booked with. Booking without one uses the user's default service.

Inputs: no named parameters.

list_stopwatchesList stopwatchesA
Read-onlyIdempotent
Inspect

The user's stopwatches: title, whether it runs, the time on the clock and the minutes a booking would suggest (rounded up to the next 15).

Inputs: no named parameters.

list_time_entriesList time entriesA
Read-onlyIdempotent
Inspect

The user's time entries in a date range (default: the current week), with totals per day and per project. Admins may also ask for another user's or everyone's entries. Revenue only when the user may see it in docket.

Inputs: to, from, user_id, project_id.

log_timeBook timeAInspect

Books time for the user on a ticket. The project comes from the ticket; the service defaults to the user's own. Duration in minutes, in steps of 15.

Inputs: ticket_id (required), duration_minutes (required), date, service_id, +1 more.

my_activityMy activityA
Read-onlyIdempotent
Inspect

What the user did in docket's tickets, day by day (default: today): tickets they created, commented on (with an excerpt), changed (which fields), closed or reopened, and the minutes they booked on each. The ground for filling in forgotten time: tickets with activity but no booked time are flagged. Up to 31 days at once.

Inputs: to, from.

my_notificationsMy notificationsA
Read-onlyIdempotent
Inspect

What's new for the user — docket's inbox: comments, mentions, assignments, closed or reopened tickets and document status changes, one entry per thing and event (with how many there were), newest first. Unread only unless asked otherwise.

Inputs: limit, include_read.

my_ticketsMy ticketsA
Read-onlyIdempotent
Inspect

What's on the user's plate: open tickets assigned to them, grouped by when they're planned — the Workload page's buckets: OVERDUE (ended before today), THIS_WEEK (lies in this week), THIS_MONTH, NEXT_MONTH, LATER, UNPLANNED (no dates). Default: overdue and this week.

Inputs: limit, buckets.

my_weekMy weekA
Read-onlyIdempotent
Inspect

How much the user has booked in a week (default: this week) against their working hours, day by day: which past days have gaps, and what they may have forgotten to book — open tickets assigned to them that are due by the end of the week, and tickets they commented on that week, without time booked on them that week.

Inputs: week.

pause_stopwatchPause a stopwatchA
Idempotent
Inspect

Pauses one of the user's stopwatches; the time so far stays on it.

Inputs: stopwatch_id (required).

project_budgetsProject budgetsA
Read-onlyIdempotent
Inspect

Budget overview of projects — e.g. all of one customer — with how much of each budget is used and which are over budget. An amount budget counts the booked time's revenue and the external costs booked on the project; an hour budget the booked hours, and it is over budget too when its external costs top what the confirmed quotes sold. Basic users and up see the percentage and whether it is over; the budget itself (hours or money) only users who see it in docket; timetrackers see no budgets. Monthly budgets count the current month.

Inputs: customer_id, include_finished, only_over_budget.

reopen_ticketReopen a ticketA
Idempotent
Inspect

Reopens a closed ticket (back to the board's backlog), as the reopen button in docket does — followers are notified.

Inputs: ticket_id (required).

reschedule_ticketReschedule a ticketA
DestructiveIdempotent
Inspect

Changes a ticket's start date, end (due) date and/or priority — e.g. moves it to next week. Pass only what changes; an empty string clears a date.

Inputs: ticket_id (required), end_date, priority, start_date.

resume_stopwatchResume a stopwatchA
Idempotent
Inspect

Resumes a paused stopwatch of the user.

Inputs: stopwatch_id (required).

revenue_forecastRevenue forecastA
Read-onlyIdempotent
Inspect

The accounting forecast for a year, as on docket's Forecast page: per month the expected revenue and how much of it is paid, totals of confirmed quotations, invoiced amounts and external costs, and the quotations and invoices behind it — optionally for one customer. Net amounts. Admins only, as in docket.

Inputs: year, customer_id.

search_customersSearch customersA
Read-onlyIdempotent
Inspect

Finds customers by company name. Returns ids for project_budgets, list_invoices and list_quotations.

Inputs: limit, query.

search_docsSearch the docsA
Read-onlyIdempotent
Inspect

Searches docket's help articles (how docket works: time tracking, tickets, budgets, invoicing, Jira, AI connections, …) and returns the best matches with a snippet. Read one in full with get_doc.

Inputs: query (required), limit, language.

search_projectsSearch projectsA
Read-onlyIdempotent
Inspect

Finds projects the user can access, by name, number or customer. Without a query it lists active projects. Returns ids to use with the other tools.

Inputs: limit, query, status, include_archived.

search_ticketsSearch ticketsB
Read-onlyIdempotent
Inspect

Finds tickets in projects the user can access — e.g. the ticket to book time on, or the user's own open tickets. Returns ids to use with the other tools.

Inputs: limit, query, status, project_id, +1 more.

start_stopwatchStart a new stopwatchAInspect

Starts a new stopwatch for the user, running in parallel with any others. The ticket is optional — it can be picked when booking.

Inputs: title, ticket_id.

team_capacityTeam capacityA
Read-onlyIdempotent
Inspect

Who still has room in a week (default: this week), optionally only people with a given expertise (e.g. "Design", matched against their service and its category). Per person: target hours left this week from their working hours, open tickets assigned to them that are due by the end of the week, and — for users who see budgets — the remaining hour budgets of those tickets and the free hours that leaves. docket has no capacity planning, so this is an estimate from ticket budgets.

Inputs: week, expertise.

update_stopwatchChange a stopwatchB
DestructiveIdempotent
Inspect

Renames one of the user's stopwatches, sets its clock to a corrected number of minutes (it keeps running if it was), or attaches a ticket.

Inputs: stopwatch_id (required), title, minutes, ticket_id.

update_ticketUpdate a ticketA
DestructiveIdempotent
Inspect

Changes a ticket's title or description, or who works on it: assign adds people, unassign takes them off, by name ("me" for the user). Pass only what changes. Dates and priority: reschedule_ticket. Closing and reopening: close_ticket, reopen_ticket.

Inputs: ticket_id (required), title, assign, unassign, +1 more.

update_time_entryChange a time entryA
DestructiveIdempotent
Inspect

Changes one of the user's own time entries: date, duration, description, ticket (the project follows the ticket) or service. Only the fields given change.

Inputs: time_entry_id (required), date, ticket_id, service_id, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables advertising and marketing agencies to query and manage their agency data in natural language through the official public API, reading the complete financial module (bank accounts, payables and receivables, service invoices with withheld taxes) and extracting logged hours down to person, department and piece. It also creates and updates jobs, catalog pieces, tasks and production checklist items.
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      A living map of all your work: projects, tasks, decisions and what waits on whom, kept by you and your agents through the same tools, with every change logged.
      10
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to track time, manage the project board with epics, milestones, schedules and dependencies, and generate shareable reports through a single authenticated connection.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources