Back to search

100

MCP live MCP 2026-07-28 streamable-http

io.github.khaoss85/agent-crm

io.github.khaoss85/agent-crm

Read-only docs for the Accordo CRM framework: what it proves, and where it stops.

Uptime

100.0%

3 direct probes · 30d

Response

605ms

last probe

Tools

callable

Resources

139

readable

Prompts

available

Primary URL

https://accordo.dev/api/mcp

Tools · 3

search_docs

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 ea…

get_capability

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 …

check_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…

Resources · 139

documentation-index

Every document this server serves, what it is, and what is deliberately excluded.

docs://index

claims-ledger

Every public capability claim bound to the tests that prove it, each paired with the limitation that bounds it, plus the standing limitations of the framework.

docs://claims

jobs-index

The CRM jobs index generated from docs/benchmarks/CRM_JTBD_MATRIX.md, each job carrying one of four statuses. Absent from a checkout until `node scripts/generate-jobs.js` has been run.

docs://jobs

AGENTS.md

This repository is an agent-native CRM framework. Preserve the separation between deterministic CRM state and AI-assisted development/orchestration.

docs://AGENTS.md

ARCHITECTURE.md

CRM state is deterministic. AI agents interpret the user's intent and compose the system, but state changes pass through services and workflows.

docs://ARCHITECTURE.md

CLAUDE.md

Read `AGENTS.md` first and follow it as the canonical repository guidance.

docs://CLAUDE.md

CONTRIBUTING.md

Thank you for looking. This project has an unusual amount of written-down process for its size,

docs://CONTRIBUTING.md

DECISIONS.md

**Status:** accepted

docs://DECISIONS.md

GEMINI.md

Read `AGENTS.md` first and follow it as the canonical repository guidance. It is

docs://GEMINI.md

PRODUCT.md

Accordo is a framework that lets a user describe a commercial process to Codex or Claude Code and have the agent safely build, run, inspect and improve a CRM a…

docs://PRODUCT.md

README.md

**Build the customer and revenue system your business actually runs.**

docs://README.md

ROADMAP.md

This file is a **pointer, not a ledger.** It used to carry a four-milestone plan

docs://ROADMAP.md

SECURITY.md

This framework is **local-development-only** and has no production security spine. That is

docs://SECURITY.md

TASKS.md

The first unchecked item is the default next task for Codex.

docs://TASKS.md

docs/ACTIONS.md

A **record action** is a lifecycle operation on one record that is more than a

docs://docs/ACTIONS.md

docs/ADMIN.md

The Admin is a zero-build, dependency-free static app (`apps/admin/public/`) served by the HTTP server at `/`. It has two parts: the handwritten CRM dashboard …

docs://docs/ADMIN.md

docs/ADMIN_SMOKE.md

Automated tests cover the Admin at the DOM/integration level (real server + real fetch + a fake document) and run in CI. **They do not drive a real browser, an…

docs://docs/ADMIN_SMOKE.md

docs/AGENT_HARNESS_COMPATIBILITY.md

Accordo is not built for one coding agent. AX1 (`app inspect`) and AX2

docs://docs/AGENT_HARNESS_COMPATIBILITY.md

docs/API.md

Base URL: `http://localhost:4000`

docs://docs/API.md

docs/APPLICATION_INSPECTION.md

One deterministic document describing the application a project has actually

docs://docs/APPLICATION_INSPECTION.md

docs/CODER_TOOLING_ROADMAP.md

The surfaces a coding agent uses to understand, plan and change an Accordo

docs://docs/CODER_TOOLING_ROADMAP.md

docs/COMMERCIAL_OPERATIONS.md

Catalog, quotes and discount approval over the B2B starter — local development

docs://docs/COMMERCIAL_OPERATIONS.md

docs/CONTRACT_ACTIVATION.md

Turning a signed immutable Order into a live commercial state: one Commercial

docs://docs/CONTRACT_ACTIVATION.md

docs/DELIVERY_CHANGE_ACCEPTANCE.md

M14b1 recorded what a delivery project **consumed**. M14b2 records what changed

docs://docs/DELIVERY_CHANGE_ACCEPTANCE.md

docs/DELIVERY_ECONOMICS.md

M13 planned a delivery project. M14a let a human run it. M14b1 records **what

docs://docs/DELIVERY_ECONOMICS.md

docs/DELIVERY_HANDOVER.md

Turning the pending Delivery Obligations of an activated contract into a

docs://docs/DELIVERY_HANDOVER.md

docs/FALSIFY.md

node scripts/falsify.js # the fast set — a couple of seconds

docs://docs/FALSIFY.md

docs/HANDOVER_CODEX.md

Target GitHub owner: `khaoss85`

docs://docs/HANDOVER_CODEX.md

docs/IMPLEMENTATION_EVIDENCE.md

`accordo solution verify <plan.json> --evidence <evidence.json> [--json] [--root dir]` — **DX10**.

docs://docs/IMPLEMENTATION_EVIDENCE.md

docs/JTBD.md

“I need this commercial outcome”

docs://docs/JTBD.md

docs/LEAD_INTELLIGENCE.md

Enrichment, explainable scoring and deterministic routing over the Lead

docs://docs/LEAD_INTELLIGENCE.md

docs/MCP.md

The server uses newline-delimited JSON-RPC over stdio. Diagnostics are written only to stderr.

docs://docs/MCP.md

docs/MODULE_EVOLUTION.md

How a record that already exists — with rows in it — gains a field, a status or

docs://docs/MODULE_EVOLUTION.md

docs/MODULE_FACTORY.md

The module factory turns a validated manifest (`docs/MODULE_MANIFEST.md`) into a complete, runnable backend module: readable service code, deterministic migrat…

docs://docs/MODULE_FACTORY.md

docs/MODULE_MANIFEST.md

A module manifest is a small declarative JSON file that describes one CRM module entity. The framework validates it with precise errors and generates determini…

docs://docs/MODULE_MANIFEST.md

docs/PACKAGE_AUTHORING.md

How Claude Code, Codex — or a person — adds a bounded domain to an Accordo

docs://docs/PACKAGE_AUTHORING.md

docs/PROJECT_STATUS.md

The single operational snapshot of the repository. Volatile facts — merged

docs://docs/PROJECT_STATUS.md

docs/QUALITY_GATES.md

The review discipline that produced Milestones 6–11 written down as repository

docs://docs/QUALITY_GATES.md

docs/RENAME_SURFACE.md

The complete inventory of where the working title lives, grouped by what breaks when it moves.

docs://docs/RENAME_SURFACE.md

docs/RENEWAL_AMENDMENT.md

**Milestone M16b. ADR-035. Packages: `contracts` (v7) and `lifecycle` (v2).**

docs://docs/RENEWAL_AMENDMENT.md

docs/REPOSITORY_TRUTH.md

`npm run repo:truth` · `npm run repo:truth -- --check` — **ADR-039**.

docs://docs/REPOSITORY_TRUTH.md

docs/SCENARIO_EVIDENCE.md

`accordo scenario run <scenario> [--json] [--root dir]` — **DX6**.

docs://docs/SCENARIO_EVIDENCE.md

docs/SERVICE_OPERATIONS.md

The **third** domain package built under ADR-018, and the second that depends on

docs://docs/SERVICE_OPERATIONS.md

docs/SIGNATURE_ORDER.md

Turning an approved Quote Version into a signed commitment and one immutable

docs://docs/SIGNATURE_ORDER.md

docs/SKILL_PACKAGING.md

A skill is the part of this framework that installs into somebody else's agent.

docs://docs/SKILL_PACKAGING.md

docs/SOLUTION_PLAN.md

AX1 answers *what has this project actually composed*. This answers the next

docs://docs/SOLUTION_PLAN.md

docs/WORK_TASKS.md

**Work v1 (ADR-030), the `work` package.** Follow-up work a person must do, and

docs://docs/WORK_TASKS.md

docs/architecture/AGENT_TOOL_SURFACE.md

**Status: strategy and proposed policy. Nothing here is implemented.** No tool

docs://docs/architecture/AGENT_TOOL_SURFACE.md

docs/architecture/EXTRACTION_PREPARATION.md

**Nothing in this document is implemented, and nothing in it authorizes an

docs://docs/architecture/EXTRACTION_PREPARATION.md

docs/architecture/INTELLIGENCE_PACKAGE_TARGET.md

**Status: accepted target, nothing implemented.** ADR-021 and ADR-022 are

docs://docs/architecture/INTELLIGENCE_PACKAGE_TARGET.md

docs/architecture/LEGACY_ALIGNMENT_MATRIX.md

**Status: assessment and policy. No domain is refactored by the PR that

docs://docs/architecture/LEGACY_ALIGNMENT_MATRIX.md

docs/benchmarks/AGENT_TOOL_SELECTION_PROTOCOL.md

**Status: protocol and pilot instrument. No product command, MCP tool, runtime or

docs://docs/benchmarks/AGENT_TOOL_SELECTION_PROTOCOL.md

docs/benchmarks/CPR_PROTOCOL.md

The question this answers, and the only one it answers: **given only the repository, does a clean

docs://docs/benchmarks/CPR_PROTOCOL.md

docs/benchmarks/CRM_JTBD_MATRIX.md

A validation catalogue of classic CRM jobs-to-be-done, tracking what the framework genuinely supports today. This is **not** a marketing claim: a JTBD is marke…

docs://docs/benchmarks/CRM_JTBD_MATRIX.md

docs/benchmarks/PILOT_PROTOCOL.md

How one operator runs one benchmark prompt, end to end, and what they are allowed

docs://docs/benchmarks/PILOT_PROTOCOL.md

docs/benchmarks/TOOL_SELECTION_PILOT_2026-08-13.md

Date: 2026-08-13

docs://docs/benchmarks/TOOL_SELECTION_PILOT_2026-08-13.md

docs/benchmarks/URR_PILOT_2026-08-10.md

Date: 2026-08-10

docs://docs/benchmarks/URR_PILOT_2026-08-10.md

docs/editions/CLOUD_INTEGRATION_CONTRACT.md

**Status: design. The contracts marked *shipped* exist in the public repository

docs://docs/editions/CLOUD_INTEGRATION_CONTRACT.md

docs/editions/MANAGED_CLOUD_EDITION.md

**Status: boundary definition. Nothing here is implemented, and this document

docs://docs/editions/MANAGED_CLOUD_EDITION.md

docs/editions/OPEN_SOURCE_EDITION.md

**Status: boundary definition. This document moves nothing and changes no

docs://docs/editions/OPEN_SOURCE_EDITION.md

docs/editions/PRIVATE_REPOSITORY_MIGRATION.md

The boundary is decided in [`REPOSITORY_BOUNDARY.md`](REPOSITORY_BOUNDARY.md).

docs://docs/editions/PRIVATE_REPOSITORY_MIGRATION.md

docs/editions/PUBLIC_ARTIFACT_POLICY.md

What may live in the public repository, how public claims stay sourced from it,

docs://docs/editions/PUBLIC_ARTIFACT_POLICY.md

docs/editions/REPOSITORY_BOUNDARY.md

**Status: design only. This phase moves nothing.** No private repository was

docs://docs/editions/REPOSITORY_BOUNDARY.md

docs/evidence/commercial-extraction.md

The second legacy domain to leave `packages/core`, on the pattern the Lead

docs://docs/evidence/commercial-extraction.md

docs/evidence/lead-intelligence-extraction.md

**What this is.** The rails an agent actually used to move a legacy domain into

docs://docs/evidence/lead-intelligence-extraction.md

docs/jtbd/AGENTS.md

Root `AGENTS.md`, `docs/QUALITY_GATES.md`, ADRs and Accordo rails are authoritative. This file only narrows how to use the desired-state catalog.

docs://docs/jtbd/AGENTS.md

docs/jtbd/MASTER.md

**HISTORICAL V1.0 SNAPSHOT — NOT CANONICAL FOR CATALOGUE V1.1.** Current desired-state records, autonomy and approval boundaries are defined only by `catalog/j…

docs://docs/jtbd/MASTER.md

docs/jtbd/NORMALIZATION_V1_1.md

Catalogue v1.1 ratifies `L3 => human_approval_required = true`. The machine-readable approval-boundary review evaluates every affected record's canonical job, …

docs://docs/jtbd/NORMALIZATION_V1_1.md

docs/jtbd/PORTFOLIO_ALIGNMENT.md

`node scripts/jtbd-gate.js` · `--write` · `--reverify` · `--json`

docs://docs/jtbd/PORTFOLIO_ALIGNMENT.md

docs/jtbd/PUBLIC_PRIVATE.md

Machine-readable form: `PUBLIC_PRIVATE.json`, checked by `scripts/jtbd-gate.js`

docs://docs/jtbd/PUBLIC_PRIVATE.md

docs/jtbd/README.md

Catalog version `2026-08-21.1`: **30 personas · 600 JTBD · 225 capabilities · 10 end-to-end scenarios**.

docs://docs/jtbd/README.md

docs/jtbd/coverage/MATRIX_CROSSWALK.md

Machine-readable form: `matrix_crosswalk.json`. Checked by `scripts/jtbd-gate.js`.

docs://docs/jtbd/coverage/MATRIX_CROSSWALK.md

docs/jtbd/coverage/STATUS_CROSSWALK.md

`docs/jtbd/AGENTS.md` and `docs/jtbd/README.md` both send a Phase D reader here before an

docs://docs/jtbd/coverage/STATUS_CROSSWALK.md

docs/jtbd/prompts/01_repo_coverage_audit.md

You are auditing an agentic CRM repository against a desired-state catalog.

docs://docs/jtbd/prompts/01_repo_coverage_audit.md

docs/jtbd/prompts/02_gap_to_roadmap.md

- `docs/jtbd/catalog/jtbd.jsonl`

docs://docs/jtbd/prompts/02_gap_to_roadmap.md

docs/jtbd/prompts/03_jtbd_to_spec.md

Input JTBD ID: `<ACC-JTBD-...>`

docs://docs/jtbd/prompts/03_jtbd_to_spec.md

docs/jtbd/prompts/04_competitor_benchmark.md

Compare Accordo with selected products without relying on memory or vendor slogans.

docs://docs/jtbd/prompts/04_competitor_benchmark.md

docs/jtbd/prompts/05_simulate_lifecycle.md

Select a persona, a set of JTBD IDs or an end-to-end scenario from `data/e2e_scenarios.json`.

docs://docs/jtbd/prompts/05_simulate_lifecycle.md

docs/jtbd/quality/SEMANTIC_QUALITY_FINDINGS.md

Audit of the **semantic quality of the catalogue records themselves**: how the

docs://docs/jtbd/quality/SEMANTIC_QUALITY_FINDINGS.md

docs/jtbd/quality_report.md

`VALIDATION_OK`

docs://docs/jtbd/quality_report.md

docs/jtbd/reviews/ownership/README.md

Each approved non-candidate owner receives a separate Markdown review here. The canonical gate

docs://docs/jtbd/reviews/ownership/README.md

docs/jtbd/roadmap/OWNERSHIP.md

Machine-readable authority: `assignments.jsonl`. Published projection:

docs://docs/jtbd/roadmap/OWNERSHIP.md

docs/marketing/AWESOME_LIST_SUBMISSIONS.md

Original submission packet, sent 2026-08-26. Current states were reconciled on

docs://docs/marketing/AWESOME_LIST_SUBMISSIONS.md

docs/marketing/BENCHMARK_ARCHITECTURE.md

Accordo distinguishes **engineering benchmarks** (runtime correctness or performance), **agent benchmarks** (an agent/model executing a controlled build), **pr…

docs://docs/marketing/BENCHMARK_ARCHITECTURE.md

docs/marketing/BENCHMARK_PUBLICATION.md

What may be said in public about an Edition L run, and what may not. This is a

docs://docs/marketing/BENCHMARK_PUBLICATION.md

docs/marketing/CONTENT_PILLARS.md

Reconciled 2026-09-07. This is the current content queue; the durable method is

docs://docs/marketing/CONTENT_PILLARS.md

docs/marketing/CONTENT_PRODUCTION.md

`CONTENT_PILLARS.md` says **what** we write and in what order. `ORGANIC_GROWTH.md`

docs://docs/marketing/CONTENT_PRODUCTION.md

docs/marketing/CORRECTIONS.md

Every public claim this project made and then had to withdraw or narrow, with the commit that

docs://docs/marketing/CORRECTIONS.md

docs/marketing/DEPLOYMENT.md

`vercel.json` builds the dependency-free static site with `npm run site:check` and serves `site/dist`. The same build regenerates HTML, strategic Markdown, ret…

docs://docs/marketing/DEPLOYMENT.md

docs/marketing/DESIGN_BRIEF.md

Hand this to a designer who has no access to the repository. Everything needed

docs://docs/marketing/DESIGN_BRIEF.md

docs/marketing/FOUNDER_CHECKLIST.md

Reconciled 2026-09-07. The August namespace, repository-opening and first-deploy

docs://docs/marketing/FOUNDER_CHECKLIST.md

docs/marketing/GITHUB_LISTING.md

Everything the repository's public surface needs, written out so applying it is mechanical.

docs://docs/marketing/GITHUB_LISTING.md

docs/marketing/LAUNCH_PACKET.md

Copy for the two launch channels, written now so that it is written carefully rather

docs://docs/marketing/LAUNCH_PACKET.md

docs/marketing/NAME_VERIFICATION.md

**Historical check: 2026-08-07.** Availability results below are archived research,

docs://docs/marketing/NAME_VERIFICATION.md

docs/marketing/OBJECTIONS.md

The fifteen hardest things a sceptical developer says, and the answer in the project's own

docs://docs/marketing/OBJECTIONS.md

docs/marketing/PENDING_HUMAN_SUBMISSION.md

Decision queue reconciled 2026-09-07. This file tracks decisions and external

docs://docs/marketing/PENDING_HUMAN_SUBMISSION.md

docs/marketing/RECONCILIATION_AUDIT_2026-08-24.md

Initial repository HEAD was `82371d28509e3c8c7e8c857a30cf68d671f95563`. During final integration PR #119 merged as `cc2a1a6d9e8641af579ee0c486c5435907278ad6`; …

docs://docs/marketing/RECONCILIATION_AUDIT_2026-08-24.md

docs/marketing/ROUNDUP_OUTREACH.md

The articles a retrieval step reads when someone asks "best open source CRM",

docs://docs/marketing/ROUNDUP_OUTREACH.md

docs/marketing/SITE_ARCHITECTURE.md

This is the contract for accordo.dev. `scripts/site-build.js` implements it and `scripts/site-check.js` enforces the claim, linking, indexing and stale-negativ…

docs://docs/marketing/SITE_ARCHITECTURE.md

docs/marketing/drafts/2026-08-09-indie-hackers-refusal-surface.md

I am building Accordo, an open-source framework that coding agents use to build

docs://docs/marketing/drafts/2026-08-09-indie-hackers-refusal-surface.md

docs/strategy/AGENTIC_CRM_RESEARCH_2026_09.md

Research checked **2026-09-09**. This is a dated evidence supplement to

docs://docs/strategy/AGENTIC_CRM_RESEARCH_2026_09.md

docs/strategy/AGENTIC_WORKFORCE_ROADMAP.md

Status: product and architecture planning only. This document does not claim implementation or JTBD coverage.

docs://docs/strategy/AGENTIC_WORKFORCE_ROADMAP.md

docs/strategy/AGENT_CRM_CLOUD.md

**Status: public product specification, not an available managed offer.** This repository does not implement the Cloud control plane. Private platform and pilo…

docs://docs/strategy/AGENT_CRM_CLOUD.md

docs/strategy/AGENT_DISCOVERY.md

How this framework becomes discoverable — and, where possible, recommendable — in the channels where coding agents and their users decide what to build with. R…

docs://docs/strategy/AGENT_DISCOVERY.md

docs/strategy/AGENT_RECOMMENDATION.md

`AGENT_DISCOVERY.md` answers *which channels exist and how they work*. This document answers a

docs://docs/strategy/AGENT_RECOMMENDATION.md

docs/strategy/ANALYTICS_STUDIO.md

**Status: product strategy and roadmap only. Nothing in this document is implemented.** No semantic model, metric definition, dataset, report, dashboard, widge…

docs://docs/strategy/ANALYTICS_STUDIO.md

docs/strategy/BRAND_REQUIREMENTS.md

The current name is a working title, and it fails as a public brand on every axis that matters for this strategy:

docs://docs/strategy/BRAND_REQUIREMENTS.md

docs/strategy/CAMPAIGNS_JOURNEYS.md

**Status: product strategy only. Nothing in this document is implemented.** No campaign, proposal, audience, suppression, journey, enrolment, content asset, la…

docs://docs/strategy/CAMPAIGNS_JOURNEYS.md

docs/strategy/CATEGORY.md

Durable positioning for Accordo. Read [MASTER_PLAN.md](MASTER_PLAN.md) first.

docs://docs/strategy/CATEGORY.md

docs/strategy/CLOUD_JTBD.md

Operator and builder jobs for the optional managed layer. `AGENT_CRM_CLOUD.md`

docs://docs/strategy/CLOUD_JTBD.md

docs/strategy/CODING_AGENT_DX_NORTH_STAR.md

**Status: canonical decision rule.** This document does not describe a feature.

docs://docs/strategy/CODING_AGENT_DX_NORTH_STAR.md

docs/strategy/COMPETITOR_MAP.md

Research date: **August 20, 2026** for every row and paragraph marked *(re-checked 2026-08-20)*; **August 4, 2026** for everything else, which was **not** re-v…

docs://docs/strategy/COMPETITOR_MAP.md

docs/strategy/CONTRACT_SUBSCRIPTION_RENEWAL.md

**Historical design baseline, scoped on 2026-09-07.** The specification and

docs://docs/strategy/CONTRACT_SUBSCRIPTION_RENEWAL.md

docs/strategy/CRM_BUILD_BENCHMARK.md

A public, reproducible benchmark measuring whether a coding agent can turn a CRM brief into a working, deployed CRM using this framework — and how it compares …

docs://docs/strategy/CRM_BUILD_BENCHMARK.md

docs/strategy/CUSTOMER_REVENUE_OS_ROADMAP.md

**Historical design baseline, scoped on 2026-09-07.** The specification and

docs://docs/strategy/CUSTOMER_REVENUE_OS_ROADMAP.md

docs/strategy/DATA_GOVERNANCE.md

**Historical design baseline, scoped on 2026-09-07.** The specification and

docs://docs/strategy/DATA_GOVERNANCE.md

docs/strategy/DELIVERY_SERVICE.md

**Status: product strategy and roadmap only. Nothing in this document is implemented.** No delivery project, milestone, partner engagement, time tracking, chan…

docs://docs/strategy/DELIVERY_SERVICE.md

docs/strategy/DESIGN_TO_CRM.md

**Status: design only. The generated Admin exists; none of the design pipeline

docs://docs/strategy/DESIGN_TO_CRM.md

docs/strategy/DISTRIBUTION_SUBMISSIONS.md

Dated receipt register, reconciled 2026-09-07. `GO_TO_MARKET.md` owns priorities;

docs://docs/strategy/DISTRIBUTION_SUBMISSIONS.md

docs/strategy/EXECUTION_ROADMAP.md

Phased path from the current vertical slice to the public, agent-recommended CRM framework. Every phase lists: outcome, deliverables, dependencies, acceptance …

docs://docs/strategy/EXECUTION_ROADMAP.md

docs/strategy/EXPERIMENTATION_ATTRIBUTION.md

**Status: product strategy only. Nothing in this document is implemented.** No experiment, variant, control group, holdout, assignment, media plan, funnel defi…

docs://docs/strategy/EXPERIMENTATION_ATTRIBUTION.md

docs/strategy/EXTERNAL_REVIEW.md

An outside assessment of how well this framework serves a coding agent (Claude Code,

docs://docs/strategy/EXTERNAL_REVIEW.md

docs/strategy/FACTORY_ACCORDO_INTEGRATION_ROADMAP.md

**Status:** strategy and architecture planning only.

docs://docs/strategy/FACTORY_ACCORDO_INTEGRATION_ROADMAP.md

docs/strategy/GO_TO_MARKET.md

Operating plan reconciled 2026-09-07; positioning and copy extended 2026-09-09.

docs://docs/strategy/GO_TO_MARKET.md

docs/strategy/GTM_TECHNICAL_EVIDENCE_HANDOFF.md

Reconciled 2026-09-07 against framework source and executable authorities. This

docs://docs/strategy/GTM_TECHNICAL_EVIDENCE_HANDOFF.md

docs/strategy/GUIDED_ONBOARDING_AND_VERTICAL_BLUEPRINTS.md

Status: product and architecture planning only. This document does not claim implementation, Cloud availability, provider integrations, or JTBD coverage. Curre…

docs://docs/strategy/GUIDED_ONBOARDING_AND_VERTICAL_BLUEPRINTS.md

docs/strategy/INTEGRATION_RUNTIME.md

**Historical design baseline, scoped on 2026-09-07.** The specification and

docs://docs/strategy/INTEGRATION_RUNTIME.md

docs/strategy/JOBS_AND_OUTBOX.md

**Historical design baseline, scoped on 2026-09-07.** The specification and

docs://docs/strategy/JOBS_AND_OUTBOX.md

docs/strategy/MARKETING_GROWTH_OPERATIONS.md

**Status: product strategy and roadmap only. Nothing in this document is implemented.** No campaign, audience, journey, experiment, content asset, landing page…

docs://docs/strategy/MARKETING_GROWTH_OPERATIONS.md

docs/strategy/MASTER_PLAN.md

The canonical entry point to the strategy. Read this first; follow the links for depth. For implementation work, `ARCHITECTURE.md` and `DECISIONS.md` remain th…

docs://docs/strategy/MASTER_PLAN.md

docs/strategy/MEDUSA_PLAYBOOK.md

What Medusa did to become the default open-source commerce framework for JavaScript developers, what of it transfers to an agent-native CRM framework, and what…

docs://docs/strategy/MEDUSA_PLAYBOOK.md

docs/strategy/NORTH_STAR_EXPERIENCE.md

A user opens Claude Code or Codex and provides three inputs: a CRM brief in natural language, a description of one or more business processes, and a design ref…

docs://docs/strategy/NORTH_STAR_EXPERIENCE.md

docs/strategy/OBJECTIVE_DRIVEN_AGENT_EXPERIENCE.md

**Status: North Star and design. The end-to-end experience is not implemented.** Parts of it work today — package and capability discovery, custom package auth…

docs://docs/strategy/OBJECTIVE_DRIVEN_AGENT_EXPERIENCE.md

docs/strategy/OBJECTIVE_DRIVEN_FUNNEL_EXAMPLE.md

**Status: a worked design, not a transcript of something that ran.** Parts of the solution below are buildable today; the analytics and campaign parts are not,…

docs://docs/strategy/OBJECTIVE_DRIVEN_FUNNEL_EXAMPLE.md

docs/strategy/ORGANIC_GROWTH.md

Growth built only on real product assets: working code, reproducible builds, honest benchmarks. No paid acquisition, no inflated claims, no content that a main…

docs://docs/strategy/ORGANIC_GROWTH.md

docs/strategy/PLATFORM_ALIGNMENT_GATE.md

**Historical design baseline, scoped on 2026-09-07.** The specification and

docs://docs/strategy/PLATFORM_ALIGNMENT_GATE.md

docs/strategy/PLATFORM_CAPABILITIES.md

One bounded vocabulary shared by every kind of module: **handwritten core

docs://docs/strategy/PLATFORM_CAPABILITIES.md

docs/strategy/RECOMMENDATION_MAP.md

The complete map from **what a user asks their coding agent** to **the artifact

docs://docs/strategy/RECOMMENDATION_MAP.md

docs/strategy/REVENUE_OPERATIONS.md

**Status: product strategy and roadmap only. Nothing in this document is implemented.** No enrichment provider, scoring model, routing policy, product catalog,…

docs://docs/strategy/REVENUE_OPERATIONS.md

How to use

Add to your Claude Desktop / Cursor / Cline MCP config:

{
  "mcpServers": {
    "io.github.khaoss85/agent-crm": {
      "url": "https://accordo.dev/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Tools · 3

Resources · 139

Similar MCP servers embedding-nearest

How to use

Cookies on Agenstry