mcp-proxy-server

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

1Explicit recommenders

202GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I have used `mcp-proxy` but (afaik) you can only use it 1-to-1 and I wanted an N-to-1 proxy so that instead of configuring all my MCP servers in the multiple clients I've…

joshstrange used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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, 3:56:07 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 week2 dated mentions

Observed mentions: 2025-02-19 19:46:17 UTC to 2025-04-14 12:53:30 UTC. Weeks start Monday, UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Feb 17	2025-02-17 00:00:00 UTC	2025-02-24 00:00:00 UTC	1	1
Feb 24	2025-02-24 00:00:00 UTC	2025-03-03 00:00:00 UTC	0	0
Mar 3	2025-03-03 00:00:00 UTC	2025-03-10 00:00:00 UTC	0	0
Mar 10	2025-03-10 00:00:00 UTC	2025-03-17 00:00:00 UTC	0	0
Mar 17	2025-03-17 00:00:00 UTC	2025-03-24 00:00:00 UTC	0	0
Mar 24	2025-03-24 00:00:00 UTC	2025-03-31 00:00:00 UTC	0	0
Mar 31	2025-03-31 00:00:00 UTC	2025-04-07 00:00:00 UTC	0	0
Apr 7	2025-04-07 00:00:00 UTC	2025-04-14 00:00:00 UTC	0	0
Apr 14	2025-04-14 00:00:00 UTC	2025-04-21 00:00:00 UTC	1	1

What Hacker News says

2 sources

nzach·Apr 14, 2025

> why we not just use API Did you meant to write "a HTTP API"? I asked myself this question before playing with it a bit. And now I have a slightly better understanding, I think the main reason was created as a way to give access of your local resources (files, envvars, network access...) to your LLM. So it was designed to be something you run locally and the LLM has access. But there is nothing preventing you making an HTTP call from a MCP server. In fact, we already have some proxy servers for this exact use-case[0][1]. [0] - https://github.com/sparfenyuk/mcp-proxy [1] - https://github.com/adamwattis/mcp-proxy-server

In Everything wrong with MCP

joshstrange·Feb 19, 2025Recommendation phrase

I have used `mcp-proxy` but (afaik) you can only use it 1-to-1 and I wanted an N-to-1 proxy so that instead of configuring all my MCP servers in the multiple clients I've tested out I could just add 1 server and pull in everything. I found `mcp-proxy-server` [0] which seemed like it would do what I want but I ran into multiple problems. I added some minor debug logging to it and the ball sort of rolled downhill from there. Now it's more my code than what was there originally but I have tool proxying working for multiple clients (respecting sessionIds, etc) and I think I've solved most all the issues I've run into and added features like optional tool prefixing so there isn't overlap between MCP servers. Given what I know now, I don't think N-to-1 is quite as useful as I thought. Or rather, it really depends on your "client". If you can to

Read the rest

ggle on/off tools in your client then it's not a big problem but sometimes you don't want "all" the tools and if you client only allows toggling per MCP server then you will have an issue. I love the ideas of workflows and how you have defined agents. I think my current issue is almost too many tools and the LLM sometimes gets confused over which ones to use. I'm especially thrilled with your HTTP endpoints you expose for the agents. My main MCP server (my custom tools I wrote, vs the third-party ones) exposes an HTTP GUI for calling the tools (faster iteration vs trying it through LLMs) and I've been using that and 3rd-party chat clients (LibreChat and OpenWebUI) as my "LLM testing" platform (because I wasn't aware of a better options) but neither of those tools let you "re-expose" the agents via an API. All in all I'm coming to the conclusion that 90% of MCP servers out there are really cool for seeing what's possible but it's probably best to write your own tools/MCP since most all MCP servers are just thin wrappers around an API. Also it's so easy to create an MCP server that they are popping up all over the place and often of low quality (don't fully implement the API, take shortcuts for the authors use-case, etc). Using LLMs to writing the "glue" code from API->Tool is fairly minor and I think is worth "owning". To sum that all up: I think my usage of 3rd party MCP servers is going to trend towards 0 as I "assimilate" MCP servers into my own codebase for more control but I really like MCP as a way to vend tools to various different LLM clients/tools. [0] https://github.com/adamwattis/mcp-proxy-server

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