Skip to main content
DoneThatDoneThat

DoneThat MCP Server

Connect Claude, ChatGPT, and other MCP clients to your DoneThat work history with OAuth 2.1.

DoneThat is a time tracker that automatically turns captured work into tasks. A task is work already done, never a future to-do.

The DoneThat MCP server lets AI assistants read your tracked time and update your projects and tasks on your behalf. Connect with OAuth 2.1 using your existing DoneThat account. Leave any client ID and secret blank in the connector setup.

https://mcp.donethat.ai

The server uses Streamable HTTP transport at / and runs in stateless mode (no persistent MCP session required). Check availability at /health.

Connect in Claude

  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Paste the server URL: https://mcp.donethat.ai
  4. Complete the OAuth sign-in flow with your DoneThat account when prompted.
  5. Grant the scopes the connector requests.

Connect in ChatGPT

  1. Open Settings → Connectors (or the Apps/connectors area in your ChatGPT plan).
  2. Add a custom MCP server and paste https://mcp.donethat.ai.
  3. Sign in with your DoneThat account when OAuth opens.
  4. Approve the requested scopes.

ChatGPT may render report results in an embedded DoneThat widget.

Connect in Cursor or VS Code

Add an MCP server entry that points at the DoneThat URL. Exact UI labels vary by client; the server URL is always:

{
  "mcpServers": {
    "donethat": {
      "url": "https://mcp.donethat.ai"
    }
  }
}

Your client discovers OAuth endpoints automatically. Sign in with DoneThat when prompted.

Auto-connect for Claude organizations

On Claude Team and Enterprise, an organization can connect its members without each of them signing in. Members are matched to DoneThat by verified email, and each member's Claude reaches only that member's data.

  1. In Claude, open Organization settings → Connectors and choose Set up auto-connect, then Claude-issued. Add the connector with Use Claude's published identity, not a client ID.
  2. Copy the Issuer URL from Claude.
  3. In DoneThat, open Organization → Auto-connect, paste the Issuer URL and turn it on. Only organization admins can do this.
  4. Copy the Tenant ID from DoneThat into Claude's setup. Claude marks it optional, but without it auto-connect stops working if another organization enters the same Issuer URL.
  5. Click Run test in Claude.

Members need a verified email and an active seat in the organization. Auto-connect never creates accounts or takes seats. Turning it off ends access straight away.

Authentication

DoneThat MCP uses OAuth 2.1 (authorization code with PKCE). You authenticate with your DoneThat account; the MCP host stores tokens on your behalf.

AI apps sign in with OAuth, so don't paste API keys into their connector settings.

Your own scripts can skip OAuth and send a DoneThat API key as Authorization: Bearer <key>. A key reaches only what its own scopes allow.

Sign-in flow

When a connector starts OAuth, the MCP server sends you to the DoneThat web app at https://app.donethat.ai:

  1. Sign in with Google or email and password (the same login you use for DoneThat).
  2. Review the requested scopes on the consent screen.
  3. Click Authorize to grant access.
  4. The connector receives an access token and refresh token and can call MCP tools on your behalf.

No client secret is required. Connectors use a public OAuth client with PKCE.

Discovery and OAuth endpoints on the MCP host:

EndpointPurpose
GET /.well-known/oauth-protected-resourceProtected resource metadata (RFC 9728)
GET /.well-known/oauth-authorization-serverAuthorization server metadata (RFC 8414)
GET /.well-known/openid-configurationSame metadata for OIDC discovery clients
GET /oauth/scopesHuman-readable scope list
POST /oauth/registerDynamic client registration
GET /oauth/authorizeAuthorization (browser sign-in)
POST /oauth/tokenToken exchange and refresh
POST /oauth/revokeEnd access for a token (RFC 7009)

Access tokens last an hour. Refresh tokens allow renewal without signing in again until they expire or are revoked.

Tools

ToolDescriptionRequired scope(s)Access
generate_reportList tracked time for a date range as rows by activity, day, task, or week. Large reports come in pages.reports:readRead
query_statsAnswer how tracked time splits or changed, by category, project, weekday and more.reports:readRead
search_contentFind tasks and activity matching search text, over the last days or a dated window of up to 30 days.search:readRead
list_projectsList your projects and their exact IDs.projects:read or projects:writeRead
manage_projectCreate a project or update its name, description, or color. Merging projects is app-only.projects:writeWrite
reassign_task_to_projectMove an already-recorded task to a different project, or unassign it.projects:writeWrite
add_manual_taskRecord uncaptured work with a start and end time.tasks:writeWrite
submit_feedbackSend bug reports, product feedback, or feature requests to DoneThat support.feedback:writeWrite

Daily summaries aren't available over MCP. Read, generate, approve, and edit them in the DoneThat app.

Large reports

generate_report returns a page of rows at a time. A paged response has totalRowCount, offset, and, unless it's the last page, nextOffset; call again with offset set to it. Use limit to set the most rows per page (up to 500), and detail: "concise" to leave out description text and empty fields.

Scopes

When you authorize a connector, DoneThat shows these OAuth scopes. Grant only what the integration needs.

ScopeGrants
reports:readGenerate DoneThat reports for the authenticated account, including activity, day, task, and week views.
search:readSearch the authenticated user's task and activity history in read-only mode.
projects:readList the authenticated user's projects, including their IDs, names, descriptions, and colors.
tasks:writeCreate manual DoneThat tasks with a start and end time.
projects:writeCreate and rename projects, and change which project a recorded task is attributed to.
feedback:writeSend product feedback, bug reports, or feature requests to the DoneThat support team.

These scopes differ from HTTP API key scopes documented in the API reference.

Data and privacy

The MCP server acts on behalf of your DoneThat account. Depending on granted scopes, it may:

  • Read aggregated activity and report rows
  • Search task and activity history
  • List, create, and update projects, and move tasks between them
  • Create manual tasks
  • Submit feedback to DoneThat support

DoneThat does not sell your data. See Privacy, Terms, and Data handling for how we collect, use, and protect information.

Rate limits and troubleshooting

Requests are rate limited per account. If a tool call fails with a rate-limit error, wait and retry.

Authentication errors: Confirm you completed OAuth sign-in and approved the scopes the tool needs. Disconnect and reconnect the connector if tokens expired without refresh. MCP needs a plan that includes it, so it stops when a trial ends.

Invalid dates: Pass dates as ISO strings (for example 2026-03-23).

Group reports: teamIds works at day, task, or week level, not activity level.

Support

Questions about MCP setup, OAuth, or tool behavior: Contact support.

For programmatic HTTP access (API keys), see the API reference.

Connect DoneThat to your assistant

Point any MCP client at mcp.donethat.ai and sign in with the account you already have.

View pricing