Live data from Hacker News

Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

github.com

41–50 of 159 posts

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#41
post #37

This looks awesome! Quick question, are there plans to support SSE MCP servers? I see Stdio [0] are supported and I can always run a proxy but SSE would be awesome. [0] https://mastra.ai/docs/reference/tools/client

Hey! Glad to hear you're excited about it! Yes, we're currently working on improving our MCP support in general - we'll have more to share soon, but part of that is supporting SSE servers directly

Very cool. Like I said I can make it work with Stdio but I have a SSE MCP proxy I wrote to combine multiple MCP servers (just to make plugging in all my tools to a new client easier to test). That said, I think after looking at the docs that I'll be tempted to move my tools in directly but I probably will keep them behind MCP for portability.

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#44
post #37

Earlier quoted context omitted.

Hey! Glad to hear you're excited about it! Yes, we're currently working on improving our MCP support in general - we'll have more to share soon, but part of that is supporting SSE servers directly

Very cool. Like I said I can make it work with Stdio but I have a SSE MCP proxy I wrote to combine multiple MCP servers (just to make plugging in all my tools to a new client easier to test). That said, I think after looking at the docs that I'll be tempted to move my tools in directly but I probably will keep them behind MCP for portability.

Oh nice, did you write your own proxy or are you using something like https://www.npmjs.com/package/mcp-proxy ?

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#45

By the developers of Gatsby is a minus, not a plus makes me think this is going to be the next abandonware.

gatsby was one of the first static react frameworks, now you have things like nextjs remix astro etc... i dont think abandonware is fair, thats just the way software goes

The Gatsby team made a lot of promises upon which they didn't follow through. Not a great way to build confidence in your next big project.

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#46

By the developers of Gatsby is a minus, not a plus makes me think this is going to be the next abandonware.

Gatsby never made sense to me. Weird design decisions I couldn’t find any plausible reason for. As soon as Next.js became capable of doing SSG I convinced my team to abandon Gatsby. Definitely a minus, sorry.

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#48
post #39

I don’t really understand agents. I just don’t get why we need to pretend we have multiple personalities, especially when they’re all using the same model. Can anyone please give me a usecase, that couldn’t be solved with a single API call to a modern LLM (capable of multi-step planning/reasoning) and a proper prompt? Or is this really just about building the prompt, and giving the LLM closer guidance by splitting in…

I don't work in prompt engineering but my partner does and she tells me numerous need for agents in cases where you want some technology which goes and seeks things on the live web and then comes back and you want to make sense of that found data with the LLM and pre-written prompts where you use that data as variables, and then possibly go back into the web if the task remains unsolved.

Re: Show HN: Mastra – Open-source JS agent framework, by the developers of Gatsby

#49
post #39

I don’t really understand agents. I just don’t get why we need to pretend we have multiple personalities, especially when they’re all using the same model. Can anyone please give me a usecase, that couldn’t be solved with a single API call to a modern LLM (capable of multi-step planning/reasoning) and a proper prompt? Or is this really just about building the prompt, and giving the LLM closer guidance by splitting in…

I don't work in prompt engineering but my partner does and she tells me numerous need for agents in cases where you want some technology which goes and seeks things on the live web and then comes back and you want to make sense of that found data with the LLM and pre-written prompts where you use that data as variables, and then possibly go back into the web if the task remains unsolved.

Can't that be solved with regular workflow tools and prompts? Is that what an agent is, essentially?

Or is an agent a collection of prompts with a limited set of available tools?

Post reply on HN