Skip to main content

Rize MCP Server

For agents and integrations

Your Rize workspace, available to any AI assistant that speaks MCP

The Rize MCP server connects Claude, ChatGPT, Codex, Cursor, and other AI assistants to your Rize workspace. Read tracked time and live dashboards, start focus sessions, review AI suggestions, manage clients and projects, prepare invoices, and configure reports and routines. Every action uses your Rize account and permissions.

One URL to paste — OAuth and client registration are automatic
Read and write time entries, review AI suggestions, and manage your data model
Read live dashboard totals, manage invoices, and run reports and routines
Every action runs as you, with your permissions

Quickstart​

1

Add the connector

In Claude Desktop or claude.ai: Customize → Connectors → Add custom connector. Paste https://mcp.rize.io/mcp as the URL. Other clients take the same URL — see Setup per client below.

2

Authorize

Your client opens a browser to sign in to Rize with Google or an emailed sign-in code, then shows a consent screen naming the client and the redirect URL it will send you back to. Approve it.

3

Orient the assistant

Ask it to call get_current_user, then get_help. These return your timezone, workspace, role, and tool guidance. Ask for get_setup_checklist if you want to check which parts of your workspace still need setup.

4

Try a prompt

"How much time did I track today?" or "Show me my pending time entry suggestions and approve the ones tagged to Acme."

What you can do​

WorkflowTools to start with
Read time totals by client, project, task, or labelget_my_time_allocation; use list_my_time_entries for individual entries.
Start or stop a focus, meeting, or break timerget_current_session, start_session, stop_session.
Review, split, merge, or retag time entriesapprove_time_entries, split_time_entry, merge_time_entries, batch_update_time_entries.
Read or manage saved dashboardslist_dashboards, get_dashboard, create_dashboard, update_dashboard, delete_dashboard.
Prepare and manage client invoiceslist_uninvoiced_time_entries, create_invoice, send_invoice, record_invoice_payment.
Check contracts and profitabilitylist_contracts, get_contract_profitability, get_org_profitability.
Create, schedule, or run reports and routinescreate_report, update_report, run_report, list_routine_templates, create_routine, run_routine.
Reuse Skills and standing guidancelist_skills, get_skill, update_team_agent_context, update_workspace_agent_context.

Availability depends on your role and workspace plan. See the tool reference for each tool's inputs and permissions.

Connection​

SettingValue
Server URLhttps://mcp.rize.io/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.0 (authorization code + PKCE)
Authorization server metadatahttps://mcp.rize.io/.well-known/oauth-authorization-server
Protected resource metadatahttps://mcp.rize.io/.well-known/oauth-protected-resource
Dynamic client registrationSupported (RFC 7591)

Clients that support dynamic client registration — Claude Desktop, Claude Code, ChatGPT, Codex, Cursor, Zed, and anything on the official MCP SDKs — register themselves the first time you connect. There is no client ID or secret for you to create.

Signing up without an account​

People who don't have a Rize account yet can use https://mcp.rize.io/mcp/public. It needs no sign-in and exposes two tools: sign_up, which emails a 6-digit sign-in code, and get_login_url, which returns the sign-in, sign-up, and desktop app download links. Once the account exists, connect to https://mcp.rize.io/mcp for everything else.

ChatGPT can call sign_up and get_login_url on https://mcp.rize.io/mcp before linking an account. Every other tool there asks ChatGPT to link the account first.

Authentication​

The server uses the OAuth 2.0 authorization code flow with PKCE. On first connection:

  1. Your MCP client requests the server's authorization metadata and registers itself.
  2. The client opens your browser to sign in to Rize with Continue with Google or an emailed sign-in code — the same way you sign in normally.
  3. Rize shows a consent screen naming the client, the exact redirect URL it will return you to, and the scopes it is asking for. Denying sends the client an access_denied error and grants nothing.
  4. After you approve, the browser redirects back to the client with an authorization code, which it exchanges for an access token.

Access tokens expire after two hours and clients refresh them silently, so you should only need to re-authorize if you disconnect the connector or revoke it from Rize. PKCE is required for every client, public or confidential.

What the assistant can reach​

Tokens are issued with the read and write scopes. In practice, the boundary that matters is not the scope — it is your own role:

You areYou get
Any memberYour own time entries, activity, apps used, calendar events, keywords, tagging settings, Skills, reports, and routines.
Team adminEverything above, plus team-wide time entries and allocation, the team roster, member rates, invites, and labels.
ManagerYour direct reports in the roster and allocation views.
Org adminContracts, expenses, revenue entries, and profitability across the workspace; invoices on plans that include invoicing.
Finance permissionProfitability reads plus expense and revenue writes, without being an org admin.

An assistant calling a tool you do not have permission for gets an error, not someone else's data. The server never widens access — it forwards your bearer token to the same API the Rize apps call.

Your workspace only

The MCP server operates entirely within the workspaces you belong to. It cannot access data outside your permissions. Team and workspace views can include other members' data only when your role allows it.

Setup per client​

Connect to Claude · Connect to ChatGPT

The Claude link prefills the connector name and server URL. Review the values and confirm to add the connector. The ChatGPT link opens the Rize listing.

Claude Desktop and claude.ai​

Connect to Claude, review the prefilled name and URL, and confirm. Connect Rize, sign in, and approve access. In Claude Desktop, open Customize → Connectors to use the same remote connector.

To add the connector manually:

  1. Open Customize → Connectors.
  2. Click Add custom connector.
  3. Enter the name Rize and the URL https://mcp.rize.io/mcp.
  4. Click Add, then Connect next to Rize. A browser window opens.
  5. Sign in, approve the consent screen, and return to Claude. The Rize tools are available in any chat.

Claude Code​

Register the server:

claude mcp add --transport http rize https://mcp.rize.io/mcp

Or commit a .mcp.json to your project root so the whole team picks it up:

{
"mcpServers": {
"rize": {
"type": "http",
"url": "https://mcp.rize.io/mcp"
}
}
}

Start or restart a session, run /mcp, select rize, and choose Authenticate. A browser window opens; once it says Authorization successful you can close it. Run /mcp again to confirm the connection.

Codex​

Register the remote server and sign in:

codex mcp add rize --url https://mcp.rize.io/mcp
codex mcp login rize

Codex stores MCP settings in ~/.codex/config.toml, not .mcp.json. For a trusted project, you can instead add this to .codex/config.toml:

[mcp_servers.rize]
url = "https://mcp.rize.io/mcp"

Run /mcp inside Codex to check the connection. See the Codex MCP documentation.

Cursor​

Add Rize to .cursor/mcp.json in your project, or ~/.cursor/mcp.json to make it available across projects:

{
"mcpServers": {
"rize": {
"url": "https://mcp.rize.io/mcp"
}
}
}

Open Cursor's MCP settings, connect Rize, and complete the browser sign-in. Use Rize from Agent chat; no API key or client secret is needed. See the Cursor MCP documentation.

ChatGPT​

  1. Open the Rize listing in ChatGPT.
  2. Click Connect (or Try in chat, then Connect when prompted).
  3. Sign in to Rize with Continue with Google or an emailed sign-in code.
  4. Approve access and return to ChatGPT. Type @Rize to use the connector.

To connect the MCP server manually, subject to your account and workspace permissions:

  1. Open Plugins.
  2. Select + → Add custom MCP server.
  3. Enter a name and description, then set the connection URL to https://mcp.rize.io/mcp.
  4. Choose OAuth, review the risk warning, and select I understand and want to continue.
  5. Select Create as a plugin, review the discovered tools, and complete sign-in and consent.

The current Plugins flow does not require enabling Developer Mode first. See OpenAI's custom MCP setup instructions.

Raycast​

Raycast connects to remote MCP servers natively and signs in with OAuth, so no bridge is needed.

  1. Open Raycast and run Install MCP Server.
  2. Enter the name Rize, choose the HTTP transport, and paste the URL https://mcp.rize.io/mcp.
  3. Leave the OAuth type on Dynamic and click Sign In. A browser window opens; sign in and approve the consent screen.
  4. Back in Raycast, type @Rize in AI Chat or Quick AI to use the tools.

Raycast asks for approval before each tool call by default, so the first few prompts will confirm what Rize is about to read or change; you can relax that per server in its MCP settings.

Zed​

Open Settings → AI → MCP Servers → Add Server → Add Remote Server and enter https://mcp.rize.io/mcp. You can also add it to your Zed settings:

{
"context_servers": {
"rize": {
"url": "https://mcp.rize.io/mcp"
}
}
}

Zed prompts you to authenticate through OAuth. No stdio bridge is required. See the Zed MCP documentation.

Any other MCP client​

Any client that speaks Streamable HTTP with OAuth 2.0 can connect directly — point it at https://mcp.rize.io/mcp and the rest is negotiated. A typical config entry looks like:

{
"mcpServers": {
"rize": {
"url": "https://mcp.rize.io/mcp"
}
}
}

Key names differ per client (url, httpUrl, type, transport), so check your client's documentation for the exact shape. Clients that only support stdio can bridge with mcp-remote:

{
"mcpServers": {
"rize": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.rize.io/mcp"]
}
}
}

How to drive it well​

These are the things that separate an assistant that gets Rize right from one that guesses.

Start with get_current_user

It returns your timezone, default team, team memberships with roles, and your org id and role. Almost every other tool needs at least one of those, and the profitability tools all need org_id.

Let the server explain itself

get_help returns workflow guides by topic — time tracking, profitability, team management, clients and projects, keywords, skills. get_product_docs searches these docs, so an assistant can answer product questions with a real URL instead of inventing one.

Times are ISO 8601, in your timezone

Every response carries a _user_timezone field. Convert user-relative times ("2pm yesterday") into that zone before sending them — assuming UTC is the single most common source of entries landing on the wrong day.

Use evidence, not vibes, when tagging

list_my_keyword_matches returns deterministic keyword-rule hits over a time window, and list_my_time_entries with include_activity: true attaches top apps, window titles, and overlapping matches per entry. Both are far stronger signals than a title.

Read totals without rebuilding them​

Use get_my_time_allocation for your own totals or the team and workspace allocation tools when your permissions allow them. Use get_dashboard for the live numbers behind a saved Tracked Time, Timesheets, Personal Productivity, or widget dashboard. These tools return calculated totals; an assistant should quote them rather than add up a page of time entries.

list_my_time_entries returns compact summaries and calculated totals. When totals.partial is true, those totals cover only the current page. Use get_time_entry for one entry's full details or include_details: true for a detailed list. Add include_activity: true only when you need app, window-title, and keyword evidence.

Time entry statuses​

Time entries move through statuses, and filtering on the wrong one is the usual reason a query comes back empty:

StatusMeaning
trackingTime being tracked live right now.
segmentingTracked activity being cut into candidate entries.
generatingAn AI suggestion is being written for the entry.
pendingAn AI suggestion waiting for you to approve or reject.
failedGeneration failed; the entry is still reviewable.
activeA confirmed entry — what reports and invoices are built from.

Rejected entries are not returned by the public API or accepted as a status filter. When someone says "my suggestions", they mean pending, generating, and failed.

list_my_time_entries includes all listed statuses by default. get_my_time_allocation defaults to active, so pass the same status filter to both tools when comparing their results.

Conventions worth knowing​

  • IDs, not names. Time entry writes take client_id, project_id, and task_id. Resolve names first with list_clients, list_projects, and list_tasks, all of which accept a query.
  • Pagination. Most list tools take limit and cursor and return has_more and next_cursor. Dashboard lists instead take first and after and return page_info.has_next_page and page_info.end_cursor. Follow each tool's schema and page through all results before claiming a list is complete.
  • Idempotency. create_time_entry accepts an idempotency_key. Pass one on every create so a retried call cannot double-log an hour.
  • Money is in cents. Every monetary value in the contract and profitability tools is an integer number of cents.
  • Async AI. generate_time_entries and regenerate_time_entry return immediately and finish in the background. Poll list_my_time_entries with statuses: ["generating", "pending"].
  • Preview before saving. add_note with blocks defaults to save: false and returns what it would create, including overlaps with existing entries. Confirm, then call again with save: true.
  • Preview bulk changes. batch_update_time_entries defaults to dry_run: true. Show the count and sample, get confirmation, then call with dry_run: false.
  • Timers start now. start_session starts a live timer and ends any running session. For work that already happened, use add_note or create_time_entry.
  • Draft before sending. create_invoice creates a draft, not an email. Review it with get_invoice before using send_invoice.
  • Reuse instructions. list_skills and get_skill expose saved Skills, and the agent context tools manage standing guidance for people, teams, and workspaces.
  • Read finished AI output. list_report_runs, get_report_run, list_routine_runs, and get_routine_run return report analyses and routine briefs without re-running the same prompt.

Rate limits​

LimitApplies to
100 requests per minute, per userAll authenticated tool calls, across every tool.
10 requests per minute, per toolThe unauthenticated tools, sign_up and get_login_url.
15 per minute and 100 per dayAI generation — generate_time_entries and regenerate_time_entry share one quota.
3 regenerations per entryregenerate_time_entry, counted for the life of the entry.
20 registrations per minute, per IPDynamic client registration during first connect.

Exceeding the per-user limit returns a RATE_LIMITED error carrying retry_after_seconds, so a well-behaved assistant knows exactly how long to wait. The AI generation quotas are enforced by the API and surface as an ordinary error message rather than a RATE_LIMITED code.

Error handling​

Every tool error comes back as a JSON object with an error field. The codes an assistant will actually encounter:

CodeMeaningWhat to do
AUTHENTICATION_ERRORNo token, or the token is expired or revoked.Re-authorize the connector.
TOKEN_EXPIRED_ERROR / TOKEN_REVOKED_ERROR / INVALID_TOKEN_ERRORThe bearer token was rejected by the API.Re-authorize the connector.
RATE_LIMITEDPer-user rate limit hit. Includes retry_after_seconds.Wait that long, then retry.
SUBSCRIPTION_ERRORNo active subscription on the account.Surface the message. Do not retry.
INVALID_TIER_ERRORThe workspace plan does not include this capability.Surface the message. Do not retry.
GRAPHQL_ERRORValidation failure, missing record, or insufficient permission. Carries a messages array.Read messages — it names the problem. Correct the input rather than retrying blind.
HTTP_5xxTransient server error.Retry once, then surface it.
INTERNAL_ERRORUnexpected server-side failure.Surface the message.

GRAPHQL_ERROR is the catch-all: a bad ID, an out-of-range value, and "you must be a team admin" all arrive under it, distinguished by the messages array rather than by code.

Troubleshooting​

"Not authenticated" on every call — the token expired or was revoked. Reconnect the connector and sign in again.

The OAuth window opens but never redirects back — some browsers block redirects to 127.0.0.1. Complete the flow in Chrome or Edge, and make sure the callback tab is not blocked by an extension.

Queries return nothing for a day you know you worked — check the status filter first. active alone excludes every AI suggestion. Then check the timezone: a date interpreted in UTC instead of your zone shifts the whole window.

generate_time_entries produces no entries — Rize only generates from tracked activity. If the desktop app was not running for that range, there is nothing to cluster. Very short ranges often produce nothing too; try a full workday.

"Admin only" style errors — list_team_time_entries, get_team_time_allocation, invite_team_member, and the label tools need team admin. The contract and profitability tools need org admin or the finance permission. Use the _my_ variants, or ask an admin.

Stale tool list after an update — some clients cache the tool list. Fully quit and relaunch, then open a new chat.

Example prompts​

  • "How much time did I track today, grouped by client?"
  • "Show me my pending suggestions and approve the ones that are clearly the Acme redesign."
  • "What did I actually work on between 2pm and 5pm yesterday? Use my app activity, not just the entry titles."
  • "Create a keyword rule so anything with 'Figma' in the window title tags to the Acme project."
  • "Log 2 hours on the NVIDIA pitch deck this afternoon."
  • "What is the margin on the Acme retainer this quarter, and how much of the included hours have we burned?"
  • "Pull my last weekly report run and list every recommendation it made."
  • "Read my latest start-of-day routine brief and turn it into a short plan."
  • "Use my 'Client profitability review' Skill before summarizing this report run."
  • "Read my saved Timesheets dashboard for this week and show the totals by member."
  • "Start a 45-minute focus session for the Acme redesign."
  • "Prepare a draft invoice for Acme's uninvoiced time this month. Don't send it."

Support​