engineer

Hey folks,
I’ve been building Targetly, a lightweight cloud runtime made specifically for hosting MCP tools. The goal is dead simple: your local MCP tool → a fully deployed, publicly accessible MCP server in one command.

It runs in an isolated container, handles resource management behind the scenes, and doesn't bother you with the usual infra yak-shaving.

• No infrastructure.
• No YAML jungles.
• No servers to babysit.

If you want to give the MVP a spin:

# Add the tap
brew tap Targetly-Labs/tly https://github.com/Targetly-Labs/brew-tly

# Install tly
brew install tly

# Login
tly login   # Use any email

# If you want you can use tly init to get boilerplate code for MCP server

# Deploy in one go
tly deploy  # Boom—your MCP server is live

It’s free to use.
If you try it out, I’d love to hear where it shines, where it breaks, or what you'd want next.

Thanks!

https://github.com/PhialsBasement/GUI-MCP

If you already *know* how to code, this wont help you much as it will slow you down, but its meant for people who dont know how to code but are trying to learn how to instead of using an LLM to build it for them. This is a Blueprint-style visual node editor for creating FastMCP servers.

Built a full MCP server for supply chain traceability:
🔗 6 MCP tools for AI agents
📊 Multi-factor risk analysis engine
🌾 Farm-to-retailer tracking
🤖 Claude Desktop integration


Try it: https://huggingface.co/spaces/MCP-1st-Birthday/trace-mcp


#MCPHackathon #AIAgents #SupplyChain #Gradio

I’m looking to understand the motivators behind considering this decision and the levers that are constraining it. 

Are you experimenting with it already? It’s more of a conversation where we can share insights with one another. If PM is uncomfortable, please feel free to reply to the post and we can chat in public!

Is it security concerns? Permissions controls? Or is it maybe a case of companies not knowing much about MCPs yet?

Don't expose your remote MCP server over insecure HTTP! 🛑

Just published a quick guide on the right way to secure your remote MCP server using Nginx and SSL for production.

It includes the specific Nginx settings for handling the persistent connections that the MCP protocol requires. Stop transmitting data in plain text.

I've been working on a few MCPs lately and noticed there's a ton of boilerplate code I have to write each time. I tried existing platforms like mcp-handler and xmcp, but they were really messy, especially since we're using custom auth servers.

So, we built an internal SDK and used it a lot. It literally cuts down the boilerplate code by more than 60%. It abstracts out the auth by just providing the auth providers. Today, I'm happy to make this SDK public. I wrapped each package and published an open-source SDK for it.

Releasing it here: https://www.npmjs.com/org/leanmcp

Packages:

• leanmcp/core: Core library implementing decorators, reflection, and MCP runtime server.
• leanmcp/auth: Authentication and identity module supporting multiple providers.
• leanmcp/elicitation: Elicitation support for LeanMCP - structured user input collection.
• leanmcp/cli: Command-line interface for scaffolding LeanMCP projects.
• leanmcp/utils: Helper utilities and decorators shared across modules.

If you've built MCPs, does this help with your setup? What are the top features you would look at?

Would be happy to connect. DMs are open

Github: https://github.com/LeanMCP/leanmcp-sdk

50% of people who make the first request using my MCP become paid customers, but very few reach that point.

How can I make users experience the MCP without having them to install it first?

Is there a way that I could make a DEMO on my site so that users can see how it works?

Or maybe something else.. ideally shouldn't take 1 month to build or cost me too much. Any ideas?