Quotes -- Connecting Context - Exploring Future Transports

Short excerpts selected from the transcript for grounding answers. Preserve transcript artifacts when quoting.

MCP transports

and then we also of course have a new a new way of connecting to remote servers with uh with the stateless HTTP um transport. So let's kind of start to dive into to some of those changes.

Source: L0369-L0373

Remote MCP servers

do with inference, um, and how you're designing the context window, sometimes actually directly wrapping an API is absolutely the right thing to do and other times, of course, it's absolutely

Source: L0646-L0650

Streamable HTTP

uh Alan kindly introduced, I work at Hugging Face on open-source connectivity and MCP and agents initiatives. um also look after one of the maintainers of our skills repository and a a tool we have

Source: L0008-L0012

Stateless protocol design

together to to kind of modify um the context of the of what you were using. Okay, so MCP clients can obviously use tools and prompts and so on. And the idea being that MCP servers could also

Source: L0089-L0093

Hugging Face MCP adoption

description of what it's seen. Um this is a good example of why context engineering matters because you don't particularly don't necessarily want um uh the AI's view of you.

Source: L0423-L0427

Context connectivity

then is we'll talk about how we've adopted MCP at hugging face in our public facing product. Um we'll look at some kind of analytics and details of how um clients connect to our uh MCP

Source: L0033-L0037

MCP transports

Slightly unusually for a lot of MCP servers, we also have um we allow both authenticated and anonymous access, right? So it's actually kind of like a very very um good and easy

Source: L0058-L0062

Remote MCP servers

complicated and so ultimately a better design to use oorth as the resource server was then introduced um and that's kind of where we um where we kicked off. So at launch time for us about 12 months

Source: L0117-L0121