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, or multiple AI accounts? See Users & roles → Multiple clients, or multiple AI accounts — isolate by client, or consolidate several AI agent accounts into one Pulse account.
🔒 What Pulse stores, who can see it, the data-flow diagrams? See Privacy & data isolation.
You need a Pulse account and a credential. There are two options:
psk_…) — a long-lived bearer token. Best for CLI tools (Claude Code, Codex, Gemini).✅ Anyone can create their own API token — no Admin needed. Where you find the option depends on your role: Admins use Settings → Developers; everyone else uses the account menu (top right) → API tokens. OAuth clients are still workspace-wide and Admin-only (see Option B).
Any workspace member — Member or Admin — can create their own token. Where to find it depends on your role:
If you're an Admin:
claude-code-laptop).psk_… value — it's shown only once. Store it somewhere safe.If you're a Member (Settings → Developers isn't visible to you):