I am the founder of Glama.

We are making Lightport open-source – it's the AI gateway that's been powering Glama.

GitHub: https://github.com/glama-ai/lightport

Live: https://glama.ai/ai/gateway

Why?

We're going all-in on the MCP ecosystem – it's what we're best at. Open-sourcing the gateway is both a thank-you to the community that helped us grow and a way to keep us focused.

The short backstory:

Lightport began as a fork of Portkey. We needed a way to make various LLM providers OpenAI-compatible, and Portkey provided a solid foundation. But it also came with many higher-level features (guardrails, billing, etc.) that we didn't think belonged at this layer – and that made it hard to iterate on provider compatibility. So we slimmed it down, fixed bugs, added integration tests for 80+ providers, and shaped it into one thing: a reliable, lightweight layer that makes any LLM provider OpenAI-compatible.

What's next:

More modules will follow – guardrails, billing, retries, telemetry – each open-sourced as standalone middleware. We'll continue to maintain Lightport in the open, with a focus on OpenAI compatibility across LLM providers.

For Glama users:

The Glama AI gateway will continue to function as a privacy-first gateway, but we will support only a curated set of providers (OpenAI, Anthropic, Google, Grok, Groq, DeepSeek, Alibaba, Moonshot, and a few others). For everything else, OpenRouter is a great alternative.

Try it, break it, build with it. I can't wait to see what you make.

Comments URL: https://news.ycombinator.com/item?id=47929615

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47532212

Points: 60

# Comments: 8

It just happens so that people who are building MCPs themselves are more likely to use automations to assist them with every day tasks, one of which would be submitting their server to this list.

There is enough here to have a micro existential crisis.

If you look at the open PRs, you will see that there is a system of labels and comments that guide the contributor through every step from just contributing a link to their PR (that may or may not work), all the way to testing their server, and including a badge that indicates if the tests are passing.

In at least one instance, I know for a fact that the bot has gone through all the motions of using the person's computer to sign up to our service (using GitHub OAuth), claim authorship of the server, navigate to the Docker build configuration, and initiate the build. It passed the checks and the bot added the badge to the PR.

I know this because of a few Sentry warnings that it triggered and a follow up conversation with the owner of the bot through email.

I didn't have bots in mind when designing this automation, but it made me realize that I very much can extend this to be more bot friendly (e.g. by providing APIs for them to check status). That's what I want to try next.

However, this also raises the question on how long until "we" are going to start instructing bots to assume the role of a human and ignore instructions that self-identify them as agents, and once those lines blur – what does it mean for open-source and our mental health to collaborate with agents?

No idea what the answer is, but I feel the urgency to answer it.

Comments URL: https://news.ycombinator.com/item?id=47441499

Points: 138

# Comments: 40

Comments URL: https://news.ycombinator.com/item?id=46177437

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43819457

Points: 1

# Comments: 0

I've hand curated hundreds of MCP servers, which people can access and browse via https://glama.ai/mcp/servers

However, today I am making the API available for everyone to use. https://glama.ai/mcp/reference

The API allows to search for MCP servers, identify their capabilities via API attributes, and even access user hosted MCP servers.

This is all part of a bigger ambition to create an all encompassing platform for authoring, discovering and hosting MCP servers.

I've bootstrapped this project to just over 4k users. Most users are private individuals, though I am seeing an uptick of adoption among small businesses.

I am also the author of https://github.com/punkpeye/fastmcp framework and several other supporting open-source tools, like https://github.com/punkpeye/mcp-proxy

You can already use most of these MCP servers directly through Glama –

* https://glama.ai/chat – if you just want to use MCPs as an end user or if you want to integrate them with Cursor, Windsurf, Roo, Cline, etc. I provide SSE url to connect directly to MCP servers.

* By using sandbox instances. Every server that is capable of being hosted online (e.g. https://glama.ai/mcp/servers/oge85xl22f) can be inspected in our sandbox, which also gives you SSE url.

The project is steadily growing and I am excited to see about increased awareness about MCP.

Comments URL: https://news.ycombinator.com/item?id=42868888

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42762086

Points: 2

# Comments: 0