MailPilot
Agent-operated CRM with Gmail as the communication layer.
Overview
MailPilot manages contacts, companies, and communication workflows through Gmail API. It is designed to be operated by AI agents -- Claude Code as the strategic orchestrator and an internal Pydantic AI agent for real-time reactive work.
Two-Layer Intelligence
- Claude Code -- strategic orchestrator. Creates workflows, assigns contacts, reviews outcomes, generates reports. Operates the system via CLI.
- Internal Pydantic AI agent -- subordinate tactical executor. Handles inbound email classification, auto-replies, and follow-up scheduling within workflows.
Key Capabilities
- Contact and company management -- track relationships, tag for segmentation, annotate with notes
- Activity timeline -- unified chronological log of all interactions per contact
- Email workflows -- inbound auto-reply and outbound campaigns via Gmail API with service account delegation
- Task scheduling -- deferred agent work with scheduled execution for long-running processes
- Reporting -- Claude Code queries the database and generates activity summaries, relationship health, and campaign effectiveness reports
Install
MailPilot ships on PyPI as mailpilot-crm. The package installs the mailpilot command. Python 3.14 or later is required.
Install with uv:
uv tool install mailpilot-crm
Or install with pip:
pip install mailpilot-crm
Verify the install:
mailpilot --version
Quick Start
MailPilot needs PostgreSQL 18 and a Google service account with domain-wide delegation for the Gmail API.
Create the database. MailPilot provisions the schema on first connection:
createdb mailpilot
Point MailPilot at the database:
mailpilot config set database_url postgresql://localhost/mailpilot
Set the Google service account credentials:
mailpilot config set google_application_credentials /path/to/service-account.json
Set the Anthropic API key:
mailpilot config set anthropic_api_key sk-ant-...
Create the Gmail account MailPilot operates:
mailpilot account create --email user@example.com --display-name "User Name"
Sync the inbox:
mailpilot account sync
Start the event-driven sync loop:
mailpilot run
License
Copyright 2026 Konstantin Borovik.
Licensed under the Apache License, Version 2.0. See LICENSE for the full text.
1 maintainer
Release files for mailpilot-crm 0.19.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mailpilot_crm-0.19.1.tar.gz | 180.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mailpilot_crm-0.19.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 379.7 kB
Release files / mailpilot_crm-0.19.1.tar.gz
| Download URL | mailpilot_crm-0.19.1.tar.gz |
|---|---|
| Size | 180.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
51dcc4f4d1a5f0113ea385332d9eab8e9be2c745e09798e43c25c5771c6b0377
|
|
BLAKE2b-256 checksum How to use checksums |
fbd112ceb2fb346f5afdcfaf8578d16ee168b6cf5df7163321441173202202da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.
Transparency logRelease files / mailpilot_crm-0.19.1-py3-none-any.whl
| Download URL | mailpilot_crm-0.19.1-py3-none-any.whl |
|---|---|
| Size | 199.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
944c3f02fc335d4697b6080a424cfd9a29ae279389f2f8219b50fa81feaa3e2a
|
|
BLAKE2b-256 checksum How to use checksums |
518a6b87044140c292812eb18de692cd2e0e6c96b3e966c6f49e07b51e6b117a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.
Transparency log
