タイムラインに戻る

5 ファイル変更 +346 -4

この更新の概要

Model Context Protocol (MCP) の導入を支援するクイックスタートガイドが新設され、初心者向けのステップバイステップの解説が拡充されました。MCPサーバーの接続時にツール定義を遅延ロードする仕組みに、サーバーの指示文も含まれるよう仕様の説明が修正されています。保存済みワークフローにおいてargsパラメータを通じて外部から入力を渡す機能が追加され、スクリプト内での動的なデータ利用が可能になりました。プラグインのリファレンスからはシャットダウンタイムアウトなどの一部の設定項目が削除されています。

mcp-quickstart +330 -0

初めてMCPサーバーを接続するユーザー向けに、環境構築から実行までを網羅した詳細なガイドが新規追加されました。

(差分が大きいため省略しています)
mcp +3 -1

クイックスタートへのリンクが追加されたほか、コンテキスト消費を抑える仕組みにおいてサーバーの指示文も遅延ロードの対象であることが明記されました。

@@ -11,6 +11,8 @@ Claude Code can connect to hundreds of external tools and data sources through t
Connect a server when you find yourself copying data into chat from another tool, like an issue tracker or a monitoring dashboard. Once connected, Claude can read and act on that system directly instead of working from what you paste.
If you're connecting your first server, start with the [MCP quickstart](/en/mcp-quickstart) for a step-by-step walkthrough. This page is the full reference.
## What you can do with MCP
With MCP servers connected, you can ask Claude Code to:
@@ -850,7 +852,7 @@ Tips:
## Scale with MCP Tool Search
Tool search keeps MCP context usage low by deferring tool definitions until Claude needs them. Only tool names load at session start, so adding more MCP servers has minimal impact on your context window.
Tool search keeps MCP context usage low by deferring tool definitions until Claude needs them. Only tool names and server instructions load at session start, so adding more MCP servers has minimal impact on your context window.
### How it works
overview +1 -1

MCPの概要説明において、最初のサーバー接続をエンドツーエンドでサポートするクイックスタートガイドへの参照が追加されました。

@@ -123,7 +123,7 @@ claude "commit my changes with a descriptive message"
In CI, you can automate code review and issue triage with [GitHub Actions](/en/github-actions) or [GitLab CI/CD](/en/gitlab-ci-cd).
The [Model Context Protocol (MCP)](/en/mcp) is an open standard for connecting AI tools to external data sources. With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling.
The [Model Context Protocol (MCP)](/en/mcp) is an open standard for connecting AI tools to external data sources. With MCP, Claude Code can read your design docs in Google Drive, update tickets in Jira, pull data from Slack, or use your own custom tooling. The [MCP quickstart](/en/mcp-quickstart) connects your first server end to end.
[`CLAUDE.md`](/en/memory) is a markdown file you add to your project root that Claude Code reads at the start of every session. Use it to set coding standards, architecture decisions, preferred libraries, and review checklists. Claude also builds [auto memory](/en/memory#auto-memory) as it works, saving learnings like build commands and debugging insights across sessions without you writing anything.
plugins-reference +0 -2

プラグイン設定のリファレンスから、強制終了までの待機時間とクラッシュ時の再起動に関する項目が削除されました。

@@ -249,8 +249,6 @@ LSP integration provides:
| `settings` | Settings passed via `workspace/didChangeConfiguration` |
| `workspaceFolder` | Workspace folder path for the server |
| `startupTimeout` | Max time to wait for server startup (milliseconds) |
| `shutdownTimeout` | Max time to wait for graceful shutdown (milliseconds) |
| `restartOnCrash` | Whether to automatically restart the server if it crashes |
| `maxRestarts` | Maximum number of restart attempts before giving up |
**You must install the language server binary separately.** LSP plugins configure how Claude Code connects to a language server, but they don't include the server itself. If you see `Executable not found in $PATH` in the `/plugin` Errors tab, install the required binary for your language.
workflows +12 -0

保存されたワークフローに対して、実行時に引数を渡してスクリプト内でargsオブジェクトとして利用する方法が追加されました。

@@ -169,6 +169,18 @@ Press Enter to save. The workflow runs as `/<name>` in future sessions from eith
If a project workflow and a personal workflow share a name, the project one runs.
### Pass input to a saved workflow
A saved workflow can accept input through the `args` parameter. The script reads it as a global named `args`. Use this to supply a research question, a list of target paths, or a configuration object at invocation time instead of editing the script for each run.
The following prompt runs a saved workflow with a list of issue numbers:
```text
> Run /triage-issues on issues 1024, 1025, and 1030
```
Claude passes the list as structured data, so the script can call array and object methods on `args` directly without parsing it first. If `args` is omitted, the global is `undefined` inside the script.
## How a workflow runs
The workflow runtime executes the script in an isolated environment, separate from your conversation. Intermediate results stay in script variables instead of landing in Claude's context.