High-level view
Nothing in this diagram runs as a multi-tenant SaaS. The rep's laptop (or their Cloud project) holds credentials and indices; Claude calls tools over MCP when a session is active.
DCOS is a field-deployable stack: Claude Desktop orchestrates local MCP servers that read CRM truth, search account memory, and research the web — then persona instructions shape the output.
Nothing in this diagram runs as a multi-tenant SaaS. The rep's laptop (or their Cloud project) holds credentials and indices; Claude calls tools over MCP when a session is active.
Chat UI, Cowork tasks, and scheduled Routines. Loads local .mcpb extensions for DCOS and Jina.
13+ tools: Salesforce queries, ES search, note indexing, connector calls, index setup. Runs in-process via bundled Node.
Web search and URL extraction for news, earnings, competitive signals — woven into account prep and briefs.
Account memory: notes, synced opps, activities, signals. Full-text search powers delta comparison across briefs.
System of record. Browser SSO via sf CLI — live SOQL at brief time plus optional background sync to ES.
Pluggable internal tools in connectors.yaml — Slack, Elastic KB, support APIs — via dcos_connector_call.
dcos_user_profile returns persona (AVP, AE, …) and account watchlist from ~/.config/dcos/.dcos_sfdc_sync pulls opportunity changes into dcos_opportunities.dcos_search across notes, prior briefs, activities, and signals per account.parallel_search_web for trigger events, leadership changes, competitive news.dcos_add_note saves findings so tomorrow's brief can diff against today.| Index | Contents |
|---|---|
dcos_notes |
MEDDPIC notes, brief findings, rep commentary — primary memory for search |
dcos_opportunities |
Salesforce opportunities synced for full-text search and territory rollups |
dcos_activities |
Tasks, events, and activity history linked to accounts |
dcos_signals |
External and internal signals (news hooks, health indicators, expansion cues) |
One install, multiple lenses. Profile + prompt choose how Claude prioritizes and formats output:
| Persona | Primary output |
|---|---|
| AVP / Leader | Territory pulse, rep handoffs, MEDDPIC heat map, leadership talking points |
| Account Executive | Deal scorecard, discovery questions, talk track, next action per opp |
| SDR | Trigger events, ICP fit, outbound hooks — pre-qualify I, M, C only |
| Solution Architect | Decision criteria matrix, PoC plan, architecture talking points |
| Customer Architect | Customer health, expansion plays, advocacy opportunities |
In Cursor, persona subagents can run in parallel for AVP rollups. In Claude Desktop, project instructions and prompt templates provide the same routing.
127.0.0.1:9200; API key written to ~/.config/dcos/env.sh.mcpb filesELASTICSEARCH_URL and ELASTICSEARCH_API_KEY in env.sh
Background sfdc-sync on a timer keeps ES fresh without Claude running.
Scheduled Claude Routines read deltas on a cadence — see
Always-on account agent.
| Secret | Where it lives |
|---|---|
| Elasticsearch API key | ~/.config/dcos/env.sh — seeded by installer, read by MCP at runtime |
| Salesforce session | Salesforce CLI auth store — browser SSO, not pasted into Claude UI |
| Jina API key | env.sh — prompted during install; used by Jina MCP extension |
| Connector tokens | connectors.yaml — optional, per-connector configuration |
MCP extensions run locally in Claude's UtilityProcess. CRM and ES calls never route through a DCOS-hosted cloud API.
DCOS trades platform breadth for sales depth: native Salesforce, MEDDPIC coaching, Elasticsearch you control, and field-first installers. Generic AI platforms optimize for many departments and centralized IT — different job, different architecture.
More questions? See Q&A or the leadership brief in the source repo
(docs/LEADERSHIP-BUILD-VS-BUY.md).