docs(mcp-server): tier-aware lede + Plans & limits comparison table#3654
Merged
Conversation
Two improvements requested after PR #3646 landed in production: 1. Lede emphasises that BOTH Pro and API tiers can OAuth-sign-in (the prior copy implied OAuth was Pro-only). The functional difference between tiers is rate limits, not auth surface. 2. New "Plans & limits" table replacing the previous bullet list. One row per plan (Free / Pro / API Starter / API Business / Enterprise) with MCP access, auth modes, daily cap, per-minute cap, and notes. Highlights: - Free: no MCP (401 at OAuth) - Pro: 50 tool calls/UTC day (the only hard daily quota) - API Starter / Business / Enterprise: no daily cap, 60/min/key - Pro's 60/min is per-USER (shared across installs); API tiers' 60/min is per-KEY (multiple keys = higher throughput) Plus a clarifying paragraph on what doesn't count: `tools/list` and `initialize` are never charged against either limit. No code changes. MDX lint + markdown lint clean.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
Greptile SummaryThis docs-only PR refreshes
Confidence Score: 3/5The change is docs-only, but it introduces a direct numeric contradiction within the same page that users will notice. The new lede claims "36+ tools" while the Tool catalog heading four sections lower still reads "32 tools" — both numbers are on the same page and users will see the conflict immediately. Until one of those numbers is corrected the page actively misleads readers about the tool count. The Retry-After format discrepancy is a smaller concern but could trip up developers writing retry logic. docs/mcp-server.mdx — the tool-count contradiction between the new lede and the unchanged catalog heading needs to be resolved before publishing. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
Client([MCP Client]) --> OAuthFlow[OAuth 2.1 Flow]
OAuthFlow --> TierCheck{Tier?}
TierCheck -->|Free| Reject401[401 INSUFFICIENT_TIER]
TierCheck -->|Pro| ProQuota{Daily quota\n50 tool calls / UTC day}
TierCheck -->|API Starter / Business / Enterprise| APIQuota{Per-minute\n60 req/min/key}
ProQuota -->|Under limit| RateCheck{Per-minute\n60 req/min/user}
ProQuota -->|Over limit| Err429Pro[429 + JSON-RPC -32029\nRetry-After: UTC midnight]
RateCheck -->|OK| Tools[tools/call executed]
RateCheck -->|Throttled| Err429Rate[429 + Retry-After]
APIQuota -->|OK| Tools
APIQuota -->|Throttled| Err429Rate
Tools -->|tools/list or initialize| NoQuota[Never counted against quota]
Reviews (1): Last reviewed commit: "docs(mcp-server): tier-aware lede + Plan..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…, Enterprise unlimited Round-2 user feedback on PR #3654: my prior commit said "no daily cap" for API tiers, which is wrong. Marketed product policy is: - API Starter: 1,000 requests / day - API Business: 10,000 requests / day - Enterprise: unlimited These daily caps are advertised to customers but NOT yet enforced in code (per-minute caps are; daily caps are on the implementation backlog). Documenting the marketed numbers — internal reviewers can see the gap from grep'ing apiRateLimit consumers. Other adjustments: - Lede: "differ only in daily quotas" instead of "Pro is the only one with a daily cap" (no longer accurate). - "Daily limit (Pro tier)" callout: add a "Need a higher allowance?" pointer to API Starter/Business/Enterprise rather than the prior "API tiers have no daily cap" line. - Plans & limits table: collapsed Daily/Per-minute into a single Daily quota column (per-minute is uniform 60/min across paid tiers, called out separately below the table to avoid table noise).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improves the MCP Server docs following user-feedback after #3646 shipped:
Tier-aware lede. The previous `` callout said "gated behind PRO" — accurate but narrow. The reality is that both Pro and API tiers can use the OAuth flow (no API key required). The new copy makes that explicit and points readers at the comparison table.
New "Plans & limits" table replacing the previous bullet list. One row per plan covering MCP access, auth modes, daily cap, per-minute cap, and notes. Surfaces the actual contrast users care about:
Clarifying line that `tools/list` and `initialize` are never counted against either limit.
Why
User reported the docs didn't make Pro's lower daily quota visible relative to API Standard / Business / Enterprise. The previous wording required reading two paragraphs to compare tiers. A table is the right shape.
Test plan
No code changes. Docs-only.