|
354 | 354 | "\n", |
355 | 355 | "We'll provide a short fragment of its sequence so the notebook runs quickly. In a real workflow, you'd paste the full sequence from UniProt.\n", |
356 | 356 | "\n", |
357 | | - "Let's use a truncated fragment of human EGFR (from UniProt P00533). In practice, use the full sequence from https://www.uniprot.org/uniprot/P00533\n" |
| 357 | + "In this example let's use a truncated fragment of human EGFR (from UniProt P00533). You can find the full sequence from https://www.uniprot.org/uniprot/P00533\n" |
358 | 358 | ] |
359 | 359 | }, |
360 | 360 | { |
|
401 | 401 | "\n", |
402 | 402 | "Note that you can use the RAG pipeline we learned in section 2.2 as a tool here to extract literature data." |
403 | 403 | ] |
404 | | - }, |
405 | | - { |
406 | | - "cell_type": "markdown", |
407 | | - "id": "41499148", |
408 | | - "metadata": {}, |
409 | | - "source": [ |
410 | | - "## 3.2.7 Standard approaches to deploying agents \n", |
411 | | - "\n", |
412 | | - "Anthtopic has released a open-source protocol known as Model Context Protocol (MCP) to standardize the these practices. Read more [here](https://www.anthropic.com/news/model-context-protocol).\n", |
413 | | - "\n", |
414 | | - "Imagine you want your AI agent to use 20 different tools such as search PubMed, query UniProt, read files, run BLAST, write to a database. If you used the notebook approach, you'd have to manually write and wire up all 20 functions yourself, in every project, every time.\n", |
415 | | - "Instead MCP introduces a plug-and-play architecture with two distinct roles:\n", |
416 | | - "\n", |
417 | | - "**MCP Server**\n", |
418 | | - "\n", |
419 | | - "- A standalone program that owns and exposes tools. For example: a \"UniProt MCP Server\" that knows how to fetch protein data from UniProt's API\n", |
420 | | - "- It advertises what tools it has, what inputs they take, and runs them when asked\n", |
421 | | - "- Anyone can build one, and they can be shared and reused across projects\n", |
422 | | - "\n", |
423 | | - "**MCP Client**\n", |
424 | | - "\n", |
425 | | - "- The AI agent (or the app hosting it) that connects to one or more servers\n", |
426 | | - "- It discovers what tools are available, and calls them when the model decides to\n", |
427 | | - "- Claude.ai, for example, acts as an MCP client when you connect it to Google Drive or Slack\n", |
428 | | - "\n", |
429 | | - "\n", |
430 | | - "\n", |
431 | | - "The relationship looks like this:\n", |
432 | | - "\n", |
433 | | - "```\n", |
434 | | - "[ Your AI Agent / Claude ] ← MCP Client\n", |
435 | | - " │\n", |
436 | | - " │ \"What tools do you have?\"\n", |
437 | | - " ▼\n", |
438 | | - "[ UniProt MCP Server ] ──→ tool: fetch_protein()\n", |
439 | | - "[ PubMed MCP Server ] ──→ tool: search_papers()\n", |
440 | | - "[ BLAST MCP Server ] ──→ tool: run_alignment()\n", |
441 | | - "```\n", |
442 | | - "\n", |
443 | | - "You can see a more detailed explanation and an implementation in chapter 3.4. In the meantime you can read more about MCP here:\n", |
444 | | - "\n", |
445 | | - "- [what is an MCP?](https://www.youtube.com/watch?v=eur8dUO9mvE)\n", |
446 | | - "- [MCP vs API](https://www.youtube.com/watch?v=7j1t3UZA1TY)\n", |
447 | | - "- [Concepts of MCP](https://modelcontextprotocol.io/docs/learn/architecture)" |
448 | | - ] |
449 | 404 | } |
450 | 405 | ], |
451 | 406 | "metadata": { |
|
0 commit comments