Connect Claude Code to tools via MCP changedmcp
Nearest release: v2.1.251, published 7 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−5removed
From line
398
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits86to this page, all time
The whole hunk
from line 398, old and new numbered
/
from line 398
398398 * Use `/mcp` to authenticate with remote servers that require OAuth 2.0 authentication
399399</Tip>
400400
401The per-server `timeout` is a hard wall-clock limit per tool call, and progress notifications from the server don't extend it. Values below 1000 are ignored and fall through to `MCP_TOOL_TIMEOUT`, or to its default of about 28 hours when that variable is unset. For an HTTP, SSE, or [claude.ai connector](/docs/en/mcp#use-mcp-servers-from-claude-ai) server there is also a second, per-request timer that covers each request through to the server's first response byte. That timer is 60 seconds unless you set the per-server `timeout` or `MCP_TOOL_TIMEOUT`; setting either to 60 seconds or higher raises the per-request timer to that value, a lower value doesn't shorten it, and the 28-hour default of an unset `MCP_TOOL_TIMEOUT` never feeds it. Stdio and WebSocket servers have no per-request timer. Before v2.1.162, values below 1000 were floored to one second instead.
401The per-server `timeout` is a hard wall-clock limit per tool call, and progress notifications from the server don't extend it. Values below 1000 are ignored and fall through to `MCP_TOOL_TIMEOUT`, or to its default of about 28 hours when that variable is unset. For an HTTP, SSE, or [claude.ai connector](/docs/en/mcp#use-mcp-servers-from-claude-ai) server there is also a second, per-request timer that covers each request through to the server's first response byte. Claude Code sets that timer to the greatest of three values: 60 seconds, the tool timeout that applies to the server, and `MCP_TIMEOUT`. The 28-hour default of an unset `MCP_TOOL_TIMEOUT` doesn't enter that comparison, and a value below 60 seconds doesn't shorten the timer. Stdio and WebSocket servers have no per-request timer. Before v2.1.162, values below 1000 were floored to one second instead.
402402
403403A per-server `timeout` of at least 1000 also acts as a floor on the idle timeout described below: Claude Code never aborts that server's tool calls for idleness sooner than the per-server `timeout`. Requires Claude Code v2.1.203 or later.
404404
from line 1436
14361436
14371437<Steps>
14381438 <Step title="Discover available prompts">
1439 Type `/` to see the commands available to you, including those from MCP servers. MCP prompts appear with the format `/mcp__servername__promptname`.
1439 Type `/` to see the commands available to you, including those from MCP servers. Claude Code lists each MCP prompt as `/servername:promptname (MCP)`. Typing `/mcp__servername__promptname` also runs it.
14401440 </Step>
14411441
14421442 <Step title="Execute a prompt without arguments">
from line 1446
14461446 </Step>
14471447
14481448 <Step title="Execute a prompt with arguments">
1449 Many prompts accept arguments. Pass them space-separated after the command:
1449 Many prompts accept arguments. Pass them space-separated after the command. Claude Code splits the arguments on whitespace, so each argument is a single token:
14501450
14511451 ```text wrap theme={null}
14521452 /mcp__github__pr_review 456
from line 1453
14531453 ```
14541454
14551455 ```text wrap theme={null}
1456 /mcp__jira__create_issue "Bug in login flow" high
1456 /mcp__jira__create_issue login-bug high
14571457 ```
14581458 </Step>
14591459</Steps>
from line 1464
14641464 * MCP prompts are dynamically discovered from connected servers
14651465 * Arguments are parsed based on the prompt's defined parameters
14661466 * Prompt results are injected directly into the conversation
1467 * Server and prompt names are normalized, with spaces converted to underscores
1467 * In the `/mcp__servername__promptname` form, Claude Code replaces any character in the server name outside `A-Z`, `a-z`, `0-9`, `_`, and `-` with `_`, and uses the prompt name as the server declares it
14681468</Tip>
14691469
14701470## Managed MCP configuration
No line in this hunk matches that.