agent-crm

A small CRM your AI agent can work. It exposes an MCP endpoint so an agent can search contacts, run the call queue, log calls and move deals, without being able to delete anything or send email. A plain web app shows you everything it did.

FastAPI, sqlite, Jinja2, Docker. One container, one database file, no external services.

Status: pre-1.0. The MCP tool set and the schema may change between releases. Back up data/crm.db before upgrading.

Who it's for

A good fit if you are one person (a solo consultant, a small clinic, a tradie) who sells through calls and follow-ups, and you want an agent to do the CRM busywork while you keep a clear view of the pipeline.

Not a fit if you need multiple users with roles and permissions, email sent and received inside the CRM, reports and dashboards, or a native mobile app. These are left out on purpose; see docs/SCOPE.md.

Related MCP server: Follow Up Boss MCP Server

Quick start

For trying it out. docker-compose.yml is a development setup with live reload; see Production for a real deployment.

git clone https://github.com/sevasek/agent-crm.git && cd agent-crm
cp .env.example .env
docker compose up --build -d
docker compose exec app python scripts/create_admin.py you@example.com "Your Name"
docker compose exec app python scripts/seed_services.py   # optional example services

Open http://localhost:8000 and log in.

Connect an agent

Generate a key, put it in .env as CRM_MCP_API_KEY, and recreate the container (a plain restart does not reload .env):

python -c "import secrets; print(secrets.token_hex(32))"
docker compose up -d

Then point any MCP client at http://localhost:8000/mcp (Streamable HTTP) with Authorization: Bearer <key>. Check it works:

curl -sS http://localhost:8000/mcp \
  -H "Content-Type: application/json" -H "Accept: application/json" \
  -H "Authorization: Bearer $CRM_MCP_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

An agent can search contacts (search_partners), pull today's queue (get_call_queue), log what happened (record_call_outcome, log_activity), and move deals (set_deal_stage). It cannot delete records, send email, manage users, or reshape the pipeline. Tools tell the agent to search before it creates, and updates fill empty fields instead of overwriting yours.

Hosted connectors that need OAuth 2.1 with PKCE can use /oauth/authorize. Full tool list, auth and limits: docs/MCP.md.

What's inside

• Companies and people in one table; people link to their company.

• Deals on a pipeline you define: stage names, order and roles are data.

• A next action and date on every deal, with due and overdue flags and a daily check that logs each due follow-up on the contact's timeline.

• A daily call list ranked out of 100 by a fixed formula you can read (deal value, source, contact completeness, recency).

• A phone-first call view with tap-to-call, the offer to pitch, and one-tap outcomes.

• Weighted fit rules, a service catalogue and priced offers you configure.

• Lead ingest over an API or CLI, with duplicate matching.

• Delegated tasks to hand work to another agent or a person, with an optional webhook.

• An optional webhook when a deal enters a nurture stage.

It starts empty apart from a starter pipeline: services, offers and fit rules are yours to define. Judgement lives in your agent, not in the CRM; scores are plain formulas, not a model.

Production

docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d --build

The app binds to 127.0.0.1:8000. Put a TLS-terminating reverse proxy in front and forward everything, including /mcp and /oauth/*. In .env:

• SECRET_KEY: a real one, not the placeholder.

• SECURE_COOKIES=true and BASE_URL=https://your.domain.

• TRUSTED_PROXIES: your proxy's address, so rate limits use the real client IP.

• TZ: decides what "today" means for follow-ups.

Security defaults: login uses expiring session cookies with CSRF protection; login and API endpoints are rate limited; the lead-ingest, stages and MCP keys are separate, and each endpoint refuses all requests until its key is set. Set BOOTSTRAP_ADMIN_EMAIL and BOOTSTRAP_ADMIN_PASSWORD once to create the first admin without shell access, then remove the password and recreate the container.

The staleness-cron service runs the follow-up check on start and daily at 08:00.

Ingest leads

POST /api/v1/leads with X-API-Key: $CRM_API_KEY (header only), or from the CLI:

python scripts/inject_leads.py --dry-run tests/fixtures/leads/example.json
python scripts/inject_leads.py tests/fixtures/leads/example.json

service_slug must already exist in your catalogue. Field meanings and matching rules are in docs/DATA_MODEL.md. To load contacts from markdown files, see scripts/import_clients.py.

Docs

SCOPE.md what's in and out and why · DATA_MODEL.md entities, schema and ingest rules · MCP.md the agent interface

Contributing

The scope is deliberately narrow, so please open an issue to discuss a feature before sending a pull request. Bug fixes are welcome directly. Run the tests first:

pip install -r requirements-dev.txt
python -m pytest tests/ -q

Support and security

Questions and bugs: open an issue. To report a vulnerability, use the private security report form rather than a public issue (see SECURITY.md).

Want it run for you? A managed and supported option is $60 AUD per month for secure hosting: https://sevasek.com/crm

License

MIT