Befehle für den MCP Server

Archivieren

archive_customer: Archive (deactivate) a customer by setting it to inactive. Use this before permanently deleting a customer. IMPORTANT: Always confirm with the user before archiving.
archive_project: Archive (deactivate) a project by setting it to inactive. Use this before permanently deleting a project. IMPORTANT: Always confirm with the user before archiving.
archive_service: Archive (deactivate) a service by setting it to inactive (active=false). Use this before permanently deleting a service. IMPORTANT: Always confirm with the user before archiving.

Count

count_customer_projects: Count projects for customers

Create

create_absence: Create a new absence record. Date fields must be in YYYY-MM-DD format.
create_customer: Create a new customer
create_project: Create a new project
create_rate: Create a new hourly rate. Optionally assign to specific customers, projects, services or users.
create_service: Create a new service/activity
create_subproject: Create a new subproject
create_targethour: Create a new target hour
create_team: Create a new team
create_time_entry: Create a new time entry (completed work). Time fields must be in ISO 8601 format.

Delete

delete_absence: Delete an absence record permanently. IMPORTANT: Always confirm with the user before deleting.
delete_customer: Delete a customer permanently. IMPORTANT: Always confirm with the user before deleting. The customer must be set to inactive first via update_customer.
delete_project: Delete a project permanently. IMPORTANT: Always confirm with the user before deleting. The project must be set to inactive first via update_project.
delete_rate: Delete a rate permanently. IMPORTANT: Always confirm with the user before deleting.
delete_service: Delete a service permanently. IMPORTANT: Always confirm with the user before deleting. The service must be set to inactive (active=false) first via update_service.
delete_subproject: Delete a subproject permanently. IMPORTANT: Always confirm with the user before deleting.
delete_targethour: Delete a target hour permanently. IMPORTANT: Always confirm with the user before deleting.
delete_team: Delete a team permanently. IMPORTANT: Always confirm with the user before deleting.
delete_time_entry: Delete a time entry permanently. IMPORTANT: Always confirm with the user before deleting.

Get

get_absence: Get details of a specific absence
get_current_clock: Get the currently running clock (if any)
get_customer: Get details of a specific customer
get_entries_by_timeframe: Get time entries for flexible timeframes (today, yesterday, this week, last week, this month, last month, or custom date ranges). Date ranges are calculated in the user's own timezone, so "today" is the user's calendar day.
get_me: Get information about the current user
get_my_absences: Get absences (vacation, sick leave, etc.) for the current authenticated user. This is a convenience tool that automatically retrieves your user ID and filters absences accordingly.
get_project: Get details of a specific project
get_project_reports: Get project time reports and statistics
get_rate: Get details of a specific rate
get_service: Get details of a specific service
get_subproject: Get details of a specific subproject
get_targethour: Get target hour
get_team: Get details of a specific team
get_time_entry: Get details of a specific time entry
get_user: Get details of a specific user
get_user_report: Get a specific user report

Liste

list_absences: List absences (vacation, sick leave, etc.). IMPORTANT: Always use return_current_time first to get the current date when calculating relative date ranges.
list_customers: List all customers with optional filters
list_entry_groups: List grouped time entries (aggregated view)
list_projects: List all projects with optional filters
list_rates: List all hourly rates
list_services: List all services/activities
list_subprojects: List all subprojects
list_targethours: List all target hours
list_teams: List all teams
list_time_entries: List time entries with optional filters. IMPORTANT: Always use return_current_time first to get the current date when calculating relative date ranges (e.g., 'last week', 'this month').
list_user_reports: List user time reports
list_users: List all users in the organization

Markieren

mark_project_complete: Mark a project as completed
mark_subproject_complete: Mark a subproject as completed

Stoppuhr

return_current_time: Returns the current time. `timestamp` is the authoritative UTC instant (as the Clockodo API stores it); `timezone` is the user's IANA timezone; `local_time` is the user's current wall-clock time. When a user says "now", reason about `local_time`.
start_clock: Start the clock for time tracking (running timer). Time fields must be in ISO 8601 format.
stop_clock: Stop the currently running clock

Update

update_absence: Update an existing absence. Date fields must be in YYYY-MM-DD format.
update_clock: Update the currently running clock entry. Time fields must be in ISO 8601 format.
update_customer: Update an existing customer
update_default_rate: Update the default hourly rate that applies to all new projects and users
update_project: Update an existing project
update_rate: Update an existing rate
update_rates_sort: Update the sort order of child rates for a given parent rate. Pass id=0 for root level.
update_service: Update an existing service
update_subproject: Update an existing subproject
update_targethour: Update target hour
update_team: Update an existing team
update_time_entry: Update an existing time entry. Time fields must be in ISO 8601 format.