Rize

Create a task, or update an existing task with the same name, optionally under a project or with a due date/reminder. Tasks are the most granular unit of work and can be assigned to team members.

create_task

Create a time entry with optional client, project, and task assignment. If a matching active entry overlaps the requested range, Rize extends and updates that entry instead. Supports idempotency keys to prevent duplicate entries on retry. Times must be in ISO 8601 format — convert user-local times to their timezone (provided as _user_timezone in responses) before sending.

create_time_entry

Delete (archive) a keyword. The keyword will no longer be used for auto-tagging. Use list_keywords to find the keyword ID first.

delete_keyword

Delete a label by ID. Requires team admin role. The label is soft-deleted and will no longer appear in label lists.

delete_label

Delete a time entry by ID. Works on entries of any status (active, pending, failed, etc.).

delete_time_entry

DEPRECATED: Use add_note instead. This tool now delegates to add_note. Start or log a time entry from natural language. Tags to client, project, and task when available. Also saves a timeline note so Rize can use the context to improve future AI suggestions. When saved blocks overlap matching active entries, those entries may be extended and updated. IMPORTANT: Always provide the `blocks` parameter. Parse the user's text yourself before calling this tool.

dictate

Generate AI time entries for a time range. Analyzes the user's actual activity — apps, websites, meetings — and uses clustering to create multiple entries based on natural activity groups. By default, skips time slots where previous entries were rejected. Rate limited: 15 per minute.

generate_time_entries

Get AI effectiveness metrics for time entry creation and tagging. Shows acceptance rates, tagging coverage, label coverage, AI vs manual breakdown, confidence scores, and trends. Use to assess how well Rize's AI is performing for a team or user.

get_ai_effectiveness_stats

Returns the Rize login URL so the user can authenticate in their browser. No authentication required. Use this when the user needs to log in or connect their Rize account.

get_login_url

Get a single contract with all its periods and profitability details.

get_contract

Get profitability metrics for a specific contract in a date range. Returns revenue, costs, margin, hours, budget burn, and period dates. Use list_contracts to find contract IDs. All monetary values are in cents.

get_contract_profitability

Get the authenticated user's profile including name, email, timezone, default team, team memberships (team id, name, role, status), and organization info (id, name, logo, role, finance permission). Call this first to get your org_id and team_id for other tools.

get_current_user

Read a dashboard's live data with the viewer's permissions: saved Tracked Time totals and groups, Timesheets member/day stats, Personal Productivity metrics, or configured widget data. Use these numbers instead of reconstructing the dashboard with time-entry queries. Dates default to the saved range or this week. Data is returned as Markdown and JSON; respect truncation markers and use provided totals.

get_dashboard

Get documentation on how to use Rize MCP tools. Pass a topic to get specific help, or omit for an overview. Topics: time_tracking, profitability, team_management, clients_projects, keywords, skills, reports_routines.

get_help

Get another workspace member's agent settings: their personal guidance, tagging instructions, and activity summary instructions. Admins only (org admins, plus admins of an active team the member belongs to) — returns not-found otherwise. Find identity ids via list_workspace_members. For your OWN settings use get_tagging_settings.

get_member_agent_settings

Get the current user's own time allocation summary. By default returns the full view — breakdowns by client, project, task, AND label — plus totals and billable hours. Pass group_by to fetch a single breakdown, including title. For team-wide allocation (admin only), use get_team_time_allocation instead.

get_my_time_allocation

Get your recent time tracking signals — the individual AI actions and user feedback events that make up your time tracking history. Returns events like entry accepts/rejects, tag suggestions, label changes, and manual edits with full metadata (reasoning, confidence, tag_type, before/after values). Use alongside get_ai_effectiveness_stats to drill into the 'why' behind aggregate metrics.

get_my_time_tracking_signals

Get aggregated profitability metrics across all non-archived contracts for an organization in a date range. Returns revenue, costs, margin, and hours. For per-contract detail use get_contract_profitability. All monetary values are in cents.

get_org_profitability

Get documentation about the Rize product itself: what Rize can do, which integrations are supported, and where to find help articles. Use this to answer questions about Rize features, integrations, platforms, or setup — never guess. Pass a `query` to search the documentation and get the matching sections back as the docs' own prose, each with a deep link — prefer this over the static topics when the question is about a specific feature, and quote the returned steps rather than paraphrasing them. Colloquial wording works: the search widens common phrasings ("clip", "overlay", "that bar") to the product's own vocabulary. Use topic "support" whenever the docs don't cover the question, the user hit a bug, or they want to request a feature — it returns where to reach a human instead of guessing. Topics: overview, integrations, docs_index, support.

get_product_docs

Get monthly revenue, cost, and expense totals for a date range. Returns one data point per month across all non-archived contracts. Useful for spotting trends and comparing periods. All monetary values are in cents.

get_profitability_trend

Get a single report run by ID, including the parent report metadata and all AI analyses with summaries and insights.

get_report_run

Get a single routine run by ID, including the parent routine metadata and all briefs the run produced with their markdown bodies.

get_routine_run

Get one reusable prompt skill by ID. Use this when the user references a skill chip or a rize://skill/:id link.

get_skill

Get the current user's auto-tagging settings: generation mode, entry duration preferences, auto-approve threshold, which tag dimensions are automated, the custom instructions for tagging and activity summaries, and the agent guidance layered onto their runs (personal, plus their default team/workspace guidance). Read-only — use update_tagging_settings to change your own settings. Admins: manage other members via get/update_member_agent_settings, teams via update_team_agent_context, and the workspace via update_workspace_agent_context.

get_tagging_settings

Get time allocation summary across all team members (team admin only). Returns total hours, billable hours, and breakdown by grouping, including workspace member title. Use creator_emails or member_titles to filter to specific people. Filter by sources to split manual (user) vs AI time. Non-admins will only see their own allocation.

get_team_time_allocation

Find where a control actually lives in Rize: the desktop menu bar, the Desktop Widget menu, and the app's settings panes, each as a full click path like "Widget > Show on Desktop". Use this whenever the user asks where a setting is, how to turn something on or off, or how to reach a screen — the paths come from the shipping navigation, so quote them exactly and never invent a screen that is not listed. An entry marked with an access note is only there for users who have that grant, so say so rather than sending everyone to it. Pair it with get_product_docs, which explains what a setting does; this tool says where to click. Pass a `query` to search, or omit it for the full map.

get_ui_map

Get a single time entry by ID with all details including client, project, task, billing info, and AI confidence data.

get_time_entry

Get time allocation across every team and person in the workspace in one call (workspace admins only; pass workspace_id from get_current_user org.id). Supports member and title grouping plus per-day buckets — ideal for workspace reports and timesheet compliance (compact member×day summaries). Day buckets use the caller's timezone. Returns total hours, billable hours, and breakdown by grouping. Filter by sources to split manual (user) vs AI time. With group_by 'member' and no client/project/task/label filter, every accepted workspace member is returned — members with no entries matching the requested statuses (default: active) appear with total_duration_seconds 0 and no date, historical groups may also include deactivated or removed members. For accepted-member headcounts, paginate list_workspace_members to completion, filter status to accepted and apply the same team/title/creator filters, then match distinct identity_id values to group id. Preserve historical allocation totals.

get_workspace_time_allocation

Invite a new member to a team by email. New members get an invitation email; re-inviting an existing member returns the existing record without sending another email. Acceptance links are delivered only to the invitee by email, not returned to the inviter. Requires team admin or org admin permissions. Title is stored on the workspace member, so setting it requires org admin access.

invite_team_member

Invite up to 25 people to one team in a single call. New members get an invitation email; people already on the team get no new email. Acceptance links are delivered only to the invitee by email, not returned to the inviter. Each result has requested_email (the address passed in) and, on success, the member record. Same permissions as invite_team_member. One failed invite does not stop the rest; check each result's error.

invite_team_members

Invite a member to a workspace (organization) without adding them to a team. Sends an invitation email. Requires workspace admin; Rize employees may target any workspace via organization_id.

invite_workspace_member

List clients (customers/accounts) with their hourly rates and team associations. Use client IDs when creating or updating time entries.

list_clients

List contracts for an organization. Contracts track billing arrangements with clients including hourly rates, retainers, and profitability metrics. Archived contracts are excluded by default — pass status to filter. Use contract IDs with get_contract_profitability.

list_contracts

List the dashboards the current user can see in a workspace, pinned first, with cursor pagination. Pass a renderable dashboard's id to get_dashboard to read its live data, including saved Tracked Time views, Timesheets, Personal Productivity, and widget boards.

list_dashboards

List active keywords (auto-tagging rules) for the current user. Keywords map text patterns to clients, projects, or tasks — when a keyword appears in a window title, URL, or app name, the time entry is auto-tagged to the parent entity. Must specify tag_type to scope the query.

list_keywords

List labels available for tagging time entries. Labels with Auto-apply off remain assignable explicitly; use label IDs when updating time entries.

list_labels

List the authenticated user's own apps and websites used in a date range, sorted by time spent. Returns app name, URL, time spent, and category.

list_my_apps_used

List calendar events (meetings, appointments) for a single day from the user's connected calendars. Returns title, start/end times, attendees, location, and video conference link per event. For raw tracked activity (app switches, website visits) use list_my_events instead.

list_my_calendar_events

List deterministic keyword-rule matches over the user's tracked time in a date range. Each match is a time window where a keyword rule fired, naming the client/project/task/label it points at. Use these as ground truth when tagging or creating time entries — a keyword match covering an entry's time range is strong evidence for that tag.

list_my_keyword_matches

List the current user's own time entries for a date range. For team-wide entries (admin only), use list_team_time_entries instead. Returns all statuses by default (tracking, segmenting, active, pending, generating, failed); rejected entries are never returned, so you can see live tracked and unprocessed time as well as reviewable suggestions. Sorted by start time. Each entry is a compact summary: id, times, duration, title, description, status, source, billable, client/project/task/label ids and names, and pending tag suggestions; empty fields are omitted. For billing amounts, rates, AI reasoning, team, creator, or tag-suggestion reasoning, call get_time_entry for one entry or pass include_details: true. Returns 50 entries by default; when has_more is true, pass next_cursor as cursor to get the next page.

list_my_time_entries