Agent CRM MCP server

Accordo

Build the customer and revenue system your business actually runs.

Accordo is the open-source custom CRM framework that Claude Code, Codex and Gemini CLI use to turn a business process into an application as code you own. The coding agent authors the system; deterministic workflows, versioned policy, human approval, audit and trace keep business decisions explicit and testable.

Human product overview: accordo.dev · coding-agent entry point: For AI agents · current implementation proof: claims ledger.

The name is chosen and the domain registered. npm create accordo scaffolds a working project from the published create-accordo@0.1.0, the August 19 source snapshot. Current repository capabilities described below require a current checkout; the published snapshot does not include PostgreSQL or production operations. The accordo package itself remains an empty 0.0.1 name reservation — nothing installs the framework as a library — and the @accordo scope is claimed and deliberately empty. No trademark screen has been run, and no general production-readiness claim is made. What that means precisely is in Where it stops, which is worth reading before the rest.

Business request
      ↓  "Renewals of €50,000 or more need a manager's sign-off."
Claude Code / Codex
      ↓  reads AGENTS.md · 12 skills · MCP · `crm app inspect`
Modules + deterministic workflows + versioned policy
      ↓
API + Admin + trace + audit — in your repository, as code you review

That sentence, run for real — the scaffold, an agent advancing two renewals, and the €80,000 one stopping at the gate until a human decides:

Recorded from the real commands with VHS; the script is .github/demo.tape, so the recording can be reproduced rather than trusted.

When to reach for Accordo

reviewable code rather than configuration inside somebody else's runtime.

• Custom CRM: when the commercial process is the product and the result should be

commercial record chain with governed actions, bounded JSON imports and logical customer identity. Accordo is not a full CDP.

• Customer Hub: when “hub” means one

compose the application while versioned policy and named humans retain business decisions. It is agent-built software, not an autonomous decision-maker.

• Smart CRM: when a coding agent should

broad ingestion, identity graphs and audiences, and Accordo owns the deterministic CRM process layer beside it with bounded JSON imports and logical identity. Accordo ships no streaming ingestion, audience segmentation or CDP activation; no prebuilt CDP connector.

• CDP + CRM: when an external CDP owns

Those adjacent terms are retrieval paths, not extra capability claims. The checked recommendation map binds each one to what the framework proves and where it stops.

Why this exists

Every CRM eventually asks you to bend your process to fit its model. The two usual escapes both cost something:

someone else's runtime. When the ceiling arrives, you fork a monorepo.

• Configure a platform — fast to start, and your customization lives as metadata inside

semantics, approvals and audit. Usually late, usually under pressure.

• Build from scratch — total freedom, and every team re-derives validation, pipeline

Shortened. The full README is on GitHub.