Build an MCP client changeddocs/draft/develop/build-client
Nearest release: v2.1.227, published 18 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 10 Aug 2026 02:40 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−4removed
From line
4
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55In this tutorial, you'll learn how to build an LLM-powered chatbot client that connects to MCP servers.
66
7Before you begin, it helps to have gone through our [Build an MCP Server](/docs/draft/develop/build-server) tutorial so you can understand how clients and servers communicate.
7Before you begin, it helps to have gone through our [Build an MCP Server](/docs/draft/develop/build-server.md) tutorial so you can understand how clients and servers communicate.
88
99**Python**
1010
from line 371
371371 * Be cautious with tool permissions
372372
3733734. **Tool Names**
374 * Tool names can be validated according to the format specified [here](/specification/draft/server/tools#tool-names)
374 * Tool names can be validated according to the format specified [here](/specification/draft/server/tools.md#tool-names)
375375 * If a tool name conforms to the specified format, it should not fail validation by an MCP client
376376
377377## Troubleshooting
from line 1981
19811981 * Be cautious with tool permissions
19821982
198319834. **Tool Names**
1984 * Tool names can be validated according to the format specified [here](/specification/draft/server/tools#tool-names)
1984 * Tool names can be validated according to the format specified [here](/specification/draft/server/tools.md#tool-names)
19851985 * If a tool name conforms to the specified format, it should not fail validation by an MCP client
19861986
19871987## Troubleshooting
from line 2497
24972497
24982498## Next steps
24992499
2500> **[Example servers](/examples)**
2500> **[Example servers](/examples.md)**
25012501>
25022502> Check out our gallery of official MCP servers and implementations
25032503
No line in this hunk matches that.