Skip to content

docs: note that MCP has its own rate limit on the overview page#3130

Closed
simone-bennett wants to merge 1 commit into
mainfrom
docs-mcp-separate-rate-limit
Closed

docs: note that MCP has its own rate limit on the overview page#3130
simone-bennett wants to merge 1 commit into
mainfrom
docs-mcp-separate-rate-limit

Conversation

@simone-bennett

@simone-bennett simone-bennett commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Customer feedback surfaced that the MCP-specific rate limit is easy to miss. It is already documented at /docs/platform/limits but is not surfaced on the MCP server overview page. This adds one line pointing at the limits page so it is easier to find.

@simone-bennett simone-bennett requested a review from a team as a code owner July 1, 2026 04:14
@github-actions github-actions Bot added the api label Jul 1, 2026
@buildsworth-bk-app

Copy link
Copy Markdown
Contributor

On it! Follow along with my review here: https://buildkite.com/buildkite/buildsworth-review-pull-request/builds/2034

@buildkite-systems

Copy link
Copy Markdown

@buildsworth-bk-app buildsworth-bk-app Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One blocking docs accuracy issue inline. The new overview note needs to be scoped to the remote MCP server so it doesn't contradict the local MCP server rate-limit guidance on the same page.

Want to dig deeper? The full session log is attached to this Buildkite build. Download the session file and open a new pi session with it:

Download the buildsworth logs from build 2034, then answer my questions about the findings.

Comment thread pages/apis/mcp_server.md

Once you have established which Buildkite MCP server to use (remote or local) and if local, have [installed the MCP server](/docs/apis/mcp-server/local/installing#install-and-run-the-server-locally) and [configured its API access token](/docs/apis/mcp-server/local/installing#configure-an-api-access-token), you can then proceed to configure your AI tools to work with the [remote](/docs/apis/mcp-server/remote/configuring-ai-tools) (recommended) or [local](/docs/apis/mcp-server/local/configuring-ai-tools) MCP server.

Note: MCP requests count against a separate rate limit from your org's REST API budget. See [[platform limits](https://buildkite.com/docs/platform/limits)](https://buildkite.com/docs/platform/limits) for the specific numbers.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: This needs to be scoped to the remote MCP server. The local MCP server section below says local requests count toward the standard REST API rate limit, so as written this tells local MCP users the opposite. The suggestion also fixes the nested Markdown link and uses a docs-relative internal URL.

Suggested change
Note: MCP requests count against a separate rate limit from your org's REST API budget. See [[platform limits](https://buildkite.com/docs/platform/limits)](https://buildkite.com/docs/platform/limits) for the specific numbers.
> 📘 Remote MCP server rate limits
> Requests made through the remote Buildkite MCP server use a separate per-user rate limit from your Buildkite organization's REST API rate limit. See [platform limits](/docs/platform/limits) for the specific numbers.

@simone-bennett simone-bennett deleted the docs-mcp-separate-rate-limit branch July 1, 2026 04:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants