io.github.khaoss85Published by GitHub account khaoss85v0.1.0Updated Nov 2, 2026
Read-only docs for the Accordo CRM framework: what it proves, and where it stops.
Read-only documentation lookup for the Accordo CRM framework: search its docs, resolve capability claims with their limits, and check which CRM jobs are…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.khaoss85%2Fagent-crm/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"agent-crm": {
"type": "http",
"url": "https://accordo.dev/api/mcp"
}
}
}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 [email protected], 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.
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.
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.
Every CRM eventually asks you to bend your process to fit its model. The two usual escapes both cost something:
This framework is the third option: an agent generates the application, and the framework
supplies the parts teams always get wrong under deadline. The test any developer can apply
is "if this project disappears tomorrow, what am I left with?" Here the answer is: a Node
application in your repository, with SQLite as a Node built-in, one pinned [email protected]
driver only if you select PostgreSQL, and a SQLite file any client can open.
Each line below is bound to a merged test. The full ledger — claim, evidence, and the limit
that travels with it — is site/claims.json, and the review discipline
behind it is docs/QUALITY_GATES.md.
The whole suite runs on every push, together with the smoke test. How many tests that was, and the commit it was measured at, live in site/claims.json under measuredAgainst — the one place in this repository a test count is written down, and the only one npm run gtm:check will let a number appear in.
Node.js 22.16 or newer. SQLite uses Node's built-in adapter; PostgreSQL requires the one
pinned driver [email protected] (tests/spine-v2-m3b-postgresql-adapter.test.js). No ORM, no
build step.
npm run tour is the fastest way to see what this actually is. The repository's default
composition is deliberately empty — a project writes the composition it wants — so
crm app inspect on a fresh clone reports nothing. The tour runs the starter installer (the
same one CI runs on every push) into a directory it keeps, then inspects the result:
It ends on the eleven things the inspector says it cannot see, because a tour that shows only
the good half is not worth running. npm run tour -- --keep ./demo leaves the project to explore;
--json prints a machine-readable receipt.
npm run falsify is the other direction. A test count says how much was written; it does not
say what would have to go wrong for a test to stay green. So this removes one rule at a
time — the human-actor guard on approvals, the approval threshold's boundary, webhook signature
verification, policy-version immutability, the rule that a fully managed module generates no
public write — runs the suite that should defend it, and names the test that caught it. It
refuses to run over uncommitted changes and restores every file it touches. Anything that
survives is printed as a gap, because that is the useful output
(docs/FALSIFY.md, tests/falsify.test.js).
npm run demo creates two renewals and is asserted by scripts/smoke.js on every push:
Claude Code reads CLAUDE.md, .mcp.json and .claude/skills/. Codex reads AGENTS.md
and .codex/config.toml. Both are checked in and wired together.
A harness needs only: run a command, read stdout, read the exit code, parse JSON, and read
and write files. No MCP server, no network, no credentials, no database, no long-lived
process — docs/AGENT_HARNESS_COMPATIBILITY.md.
Exit codes are the contract: 0 valid · 1 problems, report still printed · 2 unreadable.
The MCP server runs over stdio (node --no-warnings packages/mcp/bin/server.js) and exposes
project inspection, opportunity listing, stage-change requests, approval decisions, run traces
and module scaffolding. Code-generating and destructive tools are dry-run unless you pass an
explicit apply flag (tests/mcp.test.js, tests/scaffold.test.js — docs/MCP.md).
It is stdio-only and local-only: there is no hosted or authenticated MCP endpoint, and the server
inherits the authority of the process that starts it.
Read this before evaluating anything above. docs/benchmarks/CRM_JTBD_MATRIX.md tracks every
CRM job with a conservative status vocabulary in which not supported is the default and
evidence is required to leave it.
Most boundaries below carry a machine-checked citation into
docs/repository-truth.json, the generated fact document
(repositoryTruthContract: 1, ADR-039). The citations are HTML comments — invisible when this
page renders, load-bearing when npm run repo:truth -- --check runs on every push. A cited
sentence that survives the code it describes fails that check. Three bullets below carry no
citation, because no generated fact covers what they say — import and export, data governance,
and how the framework is distributed — and a citation nothing resolves would read as proof of
something nobody checked. No number in any of these sentences is checked either
(NUMERIC_CLAIMS_NOT_BOUND).
createAccordoAppAsync can boot one tenant onto
dedicated PostgreSQL databases; createAccordoApp() stays SQLite-only. Shared-database
row-level tenancy is not implemented, and this is not a production-readiness claim.
docs/strategy/CRM_BUILD_BENCHMARK.md is the
protocol, not a result.
tests/customer-data-foundation.test.js.
npm create accordo — the published [email protected] — scaffolds a project that boots,
reports valid from app inspect and exits 0 from project doctor, by copying the framework
source into it; the same bootstrap runs from a checkout
(node packages/create-accordo/bin/create-accordo.js <dir> --apply, no install, no network —
tests/project-bootstrap.test.js). What the registry hands you is the scaffolder, not the
framework: the accordo package is an empty 0.0.1 name reservation, deliberately. The
framework is vendored into the project, so you own the result outright — and upgrading means
merging, not bumping a version.The agent never writes to a database table. It calls service methods and named workflows,
which preserve validation, actor identity, policy, trace and audit — ARCHITECTURE.md.
MIT, confirmed by ADR-023.
Source: README.md at commit 8fe6435
Search the Framework Documentation
Keyword search across this framework's documentation set (README, AGENTS, ARCHITECTURE, PRODUCT, DECISIONS and everything under docs/). Returns the file path, the nearest heading and an excerpt for each hit. Read-only; it serves documentation, never customer records.
limitqueryrequiredGet a Capability and Its Limitation
Resolve a capability from the claims ledger by id (C-nn), by standing-limitation id (L-nn), or by topic. Every capability is returned together with the evidence that proves it and the limitation that bounds it — this tool cannot return one without the other.
idlimittopicCheck Whether the Framework Does a Job
Answer "can this framework do X?" against the CRM jobs-to-be-done index. Returns the matching jobs with their status (not supported / partially supported / technically supported / validated end to end), the tests that prove them, and an explicit answer when the truth is that the job is not supported.
limitqueryrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
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 reviewnpm run tour # compose the whole application and inspect itnpm run verify # source checks, then the whole test suitenpm run falsify # break five rules on purpose and watch the suite catch themnpm run demo # the approval slice, end to endnpm run dev # http://localhost:4000 modules 98 resources 77 policies 7 packages 9 actions 65 providers 1
production posture — not a readiness claim: the framework authenticates nobody (a deployment adapter supplies verified identity), while tenancy — one tenant per application instance — and authorization are owned and enforced by the framework. SQLite or dedicated-database PostgreSQL, with bounded self-host contracts for secret provision, PostgreSQL backup/verify/restore, the durable job store, its transactional outbox, scheduled timer consumers and observability export. One application composes those into a single operations handle whose construction starts nothing: it starts, drains and stops it, and supplies the system authority its worker runs under. Nothing autostarts. Absent: shared-database tenancy, an autostarted or operator-managed worker service, any managed jobs service, managed secret custody, managed backup custody/scheduling/retention and an observability backendRead AGENTS.md, PRODUCT.md and docs/PROJECT_STATUS.md.Run npm run crm -- app inspect --json.Tell me which parts of my commercial process this already supports, and which it does not.npm run crm -- app inspect --json # what this application containsnpm run crm -- solution check plan.json # is this plan still valid against itpackages/core/ the runtime platform: registry, services, workflow engine, auditpackages/modules/ CRM domain primitivespackages/domains/ optional domain packages (contracts, delivery) on a public contractpackages/mcp/ tools and context exposed to coding agentsapps/ API server and generated Admin