Pulse runs a remote MCP (Model Context Protocol) server, so AI coding tools like Claude Code, Codex, and Gemini CLI can read your timesheet and log time entries for you — no manual stopwatch. Once connected, you can ask your agent things like "how much time have I logged this week?" or have it log an entry automatically after finishing a task.

This guide walks through connecting from each tool. The setup is the same everywhere: point the tool at the Pulse MCP endpoint and give it a credential.

Endpoint https://pulse.transmit.work/api/mcp
Transport Streamable HTTP (remote)
Auth Authorization: Bearer <token> — either a Pulse API token (psk_…) or OAuth 2.1

👥 Working with multiple clients? See Users & roles → multi-client pattern for the folder-scoped setup.

🔒 What Pulse stores, who can see it, the data-flow diagrams? See Privacy & data isolation.

Before you start

You need a Pulse account and a credential. There are two options:

⚠️ Token creation is Admin-only. The in-app Settings → API & Connections screen (where tokens and OAuth clients are created) is visible to workspace Admins only. If you're a Member, ask an Admin to create a token for you, or connect via OAuth through a client an Admin has registered.

Get your credentials

Option A — API token (recommended for CLI tools)

If you're an Admin:

  1. Log in to Pulse.
  2. Open Settings → API & Connections.
  3. Under API tokens, enter a label (e.g. claude-code-laptop) and create the token.
  4. Copy the psk_… value — it's shown only once. Store it somewhere safe.

If you're a Member: ask an Admin to create a token for you. The token is tied to your user — entries logged with it land on your timesheet, not the Admin's.

Option B — OAuth (for the Claude.ai connector)

  1. An Admin opens Settings → API & Connections → OAuth clients and registers a client: give it a name and a redirect URI, then copy the Client ID and Client Secret (shown once).