@ontoboom/crm
Account-based B2B CRM: companies, contacts, deals, pipeline stages, activities, and ownership. Designed as the canonical schema for agents that need to reason over a sales pipeline without per-tenant guessing.
Connect this ontology
● Checking…https://mcp.ontoboom.com/o/@ontoboom/crm@0.1.0{
"mcpServers": {
"ontoboom": {
"url": "https://mcp.ontoboom.com/o/@ontoboom/crm@0.1.0",
"transport": "sse"
}
}
}Two manifest-derived tools are exposed in this iteration:list_entities anddescribe_entity. More tools (find_relationship, enumerate_values) ship as followups.
README
@ontoboom/crm
A B2B CRM ontology covering the account → contact → opportunity → close loop.
Why this exists
Most CRM SaaS products ship overlapping but incompatible schemas. Agents that hop between them either hallucinate field names or require per-vendor adapters. This pack gives you one canonical model that downstream tools can map into.
Coverage
- Account (Company) — the legal entity you're selling to.
- Contact — individual at the Account.
- Lead — pre-qualified Contact with a stated interest.
- Opportunity / Deal — open or closed sales motion against an Account.
- PipelineStage — ordered stage in your sales pipeline.
- Activity — touchpoint (email, call, meeting, note) linked to one or more Contact / Account / Opportunity.
- Owner — the rep responsible for an Account or Opportunity.
- Industry, CompanySize, DealSource — enumerated dimensions used for routing, scoring, and reporting.
SHACL constraints worth knowing
- An Opportunity requires
stage,amount(>= 0),closeDate, and a single owner. - A Contact requires an email matching a basic regex; phone numbers are optional but format-checked.
Account.industryis constrained to a list of high-level NAICS-style buckets so cross-vendor mapping is easier.
Forking
Fork this pack and customize before publishing under your own namespace —
particularly the Industry enumeration if your business is sector-specific.
Reviews
Sign in to reviewNo reviews yet · Be the first to review.