DoubleTick CLI
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Open-source CLI and MCP server for email read tracking via Gmail. Know when your emails are opened — from the terminal.
Works with the DoubleTick backend. Tracks from the CLI show up alongside tracks from the Chrome extension.
Install
Quick Start
Commands
doubletick login
Authenticate with Gmail and DoubleTick. Opens your browser for Google sign-in. One-time setup — credentials are stored locally in ~/.doubletick/credentials.json.
doubletick logout
Remove stored credentials.
doubletick send
Send a tracked email. Injects a read-tracking pixel, sends via Gmail API, and registers the track.
doubletick status
Check if a tracked email has been opened.
doubletick dashboard
List all your tracked emails with open rates and stats.
MCP Server
DoubleTick works as an MCP server so AI agents (Claude Code, Claude Desktop, etc.) can send and track emails natively.
Setup
Add to your Claude configuration:
You must run doubletick login first — the MCP server uses the same stored credentials.
Tools
| Tool | Description |
|------|-------------|
| send_tracked_email | Send an email with read tracking |
| check_tracking_status | Check if a tracked email has been opened |
| list_tracked_emails | List recent tracked emails with stats |
How It Works
1. You compose an email (text or markdown)
2. The CLI converts it to HTML, generates a tracking ID, and injects a 1x1 tracking pixel
3. The email is sent via the Gmail API
4. The track is registered with DoubleTick's backend
5. When the recipient opens the email, the pixel fires and the open is logged
6. You check the status via doubletick status
The entire DoubleTick backend (pixel serving, open logging, deduplication, device detection) works unchanged. The CLI is just a new way to inject the pixel — replacing the Chrome extension's role for terminal/agent workflows.
Architecture
Requirements