A RAG-backed MCP server that grounds Composer, background agents, and BugBot in 10+ years of CT delivery IP — so Cursor ships correct Apex, LWC, and Flow from the first prompt.
Salesforce docs teach the platform; Cursor docs teach the IDE. Neither covers what delivery actually needs: vertical business knowledge, the customer’s own processes, industry best practices — or how to build it all with Cursor. ContextCT serves that layer on demand, inside the prompt.
LSC data models, perfeCT mapping rules, governor-limit patterns, migration playbooks — curated into one governed vector index. Agents call resolve-project, then get-knowledge returns relevance-ranked context.
Enterprise Salesforce evals fail on hallucinated Apex, not IDE features. Grounded agents produce code that compiles, deploys, and passes review — the difference between a stalled pilot and a team-wide rollout.
Standard MCP serves the IDE, cloud background agents, and CLI alike — published once through the Team MCP marketplace. No per-engineer setup, no knowledge drift.
Humans meter in seats, agents in API calls, and FDE packages onboard, run, and manage the instance on demand. Three prices, one-line quote — implementable today with Stripe and an order form.
Seat comparisons undersell it: ContextCT doesn’t displace license spend — it displaces implementation labor. Sell it as digital labor, billed in the currency Salesforce buyers already budget.