MCP workflows: typical sequences with several tools

Eight proven sequences in which the AI calls several tools in a row. You phrase the goal in plain language; the tool order shows what happens in the background.

Prerequisites
  • A connected MCP access with suitable permissions (see "Roles, permissions and modules").
  • The modules involved are enabled in the organization.

Start of day

An overview of open work, time and appointments.

  1. get_running_timer: is a timer still running?
  2. list_tasks with status in_progress: which tasks are in progress?
  3. list_calendar_events: which appointments are coming up?
  4. list_unscheduled_tasks: what is not yet assigned to a week?

Create a task and add it to a sprint

An idea becomes an assigned, scheduled task.

  1. list_projects and list_members: find the IDs of project and person.
  2. create_task with projectId, assigneeId, priority and dueDate.
  3. list_sprints with status active or planning: pick a suitable sprint.
  4. add_task_to_sprint with sprintId and taskId.

Plan a sprint with the AI suggestion

The suggestion is AI-generated – review it before you adopt it.

  1. create_sprint with name, dates, goal and capacityHours.
  2. suggest_sprint_plan with the sprintId: read the suggestion.
  3. add_task_to_sprint for each adopted task.
  4. update_sprint with status active to start.
  5. get_sprint: check planned/actual hours and capacity utilization.

Track time and bill it

From time tracking to an invoice draft. Line items from time entries need approved, billable entries in the same project.

  1. create_time_entry (without endTime a timer starts) and stop_timer.
  2. list_time_entries with projectId: collect the IDs of the approved entries.
  3. create_invoice with items that contain timeEntryId, plus service date and issuer details.
  4. update_invoice with status sent: finalizes the invoice and assigns the number.
  5. For a mistake in an issued invoice: create_invoice_correction.

Lead-Engine weekly routine

Follow up on overdue items without sending anything yourself.

  1. get_crm_dashboard and get_crm_weekly_briefing: read numbers and AI briefing.
  2. list_crm_leads with category ueberfaellig: who is waiting for us?
  3. get_crm_lead: check the lead's history and context.
  4. create_crm_email_draft: save a draft with reasoning and send condition.
  5. A human reviews and sends the draft in the CRM; you log mails that were already sent with create_crm_activity (email_outbound).

Budget check

Early warning for tight budgets.

  1. list_budget_overview: traffic-light status of all projects.
  2. get_project_budget for a project that stands out.
  3. get_budget_forecast: when will the budget run out?
  4. list_retainers: retainer consumption in the current period.

Use and capture knowledge

From a meeting to tasks and documentation.

  1. search_kb and get_kb_item: read existing knowledge.
  2. create_meeting with notes, summary and actionItems.
  3. create_task for each action item.
  4. create_kb_item: document the outcome, optionally with folder.

Find a team slot

The next common appointment without back-and-forth.

  1. find_team_free_slots with durationMin, days and optionally teammateUserIds (from list_members).
  2. create_calendar_event with one of the slots, optionally addMeet.

Common pitfalls

  • Keep the order

    Changes need IDs. Let the AI call list_* tools first before it uses create_* or update_*.

  • Review AI results

    Effort estimates, sprint suggestions, the weekly briefing and email drafts are AI-generated.

Keep reading

Still have a question or a problem?

Visit support

Last reviewed on 2026-09-26