Not only editors, but also different runtime contexts like GitHub Agents running in Actions.

We can plug in MCP almost anywhere with just a small snippet of JSON and because we're serving it from a server, we get very clear telemetry regardless of tooling and envrionment.

▲

chatmasta 15 hours ago | parent [-]

What are you using for hosting and deploying the MCP servers? I’d like something low friction for enterprise teams to be able to push their MCP definitions as easily as pushing a Git repo (or ideally, as part of a Git repo, kinda like GitHub pages). It’s obviously not sustainable for every team to host their own MCP servers in their own way.

So what’s the best centralized gateway available today, with telemetry and auth and all the goodness espoused in this blog post?

	▲	CharlieDigital 15 hours ago \| parent \| next [-]
		We built our own (may open source eventually). MCP is effectively "just another HTTP REST API"; OAuth and everything. The key parts of the protocol is the communication shape and sequence with the client, which most SDKs abstract for you. The SDKs for MCPs make it very straightforward to do so now and I would recommend experimenting with them. It is as easy to deploy as any REST API.
	▲	whattheheckheck 14 hours ago \| parent \| prev [-]
		ROSA https://docs.aws.amazon.com/whitepapers/latest/overview-depl... it should be part of your app and coordinated in a way that everyone in the enterprise can find all the available mcps. Like backstage or something