This reference lists the 13 Worklog360 MCP tools available in the connected staging environment, what each does, who can use it, and example natural-language commands. Everyday users can ask their AI assistant for an outcome rather than typing the technical tool name.
Quick start: If you're an end user, choose an example prompt from a table below. If you're integrating the MCP server, refer to the technical identifiers in the tool mapping.
Worklog360 MCP guides: Overview · Time Tracking · Team Approvals · Automation Examples · Tool Reference
Tool naming: This page uses friendly labels such as log-time. In the connected staging environment, the actual tool identifiers include the _staging suffix. The exact names exposed in production or by a particular AI client may differ. Intended access descriptions are guidance, not a replacement for Worklog360 and Jira permission checks.
1. Time Logging, Worklogs & Timers — All Users
|
Tool |
What it does |
Who can use it |
Example prompt |
|---|---|---|---|
|
|
Creates a Jira worklog for the authenticated user on a specified issue and date. Supports duration, description and optional billable minutes. |
Authenticated user with Jira worklog permission |
“Log 5 hours on PROJ-16 yesterday, including 3 billable hours.” |
|
|
Edits an existing worklog, including logged minutes, billable minutes or description; verifies saved changes. |
Worklog owner or otherwise permitted editor |
“Change my PROJ-16 entry from yesterday to 6 hours.” |
|
|
Finds the authenticated user’s existing worklogs by Jira issue and optional work date; returns candidate IDs. |
Authenticated user |
“Find my worklogs on PROJ-16 from Tuesday.” |
|
|
Starts a timer on one Jira issue; if one is already running, returns it instead of starting another. |
Authenticated user |
“Start tracking time on PROJ-16.” |
|
|
Pauses the current timer; does not create a Jira worklog. |
Authenticated user |
“Stop my running timer.” |
|
|
Shows the active timer and most recently paused timer, when present. |
Authenticated user |
“What am I tracking time on?” |
|
|
Returns required/planned hours, timesheet approval status and assigned approvers for selected dates. Actual logged hours must be read from Jira. |
Authenticated user; other users only when authorized |
“Show my timesheet status and required hours for this week.” |
|
|
Submits the authenticated employee’s entire weekly or monthly timesheet and associated Jira worklogs for approval. |
Authenticated employee, subject to submission rules |
“Submit my timesheet for last week.” |
2. Team Management & Approvals
|
Tool |
What it does |
Who can use it |
Example prompt |
|---|---|---|---|
|
|
Lists accessible Worklog360 teams, IDs and assigned managers; managers can also see their team members. |
Team members and managers (accessible teams only) |
“Which Worklog360 teams do I belong to or manage?” |
|
|
Returns authorized team timesheet statuses, required/planned hours and optionally daily capacity or bookings. Not actual logged hours. |
Authorized managers or viewers of team timesheet context |
“Show my team's timesheet statuses for last week.” |
|
|
Approves or rejects one existing timesheet by its actual database ID; supports an optional comment. |
Assigned approvers or authorized team managers |
“Review and approve Alex's submitted timesheet for last week.” |
|
|
Submits, approves, rejects or recalls specifically identified Jira worklogs, including multiple selected entries. |
Authorized users or approvers, depending on action |
“Show me three selected worklogs and approve them after confirmation.” |
3. Administration & Diagnostics
|
Tool |
What it does |
Who can use it |
Example prompt |
|---|---|---|---|
|
|
Read-only diagnostic of the authenticated Forge installation and Jira tenant association. |
Administrative or support diagnostic access |
“Check whether Worklog360 is connected to this Jira site.” |
Technical Tool Names
For developers and administrators mapping AI prompts to the MCP server, the following are the tool names currently exposed by the connected staging integration.
|
Friendly label |
Current technical identifier |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Combine Tools for More Advanced Requests
Some user requests need several tools, often across both Worklog360 MCP and Atlassian MCP. These are example workflows, not additional single-purpose Worklog360 tools.
|
Workflow |
Example natural-language request |
Requirements |
|---|---|---|
|
Copy a previous week |
“Read my worklogs from last week, prepare matching entries for this week, check for duplicates, and ask before creating them.” |
Retrieve historical Jira worklogs using Atlassian MCP; create selected entries using Worklog360 MCP. |
|
Find missing logged hours |
“Compare my actual Jira hours this week with Worklog360 required hours and tell me which days are incomplete.” |
Worklog360 timesheet context plus actual Jira worklogs. |
|
Complete and submit |
“Review my timesheet, help me correct missing entries, then submit after I confirm.” |
Worklog context, Jira worklogs, optional new worklogs, and submit-timesheet. |
|
Prepare team approval review |
“Show my team's submitted timesheets for last week, flag gaps, and let me decide which to approve.” |
Authorized team context and approval tools; Jira worklogs for actual-hour checks. |
|
Weekly manager watchdog |
“Every Monday, summarize who has not submitted last week's timesheet and where required hours exceed logged hours.” |
Compatible external scheduling platform, authorized team context, and Jira worklogs for actuals. |
Permissions & Important Behavior
-
Time logging: Standard Worklog360 MCP creation creates a Jira worklog under the authenticated user's account, not under an arbitrary employee.
-
Timesheet context: Required hours and planned capacity are not recorded worklogs. For actual logged or billable hours, retrieve Jira worklogs with appropriate authorization.
-
Timers: Stopping a timer only pauses it. Creating the worklog is a separate step.
-
Timesheet vs. worklog approvals: Reviewing a timesheet changes the entire existing submission; worklog approval operations affect selected individual worklogs.
-
Approval permissions: Role access depends on the installation's actual authorization rules, assigned approvers, Jira permissions, and workflow status. A tool being listed does not grant access.
-
Bulk updates: The assistant must use verified worklog IDs, show the intended changes, confirm broad actions, and report partial failures.
-
Scheduled automation: MCP does not provide a scheduler. Recurring tasks depend on a compatible AI platform or automation service with tool access.
Capabilities Not Exposed as Dedicated Tools
The following are useful potential extensions, but are not separate tools in the currently connected Worklog360 MCP staging integration. Some related goals can already be addressed through combinations of existing tools and Atlassian MCP.
|
Potential tool |
Intended purpose |
|---|---|
|
|
Dedicated queue of submissions awaiting the approver's decision. |
|
|
Detailed logged hours and issue breakdown for a submission. |
|
|
Dedicated report on missing logged time versus required working days. |
|
|
Aggregated actual hours by employee, project or day. |
|
|
Team hours by individual Jira issue in a project. |
|
|
Create and validate a team member's absence request. |
Related Guides
This reference reflects the currently connected staging tool inventory as checked on November 16, 2026. Update it when your MCP server exposes additional tools or changes its permission model.