Skip to content

Conversation

@burtenshaw
Copy link
Collaborator

@burtenshaw burtenshaw commented May 8, 2025

This is the content for the first release of the mcp course.

Proposed Course Structure

  • (here) Unit 0 - practical
  • (here) Unit 1 - Fundamentals
  • (here) Unit 2 - Gradio use case
  • Unit 3 - Custom use case | Deep technical dive
  • Unit 4 - Bonus units by Partners

Units 3 and 4 will be based on community engagement. IMO, if the community is really excited, we could expand unit 3 and go deeper into MCP. Likewise, we could encourage partners to make more content in bonus units.

Reviewing

This is a rough and early draft but I want to get it out quick.

  • Feel free to recommend adding/removing pages or sections.
  • Could add short videos easily
  • Could add more diagrams
  • Could make more demos

PREVIEW

Copy link
Member

@Vaibhavs10 Vaibhavs10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few suggestions on increasing the readability and some videos to put the point through

@burtenshaw burtenshaw changed the base branch from basic-structure to main May 12, 2025 10:51
@HuggingFaceDocBuilderDev
Copy link
Collaborator

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@burtenshaw
Copy link
Collaborator Author

@yvrjsharma I noticed that you implemented Gradio as an MCP client here and wondered if you wanted to review and/or re-use the implementation from this PR in units/en/unit2/gradio-client.mdx.

@yvrjsharma
Copy link
Member

@yvrjsharma I noticed that you implemented Gradio as an MCP client here and wondered if you wanted to review and/or re-use the implementation from this PR in units/en/unit2/gradio-client.mdx.

Thanks for the pointers, @burtenshaw! While I don't have strong feelings on this, I believe my implementation is more general, whereas the one in the PR at units/en/unit2/gradio-client.mdx focuses specifically on smolagents. I would prefer to maintain the generic option and can reference this implementation in my course for those who are interested. However, as I mentioned, my opinions on this aren't very strong, so I will defer to @abidlabs for his perspective.

@abidlabs
Copy link
Member

Personally, I prefer the neatness of the smolagents MCP Client, as implementing it entirely in Python with Gradio is quite complicated and I feel like is not the main message. Since readers of the course will already be familiar with smolagents, good to reuse this imo!

@burtenshaw
Copy link
Collaborator Author

Thanks for taking a look @abidlabs and @yvrjsharma! Personally, I don't think the raw python example is bad in an MCP context but it's definitely educations, it's just a stretch for the agents course. I would suggest this:

Agents-course: Gradio unit : re-use the smolagents example from this PR
MCP course : include both the smolagents and raw python example.

@yvrjsharma
Copy link
Member

Thanks @abidlabs, @burtenshaw, this approach sounds good to me too!

Agents-course: Gradio unit : re-use the smolagents example from this PR
MCP course : include both the smolagents and raw python example.

@burtenshaw burtenshaw merged commit 7b4813b into main May 15, 2025
1 check passed
Guiraud pushed a commit to Guiraud/mcp-course that referenced this pull request May 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants