docs(mcp-settings): clarify credit limit is rolling monthly not all-time

[george-dilthey]

What changed

Added two clarifications to docs/mcp-settings.md to explicitly answer the "rolling monthly or all time?" question about MCP user credit limits:

1. "Setting credit limits" section — added "automatically" to the reset sentence: "Credit spend automatically resets on the 1st of each month at midnight UTC."
2. "When do credits reset?" FAQ — updated the answer from a bare reset date to lead with the nature of the limit: "The MCP user credit limit is a rolling monthly limit. Credit spend automatically resets on the 1st of each month at midnight UTC."

Why

An Enterprise customer (Britnee Terrill at Komodo Health) asked: "Is the Default Credit Limit for MCP users a rolling monthly or all time?" — Fin couldn't answer and the ticket was escalated to a human support agent (Smit Vekaria), who confirmed it's rolling monthly with an automatic reset on the 1st of each month.

The existing doc described when credits reset but didn't explicitly state that the reset is automatic or call the limit "rolling monthly." This is a meaningful gap: Clay's workbook credit limits (a separate feature in docs/credit-spend-limits-faq.md) do NOT auto-reset, so customers comparing the two features could reasonably assume MCP limits also require manual resets. The clarification removes that ambiguity in the customer's vocabulary.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475021510884
• Slack trigger thread: https://clay-hq.slack.com/archives/C0A7UM0LNBZ/p1783618305331709
• Corroborating Slack (#ent-taboola-clay, June 3 2026): https://clay-hq.slack.com/archives/C09T58ZV2TT/p1780487483470899 — "Confirmed MCP credits reset monthly (unlike workbooks' one-time allocation) — a deliberate design"
• Verifier sub-agent returned PASS on all four claims. Code evidence: libs/shared/src/RunnerTypes.ts:150 (error label "You ran out of monthly credits 😢"), services/scheduler/src/bull/jobs/reset-sales-rep-credit-spend.ts:24 (monthly cron comment), services/scheduler/src/bull/jobs/init-billing-queue-job.ts:46 (cron '0 0 1 * *', timezone UTC).

Uncertainties

None. The claims are code-verified (PASS) and corroborated by multiple Slack threads and the human support agent reply.

Related observations

• PR docs(mcp-settings,credit-budgets): document per-user MCP spend tracking and Sequencer-MCP bundling #1525 is also open on docs/mcp-settings.md and adds a Budgets-tab note and a "Can I disable Clay Sequencer access for Sales Rep users?" FAQ. It does not touch the "When do credits reset?" FAQ or the rolling-monthly framing — the changes do not overlap. A reviewer should reconcile both PRs before merging.
• The "What happens when a rep hits their credit limit?" FAQ and the "Setting credit limits" section list "ChatGPT, Claude, or Glean" but omit Codex, which is a documented supported platform. Out of scope for this trigger but worth a follow-up.

Closes DOC-1107

[linear-code]

DOC-1107