-
Notifications
You must be signed in to change notification settings - Fork 373
Agents landing page #1728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agents landing page #1728
Conversation
|
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. |
|
Thanks a lot @merveenoyan , this will be a great addition! 😃 |
Co-authored-by: Aymeric Roucher <[email protected]>
Co-authored-by: Aymeric Roucher <[email protected]>
Co-authored-by: Aymeric Roucher <[email protected]>
Co-authored-by: Aymeric Roucher <[email protected]>
abidlabs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gradio parts looks great @merveenoyan added some suggestions
pcuenca
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with @abidlabs' suggestions
Co-authored-by: Abubakar Abid <[email protected]>
Co-authored-by: Abubakar Abid <[email protected]>
Co-authored-by: Pedro Cuenca <[email protected]>
Co-authored-by: Pedro Cuenca <[email protected]>
Co-authored-by: Pedro Cuenca <[email protected]>
Co-authored-by: Abubakar Abid <[email protected]>
Co-authored-by: Abubakar Abid <[email protected]>
Co-authored-by: Pedro Cuenca <[email protected]>
Vaibhavs10
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when finished it'll be cool to write about the Python client too.
docs/hub/agents.md
Outdated
|
|
||
| demo.launch(mcp_server=True) | ||
|
|
||
| The MCP server will be available at `http://your-server:port/gradio_api/mcp/sse` where your application is served. It will have a tool corresponding to each function in your Gradio app, with the tool description automatically generated from the docstrings of your functions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for the deployed space on the hub - it'd be hf.space domain right? - I wonder if we can make it more HF spaces as a MCP server centric.
https://www.gradio.app/guides/using-docs-mcp#installing-in-the-clients
cc: @abidlabs
Co-authored-by: Pedro Cuenca <[email protected]>
Co-authored-by: vb <[email protected]>
Co-authored-by: vb <[email protected]>
Co-authored-by: vb <[email protected]>
julien-c
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also cc @burtenshaw who's been working on a mcp-course from what i've seen (from random stalking😁)
docs/hub/_toctree.yml
Outdated
| - local: agents | ||
| title: Agents on Hub |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs/hub/agents.md
Outdated
| If you want to avoid defining agents yourself, the easiest way to start an agent is through the CLI, using the `smolagent` command. | ||
|
|
||
| ```python | ||
| smolagent "Plan a trip to Tokyo, Kyoto and Osaka between Mar 28 and Apr 7." --model-type "InferenceClientModel" --model-id "Qwen/Qwen2.5-Coder-32B-Instruct" --imports "pandas numpy" --tools "web_search" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we format it on multiple lines? see current rendering: https://moon-ci-docs.huggingface.co/docs/hub/pr_1728/en/agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry it was supposed to be bash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made a suggestion on above here: #1728 (comment)
Co-authored-by: Aymeric Roucher <[email protected]>
Co-authored-by: Julien Chaumond <[email protected]>
Co-authored-by: Julien Chaumond <[email protected]>
Vaibhavs10
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting to look nice and clean, some more suggestions for readability and more complete snippets
Co-authored-by: vb <[email protected]>
Co-authored-by: vb <[email protected]>
Co-authored-by: vb <[email protected]>
|
@Vaibhavs10 re-ordered from high level to low level, @aymeric-roucher is this ok? |
|
|
||
| This page compiles all the libraries and tools Hugging Face offers for agentic workflows: huggingface.js mcp-client, Gradio MCP Server and smolagents. | ||
|
|
||
| ## huggingface.js mcp-client |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit: would prefer putting smolagents above huggingface.js agents, since it has more usage and content.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to me it makes sense to make it high to low level, but I have no strong opinion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
smolagents seems more high level IMO, this part about huggingface.js sounds like a low level detail
WDYT @Vaibhavs10 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CLI yes, but other than that it's not I think there's more customization
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really see the logic in having "one MCP server of a package" listed above "one MCP server of a bigger package" (smolagents has more usage than the agentic part of huggingface.js): for me it would make sense for the bigger one to be listed first
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
personally don't think the order matter much, it's just three options anyway, IMHO having more hub related things up front makes wee bit more sense - we can always change the order later on if it doesn't make sense.
Vaibhavs10
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 smol suggestions, otherwise good to ship!
| You can get more information about mcp-client [here](https://huggingface.co/docs/huggingface.js/en/mcp-client/README). | ||
|
|
||
|
|
||
| ## Gradio MCP Server / Tools |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small suggestion, it'd be nice to add a snippet of MCP via a space.
docs/hub/agents.md
Outdated
| } | ||
| ``` | ||
|
|
||
| This is very powerful because it lets the LLM use any Gradio application as a tool. You can find thousands of them on [Spaces](https://huggingface.co/spaces). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can link some docs for people to read more: https://www.gradio.app/guides/building-mcp-server-with-gradio
|
|
||
| This page compiles all the libraries and tools Hugging Face offers for agentic workflows: huggingface.js mcp-client, Gradio MCP Server and smolagents. | ||
|
|
||
| ## huggingface.js mcp-client |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
personally don't think the order matter much, it's just three options anyway, IMHO having more hub related things up front makes wee bit more sense - we can always change the order later on if it doesn't make sense.

compiling everything agents and MCP clients, please let me know if I miss something! @aymeric-roucher @abidlabs @julien-c