OpenAI adds MCP support to Agents SDK • Hacker News Board

Re: OpenAI adds MCP support to Agents SDK

#211

Post by otabdeveloper4 » Thu, Mar 27, 2025, 11:16 AM UTC

greyman wrote: post #203

otabdeveloper4 wrote: post #183

Earlier quoted context omitted.

> MCP is now the industry standard for connecting LLMs to external tools. No it isn't. We're still five or ten years away from real standards. (Anyways it's clear that the future is smaller self-hosted LLMs, so whatever standard eventually emerges will be based on that paradigm.)

1) It isn't a standard yet, but what else apart from filesystem-mcp can be used for prompts like "write me README.md for this repo" (like really produce the file) 2) For me it is not clear the future is smaller self-hosted LLMs. As of today, most useful for me is to use best models, and those are not self-hosted.

Once we get used to the fact that LLMs exist they won't be sold on the gee-whiz "wow, a talking assistant just like in my sci-fi movies!" factor.

They'll be used for particular language classification and search tasks, and for that you'd want several lighter, faster, cheaper and more specialized models. Not one with an arbitrary "best" score that's based on tricking the Turing test.

Re: OpenAI adds MCP support to Agents SDK

#212

Post by paradite » Thu, Mar 27, 2025, 11:35 AM UTC

MCP is basically commoditizing SaaS and software by abstracting them away behind the AI agent interface.

It benefits MCP clients (ChatGPT, Claude, Cursor, Goose) more than the MCP servers and the service behind the MCP servers (GitHub, Figma, Slack).

Re: OpenAI adds MCP support to Agents SDK

#213

Post by romankolpak » Thu, Mar 27, 2025, 12:04 PM UTC

davedx wrote: post #193

tlrobinson wrote: post #111

Earlier quoted context omitted.

100%. I know I’m in the “get off my lawn” phase of my career when I see things like MCP and LangChain, but know I would have been excited about them earlier in my career.

I’m seriously considering getting out of IT because of it

because of MCP and langchain?

Re: OpenAI adds MCP support to Agents SDK

#214

Post by liamwire » Thu, Mar 27, 2025, 12:07 PM UTC

otabdeveloper4 wrote: post #183

tcdent wrote: post #4

Big question in my mind was if OpenAI was going to formally endorse this (since it was created by Anthropic) but we have our answer. MCP is now the industry standard for connecting LLMs to external tools.

> MCP is now the industry standard for connecting LLMs to external tools. No it isn't. We're still five or ten years away from real standards. (Anyways it's clear that the future is smaller self-hosted LLMs, so whatever standard eventually emerges will be based on that paradigm.)

Sure, like how we all self-host our own email servers and photo albums? Honestly, I think you’re about as wrong as you could possibly be, both on timelines, and in that I’d argue the arc of consumer tech adoption bends towards centralisation most often.

Standards are already emerging, including MCP, and to say that simply because they’ll evolve and be replaced over time means they’re not ‘real’ now is ridiculous. Look at the early internet and web as examples.

Local models, even accounting for reasonable progress and device performance improvements, will always, inherently, be behind the eight ball compared to SOTA models. While they may be sufficient for the low hanging fruit, I’d not bet against the frontier models being every bit as compelling relatively speaking.

Using weasel words like ‘real’ and ‘x is the future’ is astoundingly arrogant, and anyone claiming with confidence that they’ve got any idea where we’re heading is almost assuredly wrong.

Re: OpenAI adds MCP support to Agents SDK

#215

Post by thisisfixer » Thu, Mar 27, 2025, 12:07 PM UTC

keithwhor wrote: post #64

Today MCP added Streamable HTTP [0] which is a huge step forward as it doesn't require an "always-on" connection to remote HTTP servers. However, if you look at the specification it's clear bringing the LSP-style paradigm to remote HTTP servers is adding a bunch of extra complexity. This is a tool call, for example: { "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "get_weather", "arguments": {…

fully agree, and that's what we do at ACI.dev as a managed authenticated tool calling platform. https://www.aci.dev/ And we expose more tool discovery flexibility rather than just list_tools()

Re: OpenAI adds MCP support to Agents SDK

#216

Post by ramesh31 » Thu, Mar 27, 2025, 12:10 PM UTC

thisisfixer wrote: post #215

keithwhor wrote: post #64

Today MCP added Streamable HTTP [0] which is a huge step forward as it doesn't require an "always-on" connection to remote HTTP servers. However, if you look at the specification it's clear bringing the LSP-style paradigm to remote HTTP servers is adding a bunch of extra complexity. This is a tool call, for example: { "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "get_weather", "arguments": {…

fully agree, and that's what we do at ACI.dev as a managed authenticated tool calling platform. https://www.aci.dev/ And we expose more tool discovery flexibility rather than just list_tools()

>And we expose more tool discovery flexibility rather than just list_tools()

Extremely curious about this as just directly listing all tools to an agent will obviously not scale well. What does the interface look like?

Re: OpenAI adds MCP support to Agents SDK

#217

Post by [deleted] » Thu, Mar 27, 2025, 12:15 PM UTC

imtringued wrote: post #200

michaelsbradley wrote: post #146

Earlier quoted context omitted.

ad hoc RPC[1] that involves JSON request/response payloads and is wed to HTTP transport is arguably worse than conforming to the JSON-RPC 2.0 specification[2]. [1] if it’s not REST (even giving a pass on HATEOAS) then it’s probably, eventually, effectively RPC, and it’s still ad hoc even if it’s well documented [2] https://www.jsonrpc.org/specification

The big irony behind HATEOAS is that LLMs are the mythical "evolvable agents" that are necessary to make HATEOAS work in the first place. HATEOAS was essentially built around human level intelligence that can automatically crawl your endpoints and read documentation written in human language and then they scratched their head why it didn't catch on. Only browser like clients could conform to HATEOAS, because they ess…

[deleted]

Re: OpenAI adds MCP support to Agents SDK

#218

Post by deadbabe » Thu, Mar 27, 2025, 12:27 PM UTC

antupis wrote: post #175

keithwhor wrote: post #64

Today MCP added Streamable HTTP [0] which is a huge step forward as it doesn't require an "always-on" connection to remote HTTP servers. However, if you look at the specification it's clear bringing the LSP-style paradigm to remote HTTP servers is adding a bunch of extra complexity. This is a tool call, for example: { "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "get_weather", "arguments": {…

Why is this get_weather location "New York" always an example when people talk about tool calling?

Because if you can make it New York City, you can make it anywhere.

Re: OpenAI adds MCP support to Agents SDK

#219

Post by thanatropism » Thu, Mar 27, 2025, 1:17 PM UTC

keithwhor wrote: post #64

Today MCP added Streamable HTTP [0] which is a huge step forward as it doesn't require an "always-on" connection to remote HTTP servers. However, if you look at the specification it's clear bringing the LSP-style paradigm to remote HTTP servers is adding a bunch of extra complexity. This is a tool call, for example: { "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "get_weather", "arguments": {…

Ehh. Sometimes you don't want to have to have string builders to assemble REST calls.

Re: OpenAI adds MCP support to Agents SDK

#220

Post by punkpeye » Thu, Mar 27, 2025, 2:08 PM UTC

tonyhb wrote: post #152

avaer wrote: post #101

Does anyone have any prior art for an MCP server "message bus" with an agent framework like Mastra? E.g. suppose I want my agent to operate as Discord bot listening on channel via an MCP server subscribed to the messages. i.e. the MCP server itself is driving the loop, not the framework, with the agent doing the processing. I can see how this could be implemented using MCP resource pubsub, with the plugin and agent b…

https://inngest.com and agentkit. disclaimer is I work on it. Does all of the event stuff and state stuff for you. Plus the orchestration.

Big fan of Inngest! Most of http://glama.ai/mcp logic is built on top of Inngest.