Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenAI adds MCP support to Agents SDK

openai.github.io

Post reply on HN
Print view View original

101–110 of 281 posts

Re: OpenAI adds MCP support to Agents SDK

#101

Post by avaer »

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 being aware of this protocol and how to pump the message bus loop, but I'd rather not reinvent it.

Is there a standard way of doing this already? Is it considered user logic that's "out of scope" for the MCP specification?

EDIT: added an example here https://github.com/avaer/mcp-message-bus

Re: OpenAI adds MCP support to Agents SDK

#103

Post by vessenes »

senko wrote: post #36
vessenes wrote: post #30

Earlier quoted context omitted.

If you're interested, I'd encourage you to implement an MCP integration and see if you change your mind. For instance, I have a little 'software team in a box' tool. v1 integrated github and three different llms manually (react + python backend). This is fine. You can call github commands via CLI on the backend, and add functionality somewhat easily, depending on the LLM's knowledge. Pain points -- if you want workfl…

That sounds like v1 was "tool calls llm", while v2 is "llm calls tool"? The fact that the tool call is via mcp and not in-process function call seems to be an implementation detail?

first sentence sounds right to me.

“Implementation detail” is doing a lot of work in the second sentence, though. There are whole startups like langchain that were trying to build out a reasonable agent framework integrated in such a way that the LLMs can drive. MCP makes that really easy — LLM training just has to happen once, against MCP spec, and I get client and LLM support for an iterative tool use scenario right in the LLM.

Re: OpenAI adds MCP support to Agents SDK

#104

Post by ondrsh »

kblissett wrote: post #96
ondrsh wrote: post #70

Earlier quoted context omitted.

To really understand MCP you need to think about application design in a different way. In traditional applications, you know at design-time which functionality will end up in the final product. For example, you might bundle AI tools into the application (e.g. by providing JSON schemas manually). Once you finish coding, you ship the application. Design-time is where most developers are operating in, and it's not wher…

Isn't this just the same paradigm as plugins?

Similar, but one level higher.

Plugins have pre-defined APIs. You code your application against the plugin API and plugin developers do the same. Functionality is being consumed directly through this API — this is level 1.

MCP is a meta-protocol. Think of it as an API that lets arbitrary plugins announce their APIs to the application at runtime. MCP thus lives one level above the plugin's API level. MCP is just used to exchange information about the level 1 API so that the LLM can then call the plugin's level 1 API at runtime.

This only works because LLMs can understand and interpret arbitrary APIs. Traditionally, developers needed to understand an API at design-time, but now LLMs can understand an API at runtime. And because this can now happen at runtime, users (instead of developers) can add arbitrary functionality to applications.

I hate plugging my own blog again but I wrote about that exact thing before, maybe it helps you: https://www.ondr.sh/blog/thoughts-on-mcp

Re: OpenAI adds MCP support to Agents SDK

#106

Post by NicuCalcea »

keyle wrote: post #97

I'm new to "MCP"... It says here that even IDE plug into this MCP server [1], as in you don't edit files directly anymore but go through a client/server? It wasn't bad enough that we now run servers locally to constantly compile code and tell us via json we made a typo... Soon we won't even be editing files on a disk, but accessing them through a json-rpc client/server? Am I getting this wrong? [1] https://modelconte…

I think you are getting it wrong. Some IDEs like Cursor and VS Code extensions like Cline support MCP servers, meaning you can give them access to your databases, Jira tickets, Notion notes, Slack messages, etc.

Re: OpenAI adds MCP support to Agents SDK

#107

Post by johnjungles »

If you want to try out mcp (model context protocol) with little to no setup:

I built https://skeet.build/mcp where anyone can try out mcp for cursor and now OpenAI agents!

We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support and complexity trying to stand up your own.

Mostly for workflows like:

* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development

Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on

Lmk what you think!

Re: OpenAI adds MCP support to Agents SDK

#108

Post by [deleted] »

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": {…

[deleted]

Re: OpenAI adds MCP support to Agents SDK

#109

Post by anonymousDan »

ondrsh wrote: post #104
kblissett wrote: post #96

Earlier quoted context omitted.

Isn't this just the same paradigm as plugins?

Similar, but one level higher. Plugins have pre-defined APIs. You code your application against the plugin API and plugin developers do the same. Functionality is being consumed directly through this API — this is level 1. MCP is a meta-protocol. Think of it as an API that lets arbitrary plugins announce their APIs to the application at runtime. MCP thus lives one level above the plugin's API level. MCP is just used…

This sounds like a security nightmare.

Re: OpenAI adds MCP support to Agents SDK

#110

Post by NicuCalcea »

zoogeny wrote: post #73

I'm curious what the revenue plan is for MCP authors. I mean, I can see wanting to add support for existing products (like an code/text editor, image/sound/video editor, etc.) But is there a market for stand-alone paid MCP services? It seems these will mostly be usurped by the models themselves sooner or later. I mean if you create a MCP popular enough to actually make money, the foundation model will soon be able to…

Most MCP servers are thin wrappers around an API, I don't think there will be a big paid market. I imagine they will be released like SDKs are now, either by companies themselves, or by individuals when there's no official implementation. A few dev agents can even write MCP servers for themselves.

https://www.reddit.com/r/ClaudeAI/comments/1hcrxl6/cline_can...

Post reply on HN