rescuetime8.7 KB
View saved version →
---
name: rescuetime
description: Analyze a user's RescueTime data, report their timesheets or their managed teams' timesheets, explicitly control their current focus session or timer, or categorize their activities through RescueTime MCP. Use for recent tracked activity, time allocation, projects, tasks or clients, timesheet totals and status reports, team timesheet reports for managers, categories, productivity, focus state, daily or weekly patterns, bounded comparisons, requests to start or stop focus, or requests to fix Uncategorized activities or change an activity's category.
---
# RescueTime
Use the RescueTime MCP tools to answer questions about the user's tracked time. Treat the records as private behavioral data and report what was observed without judging whether the user's choices were good or bad.
## Choose the operation
- Use `reference_documentation` for taxonomy, productivity, overview, and default category definitions. Its content is public RescueTime data, available on any connection without extra scopes.
- Use `recent_activity` for a compact timeline. Request a `day` chunk for one calendar day at five-minute resolution, or a `week` chunk for seven days at hourly resolution. A week can follow the user's natural calendar week or use an explicit seven-day start/end range. Prefer a day unless the question needs a broader pattern.
- Use `timesheet_report` for timesheet questions: status reports, billing, utilization, and how much time went to a client, project or task. It returns totals already filtered and grouped, per day, week, month or the whole range. Use `project_time_history` only when the question needs the individual blocks in time order (when work happened, its sequence, gaps or overlaps) or a regrouping the report does not offer. Both need `mode`: `personal` or `team`. Use `list_projects`, `list_tasks` and `list_clients`, with the same `mode`, for ids and names.
- Use `taxonomy_rollup` for totals or calendar comparisons by activity, category, overview, or productivity.
- Use `get_focus_state` to determine whether a focus zone, focus session, or timer is active.
- Use `start_focus_session`, `start_timer`, and `stop_focus` only when the user explicitly asks to change focus state.
- Use `uncategorized_activities`, `list_categories`, and `categorization_context` to propose categories, and `categorize_uncategorized_activities` or `recategorize_activities` only to apply changes the user has approved.
If a user-data tool requests authentication, let the host complete the RescueTime OAuth flow. Never ask the user to paste an OAuth token or API key into the conversation. A user who deliberately manages credentials locally may configure a RescueTime MCP API key in the host's secure credential facility.
## Interpret results
- Preserve the returned time zone and state the actual start and end bounds.
- Distinguish automatically tracked activity from manually or automatically assigned project time.
- Explain that personal category and productivity overrides take precedence over RescueTime defaults.
- Treat productivity scores as the user's configured classification, not an objective assessment.
- When a response may be limited, state the limit and avoid implying that the result is complete.
- Aggregate before presenting private detail unless the user explicitly asks for the detail.
- Personal timesheet results are the user's own records, on their personal projects and on the team projects assigned to them. Team results are other members' time; say whose time each figure is.
## Work efficiently
- Resolve relative dates using the user's returned RescueTime time zone.
- Do not request a full year when a day or week answers the question.
- Fetch recent activity as a day or week chunk. Use `today` or `yesterday` for common day requests. For weeks, use `this week`, `last week`, `N weeks ago`, `week of DATE`, or an explicit seven-day `start_date` and `end_date`. Keep taxonomy rollups within 45 inclusive days and p
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.