Ground Control for 3rd party APIs consumption 👩🚀
- Tweets 65
- Following 68
- Followers 50
- Likes 62
Pinned Tweet
Today marks an exciting new chapter for Lunar.dev. We're proud to share that @boomi has officially completed its acquisition of Lunar.dev.
By joining forces with @boomi , our AI and MCP gateway technology will reach enterprise scale, helping organizations build and operate AI-powered workflows more effectively than ever before.
A huge thank you to our customers and team for everything you've done to build Lunar.dev into what it is today.
👉 Full announcement: boomi.com/blog/lunar-dev-boo…
1
4
176
🚀 Big news! Boomi has officially completed its acquisition of spklr.io/6018EuzWi, an innovator in AI and MCP gateway.
We're excited about what we'll build together. More innovation, more possibilities.
spklr.io/6012EuzWm
2
5
356
Standing up an MCP gateway prototype isn't the hard part. Auth, routing, logging: a small team ships that in a few weeks.
1
2
134
Rotating a key across a few servers is fine. Across a few hundred instances spread across teams, it turns into a recurring fire drill nobody keeps up with.
1
2
28
Past 5 servers or any compliance ask, the maintenance curve is what gets you, not the build cost. Full breakdown: lunar.dev/post/mcp-gateway-b…
2
25
LangChain took a coding agent from 52.8% to 66.5% pass rate without changing the model.
They changed everything around it. That gap is the whole job now.
We wrote up why: lunar.dev/post/agent-harness…
1
165
Engineering gets AI in days. Everyone else gets a waitlist.
The problem is not the tools. It is the operating model.
We wrote the blueprint for rolling out AI across every department without losing governance.
lunar.dev/post/how-to-enable…
1
188
Most MCP server implementations store credentials in plaintext in the database.
Any engineer with read access can query that table and retrieve every API key, OAuth token, and database password in your system.
1
1
197
Three things that actually matter:
* Encrypt at rest with a key stored separately from the DB
* Scope credentials by identity, not just hide them in the UI
* Rotation should be automatic, not a config file runbook
1
1
137
We wrote up the full approach, including how we handle it in MCPX:
lunar.dev/post/best-practice…
1
120
CLI vs MCP is a developer argument about developer tools.
The second wave of AI users won't be developers. The LLM doesn't know or care which one you pick. It reads the description and calls the tool.
CLI breaks the moment an agent acts on behalf of someone other than the dev who set it up.
Without a governance layer across both, you don't have an AI strategy. You have experiments waiting to become a security incident.
lunar.dev/post/cli-vs-mcp-yo…
2
192
MCP just hit 97M monthly downloads. Cisco announced MCP security tooling at RSA. The "it's just a dev tool" era is over.
Here's how the top open source MCP gateways actually stack up in 2026 🧵
Full breakdown: lunar.dev/post/the-best-open…
2
2
195
4. IBM ContextForge Quick snapshot:
* Best for: Large enterprises with dedicated platform teams and months to deploy
* Latency: Cluster dependent
* License: MIT
* Deployment: High complexity
* Key limitation: Enterprise governance features are less documented than the federation capabilities; the access control model is partial
1
102
5. MCPJungle Quick snapshot:
* Best for: Prototyping and early-stage deployments you expect to outgrow
* Latency: Low
* License: Open source
* Deployment: Single binary or Docker Compose
* Key limitation: No credential isolation, no compliance-ready audit trails, and RBAC is basic even in enterprise mode
83