1. Mercury-specific speedups (BOSSTORQUE)
| Build | Current pain | Optimization | Path | Time saved |
|---|---|---|---|---|
| Monthly close / P&L | Manual export, sort, classify in Quicken | Scheduled Cowork task pulls last 30d txns via Mercury MCP, AI-categorizes, drops HTML P&L in outputs | MCP read | ~2 hrs/mo |
| Cash-flow watch | Check balances by hand, no upcoming-AP visibility | Daily scheduled pull of balances + pending Send Money requests; Dispatch ping if balance < threshold | MCP read | ~30 min/wk + miss-prevention |
| Invoice send | Build invoice in UI, copy to email, send | Generate from project notes, push via Mercury CLI (mercury invoices create), Dispatch-gated send | CLI write | 20–30 min/invoice |
| Receipt attach | Manual upload one-by-one | Forward receipts to inbox → Gmail MCP fetches → match by amount/date → CLI upload | CLI write | ~1 hr/mo |
| Vendor payment | Quicken bill pay or manual transfer | Cowork drafts the Send Money request; you approve in Mercury UI (CLI can stage, never auto-execute) | CLI + Jason approves | ~10 min/payment |
| Quarterly tax estimate | Pull P&L from books, compute by hand | Cowork pulls 90d txns + categories, runs estimate via tax skill, HTML deliverable | MCP read | ~1 hr/qtr |
2. Pattern speedups (apply to every client build)
The Mercury announcement is one instance of a broader pattern: vendor-shipped MCPs and CLIs collapse the build cost of integrations from days to hours. The optimizations below are reusable across BOSSTORQUE deliverables, not just Mercury.
1. Read-MCP-first, write-via-CLI escalation
For any vendor that ships both: use the MCP for autopilot read flows, route writes through CLI gated by Dispatch confirmation. Same pattern for Jobber, ServiceTitan, QuickBooks, ConvertKit, Apollo. Lock the standard, copy-paste across clients.
2. CLI install once, reuse forever
Cowork's bash sandbox can run any CLI. Maintain a setup.sh per client/project that curl|sh's required CLIs on first session boot. Mercury, gh, wrangler, supabase, stripe — same pattern.
3. OAuth 2.0 dynamic client reg
Mercury supports it. So do most modern vendors now. For client deliverables that need persistent automated access, register a BOSSTORQUE-named OAuth client per vendor — beats raw API keys, professional in audit trails, survives password changes.
4. Doc-digest subagent pattern
Vendor docs often blow past context limits (this Mercury MCP doc was 102K chars). Standard play: dispatch a Haiku subagent to fetch + summarize, return the 5 facts that matter. Cuts main-context burn ~80% per vendor onboarding.
5. Scheduled task = recurring deliverable
Anything you'd otherwise do manually each month (close, status report, cash-flow check, client digest) becomes a scheduled task. MCP read-only flows are the safest first candidates — no write blast radius.
6. New-connector intake checklist
Standard 30-min playbook when any vendor MCP/CLI lands: (1) test auth, (2) enumerate read scopes, (3) enumerate write scopes, (4) note rate limits, (5) update memory glossary, (6) flag which existing builds it accelerates. Treat each new MCP as a build-cost reduction event.
3. Standards locked in
| Standard | Rule |
|---|---|
| Mercury MCP scope | Read-only. Use freely on autopilot — accounts, balances, transactions, invoices, recipients, treasury, statements, send-money approval requests. |
| Mercury CLI | Write actions live here. Install once on Mac via curl -sSf https://cli.mercury.com/install.sh | sh. Cowork invokes via Desktop Commander. |
| Money movement | CLI can stage Send Money requests. Never auto-execute. Always Dispatch + Jason confirms in Mercury UI. Aligns with global "no trades / no transfers" rule. |
| Categorization, invoice draft, receipt upload | Low-risk writes. Dispatch the summary of what was done, not a pre-approval gate. Drafts are reversible. |
| OAuth client registration | Name BOSSTORQUE clients Mercury MCP for BOSSTORQUE per Mercury's convention. Token storage: 1Password, never repo. |
| Sandbox vs prod | Default all new write-flow development to sandbox; promote only after Jason signs off. |
4. Action items (ranked by ROI)
- Install Mercury CLI on Mac (you, ~30 sec). Run
curl -sSf https://cli.mercury.com/install.sh | sh. Unlocks every write-side optimization. unblocks 4 builds - Stand up the monthly-close scheduled task. Mercury MCP read → AI categorization → HTML P&L. ~2 hrs/mo recovered, no write-side risk.
- Add
mercury.mdto memory + hot cache. Locks in the read/write split so we don't relitigate it every session. - Build the cash-flow watch task. Daily balance pull, low-balance Dispatch alert. Costs nothing, prevents missed AP.
- Roll the "new-connector intake checklist" into
connectors.md. Pays back the next time any vendor ships an MCP — which is now monthly. - Decide on BOSSTORQUE-owned OAuth client. Worth doing if we plan to ship Mercury-integrated client deliverables. Skip if internal only.
- Pin a CLI version. Repo lives on
nextbranch — pin to a tagged release once stable, don't track HEAD in production scheduled tasks.
5. Link audit (the email itself)
| Link | What it is | Action |
|---|---|---|
docs.mercury.com/docs/connecting-mercury-mcp | Hosted MCP setup, OAuth dynamic client reg, scope notes | Read once, reference. Already extracted key facts. |
github.com/MercuryTechnologies/mercury-cli | CLI source + install. README on next branch. | Install when convenient. Pin version when stable. |
docs.mercury.com/docs/welcome | General API/dev docs | Reference only. No new info beyond MCP doc. |
mercury.com/api | Marketing landing for the dev suite | Skip. Marketing. |
| Track/customer.io unsubscribe + social | Marketing telemetry | Ignore. |