HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lastmile-ai
mcp-agent
Python2025–2025
lastmile-ai / mcp-agent

mcp-agent

Build effective agents using Model Context Protocol and simple workflow patterns

5Distinct people
12Mentions
0Explicit recommenders
8.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Build effective agents using Model Context Protocol and simple workflow patterns

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month12 dated mentions

Observed mentions: 2025-01-29 16:26:07 UTC to 2025-10-28 17:25:38 UTC.

01232025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsJan 20252025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsMay 20252025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsOct 2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC312
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC312
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC000
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC211
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC000
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC110
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC220

What Hacker News says

12 sources

Show HN: MCP-C – cloud platform for running MCP agents and apps

Hello HN! Earlier this year, we shared mcp-agent (https://github.com/lastmile-ai/mcp-agent) [1][2], a lightweight framework for building agents with MCP. Since then we have tried to push the protocol to the limits, including hosting agents as long-running tools on MCP [3], and seen other creative approaches surface (mcp-ui, chatgpt apps sdk). Today, we are launching mcp-c – a cloud platform designed for hosting any kind of MCP server, including agents, ChatGPT apps, etc. We are in open beta and free to use, and would love your feedback. Here are some key choices we made: 1) Everything is MCP - Each application is deployed as a remote SSE endpoint, and implements the full MCP spec, including advanced features like elicitation, sampling, notifications and logging. 2) Durable execution via Temporal - We use Temporal as the runtime environmen
Read the rest
t, allowing you to run long-running operations. This is especially critical for agents, which need to pause/resume, be fault-tolerant, and run for a long time. 3) Local to Cloud - we're fans of how easy it is to deploy a Next.js app to Vercel, so we've made it simple to take your local mcp-agent, mcp server, OpenAI app, etc. and deploy it to the cloud. We have several examples and even a handy CLI to get started quickly [4]. It's as simple as: - uvx mcp-agent init - uv init - uv add "mcp-agent[openai]" - uvx mcp-agent login # add your openai key to mcp_agent.secrets.yaml - uvx mcp-agent deploy You can also try out these hosted mcp servers to get an idea. These can be connected to any MCP client (ChatGPT, Claude Desktop/Code, Cursor, etc.) OpenAI Pizza App - https://18t536mliucyeuhkkcnjdavxtyg66pgl.deployments.mcp-age... Basic Agent Server - https://1m82g32x8nkoppinayx0k5ye12oar6vk.deployments.mcp-age... The HN community has been a big part of mcp-agent's growth, and we're super excited to share this with you as well. We would love to hear your thoughts and feedback! --- [1] - https://news.ycombinator.com/item?id=42867050 [2] - https://github.com/lastmile-ai/mcp-agent [3] - https://news.ycombinator.com/item?id=44053754 [4] - https://github.com/lastmile-ai/mcp-agent/tree/main/examples/... [5] - https://docs.mcp-agent.com/get-started/welcome [6] - https://youtu.be/9ddtaSbUJIc
9 points · Open discussion

Show HN: MCP-C – cloud platform for running MCP agents and apps

Hello HN! Earlier this year, we shared mcp-agent (https://github.com/lastmile-ai/mcp-agent) [1][2], a lightweight framework for building agents with MCP. Since then we have tried to push the protocol to the limits, including hosting agents as long-running tools on MCP [3], and seen other creative approaches surface (mcp-ui, chatgpt apps sdk). Today, we are launching mcp-c – a cloud platform designed for hosting any kind of MCP server, including agents, ChatGPT apps, etc. We are in open beta and free to use, and would love your feedback. Here are some key choices we made: 1) Everything is MCP - Each application is deployed as a remote SSE endpoint, and implements the full MCP spec, including advanced features like elicitation, sampling, notifications and logging. 2) Durable execution via Temporal - We use Temporal as the runtime environmen
Read the rest
t, allowing you to run long-running operations. This is especially critical for agents, which need to pause/resume, be fault-tolerant, and run for a long time. 3) Local to Cloud - we're fans of how easy it is to deploy a Next.js app to Vercel, so we've made it simple to take your local mcp-agent, mcp server, OpenAI app, etc. and deploy it to the cloud. We have several examples and even a handy CLI to get started quickly [4]. It's as simple as: - uvx mcp-agent init - uv init - uv add "mcp-agent[openai]" - uvx mcp-agent login # add your openai key to mcp_agent.secrets.yaml - uvx mcp-agent deploy You can also try out these hosted mcp servers to get an idea. These can be connected to any MCP client (ChatGPT, Claude Desktop/Code, Cursor, etc.) OpenAI Pizza App - https://18t536mliucyeuhkkcnjdavxtyg66pgl.deployments.mcp-age... Basic Agent Server - https://1m82g32x8nkoppinayx0k5ye12oar6vk.deployments.mcp-age... The HN community has been a big part of mcp-agent's growth, and we're super excited to share this with you as well. We would love to hear your thoughts and feedback! --- [1] - https://news.ycombinator.com/item?id=42867050 [2] - https://github.com/lastmile-ai/mcp-agent [3] - https://news.ycombinator.com/item?id=44053754 [4] - https://github.com/lastmile-ai/mcp-agent/tree/main/examples/... [5] - https://docs.mcp-agent.com/get-started/welcome
1 points · Open discussion
Haha, I didn't have control on the blog website, just the content. The readme and code is the ultimate source of truth (and easier to read):https://github.com/lastmile-ai/mcp-agent/blob/main/src/mcp_a... So the core idea is the Deep Orchestrator is pretty unopinionated on what to use for searching, as long as it is exposed over MCP. I tried with a basic fetch server that's one of the reference MCP servers (with a single tool called `fetch`), and also tried with Brave. I think the folks at Jina wrote some really good stuff on the actual search part: https://jina.ai/news/a-practical-guide-to-implementing-deeps... -- and how to do page/url ranking over the course of the flow. My recommendation would be to do all that in an MCP server itself. That keeps the "deep orchestrator" architecture fairly clean, and you can plug in increasingly sophis
Read the rest
ticated search techniques over time.
In Show HN: Building a Deep Research Agent Using MCP-Agent
haniehz·Jul 19, 2025Submission

Show HN: I built an AI agent that helps me invest

A while back, I built a simple app to track stocks. It pulled market data and generated daily reports based on my risk tolerance. Basically a personal investment assistant. It worked well enough that I kept going. Now, the same framework helps me with real estate: comparing neighborhoods, checking flood risk, weather patterns, school zones, old vs. new builds, etc. It’s a messy, multi-variable decision—which turns out to be a great use case for AI agents. Instead of ChatGPT or Grok 4, I use mcp-agent, which lets me build a persistent, multi-agent system that pulls live data, remembers my preferences, and improves over time. Key pieces: • Orchestrator: picks the right agent or tool for the job • EvaluatorOptimizer: rates and refines the results until they’re high quality • Elicitation: adds a human-in-the-loop when needed • MCP server:
Read the rest
exposes everything via API so I can use it in Streamlit, CLI, or anywhere • Memory: stores preferences and outcomes for personalization It’s modular, model-agnostic (works with GPT-4 or local models via Ollama), and shareable. Let me know what you all think!
32 points · Open discussion
This is exactly what we're working on at the moment! (If you're curious about following along progress, check out feature/distributed_tracing branch -- https://github.com/lastmile-ai/mcp-agent/tree/feature/distri...) The nice thing about representing agents as MCP servers is we can leverage distributed tracing via OTEL to log multi-agent chains. Within the agent application, mcp-agent tracing follows the LLM semantic conventions from OpenTelemetry (https://opentelemetry.io/docs/specs/semconv/gen-ai/). For any MCP server that the agent uses, we propagate the trace context along.
In Show HN: Representing Agents as MCP Servers
saqadri·May 21, 2025Submission

Show HN: Representing Agents as MCP Servers

Hey HN! A few months ago we shared mcp-agent (https://github.com/lastmile-ai/mcp-agent) [1][2], a lightweight framework that implements every agent pattern from Anthropic’s Building Effective Agents blog [3] and handles MCP server/client management seamlessly. Our core bet is that connecting LLMs to tools, resources, and external systems will soon be MCP-native by default. Today we're launching a significant update: Agents as MCP servers. Currently "agentic" behavior exists only on the MCP client side – clients like Claude or Cursor use MCP servers to solve tasks. With this update, Agents can be MCP servers themselves, so that any MCP client can invoke, coordinate and orchestrate agents the same way it does with any other MCP server. This paradigm shift enables: 1. Agent Composition: Build complex multi-agent systems over the same base pr
Read the rest
otocol (MCP). 2. Platform Independence: Use your agents from any MCP-compatible client 3. Scalability: Run agent workflows on dedicated infrastructure, not just within client environments 4. Customization: Develop your own agent workflows and reuse them across any MCP client. How an agent server is implemented: We’ve implemented this in mcp-agent with Workflows. Each workflow is an agent application that can interact with other MCP servers (e.g. summarizing GitHub issues → Slack message). mcp-agent exposes workflows as MCP tools on an MCP Agent Server [5]: - workflows/list – list available workflows - workflows/{WorkflowName}/run – Execute the workflow (async) - workflows/{WorkflowName}/get_status – Check workflow status - workflows/{WorkflowName}/resume – Resume paused workflow (e.g. with human input) - workflows/{WorkflowName}/cancel – Terminate workflow We’ve also implemented Temporal for durable execution [6], so agent workflows can be paused, resumed and retried in production settings. This demo [7] shows Claude invoking an MCP agent server, running workflows when appropriate, and polling for status. It basically shows agentic behavior on both the MCP client and MCP server side. We're excited about the potential this unlocks—especially as more applications become MCP-compatible clients. We'd love your feedback and ideas! [1] - https://news.ycombinator.com/item?id=42867050 [2] - https://github.com/lastmile-ai/mcp-agent [3] - https://www.anthropic.com/research/building-effective-agents [4] - https://github.com/github/github-mcp-server [5] - https://github.com/lastmile-ai/mcp-agent/tree/main/examples/... [6] - https://github.com/lastmile-ai/mcp-agent/tree/main/examples/... [7] - https://youtu.be/pLe2GAjEoYs [DEMO]
58 points · Open discussion
saqadri·Mar 12, 2025Submission

Show HN: MCP-Compatible OpenAI Agents SDK

Hey HN, OpenAI released the Agents SDK yesterday, which is great because of its simplicity. I just added MCP support for it, which is currently available as a fork here: https://github.com/lastmile-ai/openai-agents-mcp (and on pypi as the openai-agents-mcp package). You can specify the names of MCP servers to give an Agent access to by setting its `mcp_servers` property. The Agent will then automatically aggregate tools from the MCP servers, as well as any `tools` specified, and create a single extended list of tools. This means you can seamlessly use MCP servers, local tools, OpenAI-hosted tools, and other kinds of Agent SDK tools through a single unified syntax -- and have them interact in the same Agent run loop! Everything else stays exactly the same. ``` agent = Agent( name="MCP Assistant", instructions="You are a helpful as
Read the rest
sistant with access to MCP tools.", tools=[your_other_tools], # Regular tool use for Agent SDK mcp_servers=["fetch", "filesystem"] # Names of MCP servers from your config file (see below) ) ``` The servers are configured in an `mcp_agent.config.yaml` file, very similar to how they are configured for Claude Desktop: ``` $schema: "https://raw.githubusercontent.com/lastmile-ai/mcp-agent/main..." mcp: servers: fetch: command: "uvx" args: ["mcp-server-fetch"] filesystem: command: "npx" args: ["-y", "@modelcontextprotocol/server-filesystem", "."] slack: command: "npx" args: ["-y", "@modelcontextprotocol/server-slack"] ``` I have submitted an issue and PR into the openai-agents-python repo [2], and my plan is instead of a fork, I will create an extension package for MCP support (coming later today). I was able to do this pretty quickly (got it working yesterday) because I've been building the mcp-agent library (https://github.com/lastmile-ai/mcp-agent), which makes MCP server aggregation/connection really easy. I did a Show HN about it a few weeks ago [3]. Wanted to share here to get community feedback on whether this is useful, which will help me decide if I should dedicate more time to it. [1] - https://github.com/lastmile-ai/mcp-agent [2] - https://github.com/openai/openai-agents-python/issues/23 [3] - https://news.ycombinator.com/item?id=42867050
5 points · Open discussion
Here's a fairly comprehensive list: https://github.com/slavakurilyak/awesome-ai-agents CrewAI is a popular VC-backed one, but two that I think are kind of interesting in the open source space are: https://github.com/i-am-bee/beeai-framework https://github.com/lastmile-ai/mcp-agent ... However I think the vast majority of "AI Agent" use-cases in practice right now are actually just workflows, and imo dify is great for those: https://github.com/langgenius/dify [edit] worth mentioning [langfuse](https://github.com/langfuse/langfuse), which is more like a platform that addresses the observability/evals/prompt management piece of the puzzle as opposed to a full-on "agent framework". In practice I have not yet run into a case where I needed something like what OpenAI just released, nor crewAI etc (despite it feeling like those cases may be comi
Read the rest
ng)
In New tools for building agents
Ah, just saw your edited comment. I am open to suggestions about this. These names are defined in the mcp_agent.config.yaml (e.g. https://github.com/lastmile-ai/mcp-agent/blob/main/examples/...). The logic that manages keeping track of them is mcp_server_registry.py. I am open to alternative suggestions for this. I just wanted to make it easy to reference MCP servers by name and hide the logic of how they are initialized, what transport they use, what args are passed to them, into configs
In Show HN: Mcp-Agent – Build effective agents with Model Context Protocol
saqadri·Jan 29, 2025Submission

Show HN: Mcp-Agent – Build effective agents with Model Context Protocol

Hey HN, I spent my xmas break building an agent framework called mcp-agent [1](https://github.com/lastmile-ai/mcp-agent) for Model Context Protocol [2]. It makes it easy to build AI apps with MCP servers, and implements every pattern from the popular Building Effective Agents blog [3] as well as OpenAI’s Swarm [4]. I’m sharing it early to get community feedback on where to take it from here, and to ask for contributions. For those who aren’t familiar with MCP, I think of it as a standardized interface to let AI communicate with software via tool calls, resources and prompts. mcp-agent provides a higher level interface to build apps with MCP. It handles the connection management of MCP servers so you don’t have to. It also implements the Building Effective Agents patterns: - Augmented LLM (an LLM with access to one or more MCP servers) - R
Read the rest
outer, Orchestrator-Worker, Evaluator-Optimizer, and more - Swarm The key design principles are composability and reusability – every pattern is an AugmentedLLM itself, so you can chain them into more complex workflows. Some background: I worked on LSP [5] and language servers at Microsoft, and saw firsthand how standards and protocols can revolutionize developer workflows. Before LSP every IDE had its own esoteric ways of providing language services. LSP changed all that, and arguably made every language server better, since they can focus on improving a single implementation for all clients. I think AI development is in a similar pre-LSP space right now. There are tons of frameworks [6], every model provider has its own way of handling messages, tool calls, streaming, etc. I really think we need a protocol to standardize these patterns. Pretty soon every service is going to expose an MCP interface, and mcp-agent is about letting developers orchestrate these services into applications (i.e. build “MCP apps”). This can cover any use of an AI model that needs to interact with the world around it: - RAG pipelines and Q&A chatbots - Process automation via AI workflows/async tasks - Multi-agent orchestration, with human in the loop The repo contains examples [7] to build RAG agents, streamlit apps and more. There’s a lot left to build, like streaming support, server auth and tighter integration with MCP clients. But I wanted to share early in the hopes that you can guide me: - If you find this useful, please let me know. If it’s useful to you, I will dedicate all my time to improving it. - I really welcome contributions. If you want to collaborate, please reach out on github to help take this forward. I want to help standardize AI development, so developers a few years from now can look back with horror at the pre-MCP days. [1] - https://github.com/lastmile-ai/mcp-agent [2] - https://modelcontextprotocol.io/introduction [3] - https://www.anthropic.com/research/building-effective-agents [4] - https://github.com/openai/swarm [5] - https://microsoft.github.io/language-server-protocol/ [6] - https://xkcd.com/927/ (I understand the irony) [7] - https://github.com/lastmile-ai/mcp-agent/tree/main/examples
80 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.