Check whether the local meegle CLI is already authenticated. Call this first when any business tool unexpectedly fails, or when you need to confirm the server can reuse the user's local login state.

Search Meegle projects by keyword, project key, simple name, or exact project name. In multi-project scenarios this is the primary entry tool: call it first when project context is missing, ambiguous, or expressed only as a human name, then pass the resolved project_key into later project-scoped tools.

List available work item types in a project. Use this before querying, creating, or filtering work items when the type key is unknown. Defaults to the configured test project.

List field configuration for a work item type in a project. Use this before workitem_create or workitem_update to discover valid field_key values, field types, and options.

Create a work item in Meegle. Use workitem_meta_fields first to discover valid field_key values. Complex array or object field values are automatically JSON-stringified to match meegle CLI expectations. This tool defaults to dry_run=true for safety.

Run an MQL query against a project. Use this for listing or searching work items across a project. The mql argument must be a complete SQL-like MQL string, not just filters or fragments. For select or status filters, use the project actual display labels or configured values instead of assuming generic English constants like OPEN or IN_PROGRESS.

Sample actual status values for a work item type and return both backend keys and display labels. Use this before filtering workitem_query by status so the model does not guess generic constants like OPEN or IN_PROGRESS.

Get a single work item by ID or name. Use this for detail reads after resolving a work_item_id from workitem_query or workitem_batch_get. Defaults to the configured test project.

Update work item fields or role operations. Use workitem_meta_fields or role metadata first when field keys or role keys are unknown. Arrays and objects in field_value are automatically stringified for meegle CLI compatibility. This tool defaults to dry_run=true for safety.

Get multiple work items by ID in one request fan-out. Use this when you already have a set of work_item_ids and need multiple detail reads with one tool call.

Add a comment to a work item. Use file_token only when an attachment was uploaded separately. This tool defaults to dry_run=true for safety.

List comments on a work item. Use optional start_time and end_time to narrow the time window.

List relation definitions in a project. Use this before relation_list when you need to discover relation IDs or relation field keys.

List work items linked by a relation field. Call relation_meta_definitions first when relation_id or relation_field_key is unknown.

List work items under a view by view ID. Use view_search first when you only know the view name.

Search views by title and resolve view IDs. Use this before view_get or chart_list when the user only knows a view name.

List charts under a view. Use this after resolving a view_id through view_search or direct user input.

Get chart details by chart ID. Use this after resolving chart_id from chart_list.

List teams in a project. Use this before team_list_members when only a team name is known.

List members of a team by team ID. Call team_list first when you need to resolve the team_id from a team name.

List schedule and workload details for up to 20 users within a 3-month span. Use user_resolve_keys first when you need to resolve names or emails into canonical user_key values.

Preprocess an attachment download and return the signed URL plan. Use this when you already have a file_url from workitem_get or comment_list and need the backend-generated download plan.

Preprocess an attachment upload and return the signed upload plan. Use this when a caller wants to manage the upload bytes outside meegle CLI but still needs backend-generated signed upload metadata.

List the current user's Meegle to-dos or completed items. Use this for personal work queues instead of project-wide query logic.

Get workflow node details for a work item. Use this before workflow_transition or subtask_update when node IDs or node-specific fields are unknown.

Create, update, confirm, or rollback a subtask. Use workflow_get_node first when node_id or existing subtask context is unknown. This tool defaults to dry_run=true for safety.

Transition or rollback a workflow node. Defaults to dry-run for safety.

Transition a state-flow status. Defaults to dry-run for safety.

List available state transitions for a work item.

Automatically detect node-driven vs status-driven workflow and execute the correct transition command. In auto mode it probes workflow_get_node first, then falls back to list-state-transitions when needed.

Resolve user identifiers (user_key, email, or display name) into Meegle user records. For normalized mapping output, use user_resolve_keys.

Resolve names/emails/aliases into canonical user_key values, so write tools can safely fill user fields and role assignments.

Inspect the latest meegle CLI command schema.

Run a raw meegle CLI command as an argv array. Uses spawn without a shell.