Tolmete Connectors · MCP

Log Time From The AI Agent You Already Work With

Connect Tolmete to Claude Desktop, Cursor, Codex, or any MCP-compatible client. Tell your agent what you worked on, and it can create, review, and correct your Tolmete time entries — without opening another timesheet.

Works With

Any MCP-Compatible Client

Tolmete Connectors preview — an AI agent logs checkout refactor and code review time that appears in My Activity

The Problem

Time Tracking Shouldn't Pull You Out of Your Work

Tolmete makes project management through chat feel natural for contributors and managers. You describe what you did or what you need; the AI workflow assistant for teams handles the structure, fields, and formatting in the background.

Developers and designers already spend their day inside editors, terminals, and AI agents. But logging time usually means leaving that environment, opening another tool, finding the right project, remembering what happened earlier, and filling in a form.

  • Context Switching Loses Detail

    A debugging session with a specific cause, investigation, and outcome can become nothing more than “bug fixing” by the time the timesheet gets filled in.

  • Timesheets Get Reconstructed Later

    Logging Monday's work on Friday means relying on memory. The result may look reasonable, but the detail behind the work is already gone.

  • Your AI Workflow and Your Time Tracker are Disconnected

    The AI agent is already part of the contributor's working environment. Traditional time tracking still lives somewhere else.

    Tolmete Connectors close that gap.

Product Demo

From One Sentence
To Real Tolmete Time Entries

If you're looking for "a better timesheet," Tolmete is probably not what you actually need. Time trackers focus on control. Tolmete focuses on understanding.

Review Your Entries

Ask What Is Already Logged

What have I logged this week?

Correct an Entry

Change it in the same conversation

Make the checkout refactor 4 hours instead of 5.

Log Multiple Activities

One message, several entries

Log yesterday: 4h on the API integration and 2h on design review.

Manage an Absence

Days off go through the same flow

Log Friday as a day off.

You keep talking to the AI agent already on your screen. Tolmete receives the data through the same projects and permissions used by your Tolmete account.

How It Works

Connect Your AI Agent to Tolmete
In Four Steps

The connector gives your AI agent a defined set of Tolmete actions while keeping those actions within your existing permissions.

01.

Generate Your Personal Token

Give the connection a label and choose its expiration period. The token secret is shown when it is generated.

Profile Settings → Connectors → Generate Token

02.

Add the MCP configuration

Tolmete gives you the configuration snippet needed by your AI client. Copy it into Claude Desktop, Cursor, Codex, or another MCP-compatible client.

Step-by-step integration guides are available for supported clients.

03.

Tell Your Agent What to Log

No separate timesheet form is required during the interaction.

Example: Log 3 hours on the payments refactor and 1 hour on code review today.

04.

See the Entries in Tolmete

The resulting entries appear as normal Tolmete time logs associated with your projects. They remain available in the Tolmete interface, reports, and connected workflows.

Connect Tolmete via MCP

{
  "mcpServers": {
    "tolmete": {
      "url": "https://…/api/mcp",
      "headers": {
        "Authorization": "Bearer tlm_mcp_…"
      }
    }
  }
}

Capabilities

What Can You Do With Tolmete Connectors?

The connector gives your AI agent a defined set of Tolmete actions while keeping those actions within your existing permissions.

  • Find Your Projects

    Your agent can look up projects available to you so entries can be assigned to the appropriate Tolmete project without manually copying project IDs.

  • Log Several Entries at Once

    A single message can contain multiple activities.

    Log yesterday: 4h on the API and 2h on design review.

  • Review What You Already Logged

    Ask what has already been recorded before adding new entries.

    What did I log yesterday?

  • Correct Existing Entries

    Change the duration, project, or description conversationally.

    Change the API entry from 4 hours to 3.5.

  • Remove an Incorrect Entry

    Your agent can remove your own entries when necessary.

    Destructive actions are marked accordingly so compatible AI clients can treat them as destructive operations.

  • Manage Absences

    Days off and absences can go through the same connector and into Tolmete's existing absence flow.

Bring Time Tracking Into Your AI Workflow

See how Tolmete Connectors let your team log, review, and correct time directly from the AI agents they already use — while keeping everything inside the same Tolmete projects, permissions, and reporting workflows.

Works With

Any MCP-Compatible Client

Core Value

Better Time Data Starts With Easier
Time Logging

When logging time takes one short interaction in a tool that is already open, contributors have fewer reasons to postpone it. That improves the quality of the data that reaches the rest of the business.

  • Same-Day Time Entries

    Log work while the details are still fresh instead of reconstructing the week from memory.

  • More Useful Descriptions

    Entries can retain meaningful information about what actually happened instead of collapsing into generic categories.

  • No Separate Logging Workflow

    Developers and designers continue working in the AI tools they already use. Time logging becomes another action inside that workflow.

How Intelligent Risk Alerting Works

Built for the People Who Log Time
— and the People Who Depend on It

A scope change on a time-and-materials project is routine. The same change on a fixed-price project near a deadline is a crisis. This is where AI project risk detection becomes useful: Tolmete evaluates sprint timing, billing models, and team capacity so managers only see alerts that actually require attention.

Developers & Designers

Log Your Day Without Leaving Your AI Agent

Time tracking should not be the administrative task that pulls you away from your editor or AI workflow.

Tell the agent already on your screen what should be logged, and the resulting entries appear in Tolmete.

Log yesterday: 4h on the API and 2h on design review.

  • No separate timesheet form during the interaction
  • Less context switching
  • Same-day logging while details are still fresh
  • Conversational corrections
  • Multiple activities in one request

Project Managers

Spend Less Time Chasing Timesheets

When contributors can log work with less friction, project data can arrive sooner and with more useful descriptions.

That gives PMs a more current view of project activity without relying entirely on end-of-week reminders.

  • Fewer missing time entries
  • More detailed descriptions for review
  • More current project data
  • Less manual follow-up with contributors

Agency Leaders

Improve the Inputs Behind Reporting and Billing

Utilisation, project profitability, reporting, and invoicing all depend on the quality of the underlying time data.

Making time logging easier for contributors improves the inputs those downstream processes depend on.

  • Fewer gaps between worked and logged hours
  • More current data for reporting
  • Better inputs for profitability analysis
  • Timelier information for billing workflows

Product ecosystem

Where Connectors Fit
in Tolmete

Tolmete Connectors are not a separate time tracking system. They provide another way to create and manage data inside Tolmete's existing workflows.

  • Time Tracking

    Entries created through an AI agent are ordinary Tolmete time logs. They use the same projects and appear alongside entries created through the Tolmete interface.

    Try the ROI Calculator
  • Invoicing Integrations

    Time logged through an AI agent can continue through the same invoicing workflows as other Tolmete time entries.

    Explore Invoicing Integrations
  • Absence Management

    Absences created through the connector enter Tolmete's existing absence management workflow.

    Explore Absence Management

Comparison

Manual Time Tracking vs. Logging Through Your AI Agent

Traditional client reporting depends on someone finding the time to build it. Tolmete replaces that cycle with a client reporting system that uses delivery evidence and automatically keeps clients informed.

Without Tolmete

Manual Time Tracking

  • Leave the environment where the work happened
  • Open a separate time tracking interface
  • Reconstruct work from memory
  • Find the correct entry again when something needs changing
  • Add another administrative step to the working day
  • Frequently complete entries later instead of while the context is fresh

With Tolmete

Tolmete Connectors

  • Log time from the AI agent already in your workflow
  • Create several entries from one message
  • Review existing entries conversationally
  • Correct an entry with another sentence
  • Keep using the same Tolmete projects and reports
  • Reduce the friction between finishing work and recording it

Traditional time tracking asks contributors to go to the tracker. Tolmete brings time logging into the AI workflow where work is already happening.

Security & Permissions

Your Agent Gets Your Tolmete Access
— Nothing More

Connecting an AI client does not create a separate permission model inside Tolmete. Actions performed through the connector run with the permissions of the person who created the token.

  • Personal Connections

    Each connector token belongs to the individual Tolmete account that created it.

  • Token Expiration

    Choose an expiration period when creating your connection.

  • Existing Permissions Apply

    What you cannot access in Tolmete, your agent cannot access through the connector either.

  • Revoke Access

    A connector token can be revoked from Tolmete when the connection is no longer needed.

  • Connection Visibility

    Tolmete provides information about connector usage so users can review their connections.

Stop Leaving Your Workflow
Just to Fill in a Timesheet

Connect Tolmete to the AI agent you already work with and turn time logging into a conversation instead of another administrative task.

Works With

Any MCP-Compatible Client

FAQ

Frequently Asked Questions

Everything you need to know about Tolmete.

Tolmete Connectors allow MCP-compatible AI clients to interact with your Tolmete account, so you can create, review, update, and remove time entries through an AI agent.
Model Context Protocol (MCP) is an open protocol that allows AI applications to connect to external tools and data sources.
Tolmete provides integration guidance for Claude Desktop, Cursor, and Codex. Other MCP-compatible clients can use this connection method where supported.
Yes. A single request can create multiple time entries, allowing you to record several activities in one conversation.
No. Tolmete Connectors do not monitor your activity, read your repository, or generate timesheets from commits or code. You tell your AI agent what should be recorded.
Only if your Tolmete account has permission to access them. The connector does not add permissions to your account.
Ask the agent to correct or remove the entry. The connector supports both actions for entries your account is allowed to manage.
No. Connectors provide another way to create and manage Tolmete data. Entries created through an AI agent still appear in the web app and remain available for reporting and billing.
No. Connections are personal, so contributors can adopt them individually without changing how the rest of the team records time.