DoubleTick CLI is the command-line interface and MCP server for the DoubleTick email read tracking service. It allows users to send tracked emails from the terminal and check whether emails have been opened. This tool works with the DoubleTick backend, and tracking records created via the CLI are displayed alongside tracking records created by the Chrome extension.
The main commands include:
- doubletick login: Authenticates with Gmail and DoubleTick via the browser, with credentials saved locally to ~/.doubletick/credentials.json.
- doubletick logout: Deletes the stored credentials.
- doubletick send: Sends a tracked email, injects a read tracking pixel, sends it via the Gmail API, and registers the tracking.
- doubletick status: Checks whether tracked emails have been opened.
- doubletick dashboard: Lists all tracked emails along with their open rates and statistics.
As an MCP server, DoubleTick allows AI agents (such as Claude Code, Claude Desktop, etc.) to natively send and track emails. Before use, doubletick login must be run first, because the MCP server uses the same stored credentials.
Workflow: The user composes an email (text or Markdown) → the CLI converts it to HTML, generates a tracking ID, and injects a 1x1 tracking pixel → the email is sent via the Gmail API → tracking is registered with the DoubleTick backend → when the recipient opens the email, the pixel is triggered and the open is recorded → the user checks the status via doubletick status. The entire DoubleTick backend (pixel service, open logging, deduplication, device detection) remains unchanged; the CLI is simply a new way to inject the pixel, replacing the role of the Chrome extension in terminal/agent workflows.
Use cases: Users who need to send and track emails in the terminal or from an AI agent, such as sales, marketing, or scenarios where confirmation of email delivery is needed.
Limitations: A Gmail account and a DoubleTick account are required (the free tier can track 5 emails per week).
