Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
simone-bennett wants to merge 1 commit into from
Closed

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions pages/apis/mcp_server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ To start using Buildkite's MCP server, first determine which [type of Buildkite

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.

@buildsworth-bk-app buildsworth-bk-app Bot Jul 1, 2026

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.


## Types of MCP servers

Buildkite provides both a [remote](#types-of-mcp-servers-remote-mcp-server) and [local](#types-of-mcp-servers-local-mcp-server) MCP server, both of which provide access to its [MCP server tools](/docs/apis/mcp-server/tools#available-mcp-tools). The remote MCP server supports OAuth authentication for interactive AI tools and [API token pass-through](#api-token-pass-through-remote-mcp-server) for headless agents.
Expand Down