Agent Ready CRM
A CRM for AI agents, served as an MCP server: organizations, contacts, interactions, deals, and the evidence behind them. An agent resolves a company or a person before it writes, logs every touch, moves deals through a pipeline, and records the facts it found with the quote and the URL that prove them. A person sees the same records in views that render inside MCP Apps hosts.
It runs on your own machine: one SQLite file, no account, no cloud service. A hosted service
at mcp.agentreadycrm.com, serving the same tools to a team, is coming soon.
Install
Run it with uv (Python 3.13 or later):
uvx agentreadycrm
That serves MCP over stdio. To add it to Claude Code:
claude mcp add agentreadycrm -- uvx agentreadycrm
For Claude Desktop and other hosts that install MCP bundles, the bundle
@nimblebraininc/agentreadycrm is available from mpak. It runs the
same package and asks where to keep the database.
Any other MCP client that starts a stdio server can run uvx agentreadycrm the same way. To
serve HTTP on 127.0.0.1 instead, run uvx agentreadycrm --http; HTTP requires a bearer
token, which uvx agentreadycrm --print-token prints. See docs/local.md.
Where your data lives
Everything is in one SQLite file, crm.db, in your user data directory:
| OS | Default location |
|---|---|
| macOS | ~/Library/Application Support/agentreadycrm/crm.db |
| Linux | $XDG_DATA_HOME/agentreadycrm/crm.db (~/.local/share/... when unset) |
| Windows | %LOCALAPPDATA%\agentreadycrm\crm.db |
Set PEOPLE_LOCAL_DB to use another file. Keep it on a local disk, not a network share.
Several clients may use the same file at once. Upgrades, backups and the HTTP token are
covered in docs/local.md.
Local or hosted
| Local (this package) | Hosted (coming soon) | |
|---|---|---|
| Runs | On your machine, started by your MCP client | At mcp.agentreadycrm.com |
| Data | One SQLite file you own | A managed Postgres database |
| Who | One person | A team, each signed in |
| Tools, views, skills | The same | The same |
Both serve the same core: a client sees the same tools, schemas, views and skills, and only where identity comes from and where the data lives differ.
Tools
46 tools, in these families:
| Family | Tools |
|---|---|
| Resolve and import | find_or_create_organization, find_or_create_contact, import_organizations, import_contacts (up to 500 rows a call) |
| Read and list | get_contact, get_organization, get_opportunity, list_contacts, list_organizations, list_opportunities, list_interactions, count_records, resolve_external_refs |
| Change | update_contact, update_organization, update_opportunity, log_interaction |
| Duplicates, hide and delete | merge_contacts, merge_organizations, archive_contact, archive_organization, delete_contact, delete_organization |
| Deals and the pipeline | create_opportunity, move_opportunity, get_pipeline, define_pipeline_stage, update_pipeline_stage |
| Custom fields | define_field, update_field, list_fields |
| Lookalike companies | link_similar_organizations, list_similar_organizations, promote_organization |
| Evidence: signals | record_signal, withdraw_signal, update_signal, get_signal, list_signals, list_signal_types, define_signal_type, update_signal_type |
| Evidence: proof points | record_proof_point, verify_proof_point, get_proof_point, list_proof_points |
A few rules shape all of them:
- Resolve before you write.
find_or_create_*matches by external reference, then domain or email, then name, and a match fills only empty fields, so repeating a call converges on one record. - Every result carries a
next_steptelling the agent what to do with it, and every failure is one error envelope with anext_stepthat names the fix. - Listings query, they don't walk.
list_*take a free-textquery, afilterandsorton any core, custom, related or rollup field, andcolumns, and page with a cursor. - Nothing is removed. A delete marks a record so no read finds it; archiving is the reversible hide.
The server also serves two skills (skill://people/SKILL.md and
skill://people-evidence/SKILL.md) with worked examples for hosts that load skills.
Views
Four views, ui://people/contacts, organizations, opportunities and settings, render
in hosts that support MCP Apps. Each record has an
address (people://contacts/<id> and so on) that a host can open in a view. The views read
and change data only through the same tools.
More
docs/architecture.md: runtimes, the data model, deletion and archiving, the surface, errors and annotations.docs/local.md: the database file, several processes, the HTTP token, upgrades, backups, and what differs on SQLite.CONTRIBUTING.md: building and testing.
Licence
MIT. See LICENSE.
Metadata
Release files for agentreadycrm 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agentreadycrm-0.1.0.tar.gz | 393.0 kB | With provenance | Details for agentreadycrm-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentreadycrm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agentreadycrm-0.1.0-py3-none-any.whl |
Total release size: 803.4 kB
Release files / agentreadycrm-0.1.0.tar.gz
| Download URL | agentreadycrm-0.1.0.tar.gz |
|---|---|
| Size | 393.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0cc7a2ff380f1d0e2377893aa5c570a2c54dabd60865267852b6574b87872b29
|
|
BLAKE2b-256 checksum How to use checksums |
8c9c689e8e921e32194c57040909a87bb2a72b15d77efefbf54649a31dbd3a12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 18, 2026.
Transparency logRelease files / agentreadycrm-0.1.0-py3-none-any.whl
| Download URL | agentreadycrm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 410.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
585beb91e0a7cccc22ab999bdd350f1ad8c8769cfc4ca4517a3b8f5eb7633553
|
|
BLAKE2b-256 checksum How to use checksums |
141bf3d0fcc0846e948bad3f22f3e9a12c30cab59bc532e960369c4d2a5952d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 18, 2026.
Transparency logSecurity for agentreadycrm 0.1.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for agentreadycrm-0.1.0.tar.gz
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 Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.