This week we’re excited to walk you through the main hosting features that can be found on Alpic, starting with one-click deployment!

Why?

Ease of use is our bread and butter. When we set out to build Alpic, we wanted to make deploying MCP so simple that you forget that there’s infrastructure running your code. 

How it works

To get started, simply sign in to Alpic with your Github account. 

You’ll first be prompted to create a Team and add the Aplic AI app to your Github organisation. This enables a seamless sync between your deployments and your git workflow. If you belong to several organizations on Github, you can link multiple organizations to Alpic. 

Once you’re connected, choose the organization and repository containing your MCP server. If you haven’t built your MCP server yet, you can clone our Typescript template to get started.

Alpic currently supports MCPs built in Typescript, but our goal is to be both framework and language agnostic, so more support is coming soon (spoiler: Python, VERY soon)! Drop us a line if you’d like to have a say in what we support first.

Once you’ve chosen your repo, choose which branch to sync with your production environment. Alpic deploys a new version whenever you push changes to this branch. 

It's worth noting that Alpic lets you deploy your MCP servers on multiple environments, each linked to a specific branch of your git repository. We’ll talk about that later on this week!

Specify your environment variables and confirm the build commands. We automatically detect your MCP framework and build commands from your repository metadata, but you can always change them here. 

Click deploy, and that’s it! 🚀

Head to your project page to see your deployment status and build logs, as well as add new environments and and get a remote URL to try out your server with your favorite MCP client supporting SSE or streamable HTTP transport. We can also help you set up a custom domain for distribution as well. 

What this means for developers

OK fine, this is more than one click but you get the idea. You’ve done the work building your MCP server, we’ve taken care of everything you need to spin it up, test it, and share it with the world. 

The platform handles the heavy lifting, which features like authentication, logs, monitoring and others that we’ll tell you about later this week! We also take care of the transport layer, so if you build your server with stdio it will automatically support SSE, WebSockets, and HTTP streaming. And as the MCP ecosystem evolves, Alpic will keep your server compatible with new transports (and auth, and other protocol improvements), letting you stay focused on functionality instead of infrastructure.

Get started

Head to app.alpic.ai to deploy your server in seconds, and check back here tomorrow as we dive into authentication!

Bonus! Distribute your MCP server to the world… 

Now that you’ve deployed your MCP server, you’re obviously going to want to show it to everyone you know!

Unfortunately, an official MCP registry does not yet exist (at the time of writing, it’s in development by the working group maintaining the protocol). You’ll therefore need to add your server to the various registries manually. We keep an up-to-date list of the most popular registries with submission instructions and links in our docs. 

To reduce the hassle, we’ve also created an MCP install instructions generator that produces a complete tutorial and 1-click install links for the most popular MCP clients. 

Try it out here and check out our Kiwi Flight Search MCP server instructions for an example of what it looks like.​

​