Skip to content

MCP usage limits: default the meter to remote#593

Merged
saleh-mir merged 1 commit into
masterfrom
feat/mcp-usage-meter-default-remote
Jun 25, 2026
Merged

MCP usage limits: default the meter to remote#593
saleh-mir merged 1 commit into
masterfrom
feat/mcp-usage-meter-default-remote

Conversation

@saleh-mir

Copy link
Copy Markdown
Member

Makes the server-authoritative meter the default (was local) so the daily limit is enforced by the backend with no env var — no client needs to add a setting. MCP_USAGE_METER=local remains as an opt-out. Fails open, so a backend outage never disrupts usage.

Tests: an autouse fixture forces local mode for the existing local-flow tests; added a default-is-remote check. All 26 pass (pytest tests/test_mcp_usage_limits.py -p no:anyio).

🤖 Generated with Claude Code

Make the server-authoritative backend the default (was "local") so the daily limit
is enforced by the licensing backend with no env var needed. "local" stays available
as an opt-out via MCP_USAGE_METER=local. Fails open, so a backend outage never
disrupts usage.

Tests: an autouse fixture forces local mode for the existing local-flow tests; add a
default-is-remote check. All 26 pass.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@saleh-mir saleh-mir merged commit fa933cf into master Jun 25, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant