Track time with your agent

Connect your agent to Timetable, then ask it to record hours, start a timer, or summarize your week.

“Clock 2 hours on Website redesign for today.”

“Start a timer for Blue Drop Labs.”

“How much time have I logged this week?”

1. Create a personal token

Open Settings → Personal API tokens → New token. Give your agent its own token, such as “My desktop agent.” Create the token while you are in the team you want the agent to use. A token can only access that team, and revoking it immediately removes access.

Keep the token in your agent’s environment or secret settings. Do not paste it into a conversation. The connector uses your account’s existing API permissions; its initial tools act on your own time.

2. Add the MCP connector

This version runs locally with your agent and connects to the hosted Timetable API. It requires Node.js 22 or newer and an agent that supports local MCP servers over stdio. It does not provide a remote MCP URL for clients that only support hosted connectors.

Download the connector package and keep it in a permanent local folder. Add this to your agent’s MCP configuration, replacing the package path with the downloaded file’s absolute path and adapting the enclosing format to your agent. Replace the token placeholder through its local configuration or secret settings. The first start installs the connector’s npm dependencies.

{
  "mcpServers": {
    "timetable": {
      "command": "npx",
      "args": [
        "--yes",
        "--package=/absolute/path/to/blue-drop-labs-timetable-mcp-0.1.0.tgz",
        "timetable-mcp"
      ],
      "env": {
        "TIMETABLE_URL": "https://time.me-667.workers.dev",
        "TIMETABLE_TOKEN": "YOUR_PERSONAL_API_TOKEN"
      }
    }
  }
}

Restart or reconnect the agent after saving its configuration. Ask it “Which Timetable team am I connected to?” It should show your name, team, and timezone before you log anything.

You can also install the downloaded package locally with npm and use its timetable-mcp executable. This release uses a versioned package so updates are deliberate. Using the downloaded file also works when npm blocks installing packages directly from remote URLs; no global npm security settings need changing.

For a different deployment, set TIMETABLE_URL to its HTTPS origin. Local development over HTTP additionally requires TIMETABLE_ALLOW_HTTP=1. This exception is only for development.

3. Add the companion skill

Download the Timetable skill and install the included timetable directory in your agent’s supported skills directory. If your agent accepts a single skill file, use SKILL.md.

The MCP tools work without the skill. The skill teaches the agent how to resolve project names, use your timezone, avoid duplicate submissions, and give a useful confirmation.

What your agent can do

Tool	Action
`get_context`	Identify your account, team, timezone, date, and a new request UUID
`find_projects`	Find active projects by project or client name
`log_time`	Record a completed duration for yourself
`list_entries`	Read your time entries and running timers
`start_timer`	Start a timer, stopping your others by default
`stop_timer`	Stop one of your timers
`get_report`	Summarize your recorded time
`get_forecast`	Estimate your month-end hours

If several projects match, the agent should ask which you mean. Dates default to today in your timezone when you have not specified another day. 1.25 means one hour and 15 minutes. Entries keep exact time and may overlap.

Writes use a unique request UUID. Retrying the same request with the same UUID returns the saved entry, preventing duplicate hours. A connection error is not proof that a save failed. Keep the UUID and arguments unchanged when retrying.

The connector does not create teams, change permissions, or delete entries. Use Timetable’s web interface for those actions.