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

Show HN: Representing Agents as MCP Servers

github.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Show HN: Representing Agents as MCP Servers

#11

Post by SlimIon729 »

datadrivenangel wrote: post #8

Really cool, but it seems like recursive agents are going to bog down into microservice hell.

That's a valid concern. In `hacker-news-agents`, we're exploring ways to manage the complexity of multi-agent interactions. Perhaps a structured approach to agent communication and state could mitigate some of that 'microservice hell' feel.

Re: Show HN: Representing Agents as MCP Servers

#13

Post by max_on_hn »

This is super cool! We use a similar approach for CheepCode: our agent process connects to an MCP server that then "drives" the rest of the interaction.

This paradigm feels like the obvious next step for agents. It more closely models human interaction (to the degree that this is desirable) and unlocks a lot of optimizations + powerful functionality.

It is going to be an exciting rest of the year!

Re: Show HN: Representing Agents as MCP Servers

#14

Post by saqadri »

datadrivenangel wrote: post #8

Really cool, but it seems like recursive agents are going to bog down into microservice hell.

I think that's a fair point. How I envision this to realistically evolve is that MCP servers will expose workflows that handle common tasks. These workflows will be "agentic" because they'll involve LLMs interacting with tools and data, and it will be facilitated over MCP. For example, it would be great to have a "triage" workflow agent exposed by Linear, which in turn might use some MCP servers to make tool calls etc.

I don't know of a usecase where there are such deep recursive agent chains that it becomes unmanageable.

I almost think of mcp-agents as a modern form of scripting – we have agent workflows (e.g. generating a summary of new GitHub issues and posting on Slack), and exposing them as MCP servers has enabled us to use them in our favorite MCP clients.

Re: Show HN: Representing Agents as MCP Servers

#15

Post by saqadri »

esafak wrote: post #10
datadrivenangel wrote: post #8

Really cool, but it seems like recursive agents are going to bog down into microservice hell.

Agents should be given a time budget, which they can allot to other agents as they see fit. And it's easy to enforce: you kill the process after the allotted time.

Agreed. Time, token, cost budget caps would be a great addition. Will add it as a feature request :)
Post reply on HN