Deploy your own MCP server with HTTPS and an access key
Originally published on the Hubfly space blog . TL;DR What you get: your own MCP server on a public HTTPS address, locked with an access key, and connected to Claude Code, Cursor and Codex. Who it's for: developers who built (or want to build) an MCP server and are tired of it only working on localhost . Time: about 15 minutes. Cost: free on the shared tier (360 compute hours a month, no card);…
This guide explains how to deploy your own MCP (Multi-Modal Code) server with HTTPS and an access key, allowing you to access it via a public HTTPS address. It is designed for developers who have built or plan to build an MCP server but want it available beyond their local machine.
The process takes around 15 minutes and costs nothing on Hubfly's shared tier, which provides 360 compute hours per month. If you need it to run constantly, expect to pay about $2.25 per month for a dedicated 0.5 vCPU and 512 MB of RAM.
Key aspects of the guide include:
1. The server is an HTTP server, reachable at `https://your-server.eu1.hubfly.app/mcp`.
2. You can update the server from a single location, avoiding the need to duplicate setups on multiple machines.
3. The setup involves a small Python server with two tools: `add_note` and `list_notes`. Users can replace these tools with their own.
4. The deployment is done using Hubfly space, which provides a free tier without the need for a credit card.
5. Security is enhanced by the ability to lock the server using an access key at the edge, preventing unauthorized access.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
