Building @ClawQL Agent/MCP as the API and document intelligence platform for enterprises!
PlatformEng/SRE/DevOps in a love-hate relationship with Kubernetes.
mcp-grpc-transport is now on npm (v0.1.0).
Pluggable gRPC transport for MCP that supports:
- Full protobuf surface (ListTools, CallTool, streaming ops, pagination, cancellation)
- Bidirectional Mcp.Session stream (NDJSON compatibility)
- gRPC health checking + optional server reflection
- TLS/mTLS via env vars
- Interceptors and custom options
This is the transport many teams have been waiting for, especially those already running gRPC microservices.
If you’re building production MCP servers and already operate in a gRPC-heavy environment, this should feel like a natural fit. It also pairs excellently with unified MCP servers that embed optimized internal layers (like GraphQL proxies for token efficiency).
Installation & basic usage is straightforward (see code snippet in comments or npm page).
One-liner integration via maybeStartGrpcMcpServer({ createMcpServer }).
Perfect drop-in for teams tired of JSON serialization overhead or wanting native mesh routing.
Docs & examples on the npm page. Built as part of the ClawQL stack but completely generic.
Try it with ClawQL (now unified single-process) or your own MCP server. Feedback, issues, and contributions welcome.
Repo: https://t.co/yYHhb12Nih
npm: https://t.co/DaA3a62CZs
Feedback, bug reports, and PRs are very welcome. Let’s make MCP even more cloud-native and production-ready together.
#MCP #gRPC #AI #AgenticAI #TypeScript #Kubernetes #EnterpriseAI
@RhysSullivan@ProEvilz Kubernetes is one way with local DNS / loadbalancer
Install it into locally running cluster, expose it, then route to it with local dns or load balancer if you run multiple replicas
Then when computer restarts or the mcp has an issue etc the cluster and container heals itself🍻
If y’all want to see what an MCP done right looks like then check out @ClawQL
Built around codemode with graphql layer to trim token payloads. Saves cost and improves performance.
Search/Execute for any API
Cache short term info
Memory for long term info
Heavy defense-in-depth
@kentcdodds MCP was never dead. Just needed time to fully wake up. We’ve made such huge progress on the MCP front in terms of token reduction, better auth, better isolation, and more. All we needed was people willing to put in the work to get it right and now MCP is stronger than ever before
@LowLevelTweets@kentcdodds It was mostly in context of them vs cli tools directly. Argument was MCP would bloat. So many bad engineers cried about it and gave up.
Then @Cloudflare came along with code mode and now Claude and others have dynamic tool loading and there are several ways to solve the issues.
@RhysSullivan Yep but why stop there? IMO the real unlock is drafting a synthetic dataset with examples of how the MCP should and should not be used then doing a QLoRA fine tune against the models to force them to perform tool calls more efficiently.
We should be shipping datasets + skills 🍻
@RhysSullivan@kr0der Connect Presidio by Microsoft or Privacy Filter by OpenAI for automatic privacy redaction. Lightweight enough to run on every call to ensure no leaking of sensitive info
I’ve mentioned this before: this is one of the oncoming trains for corp-security. We’ve long failed at least-privilege, but weren’t often punished for it.
Helen in HR (or Bob in accounts) didn’t know what to do with the extra perms they didn’t know they had.
Their agents will.
@wisplite@growing_daniel@lucas__crespo Yep and you still can. But for an increasingly large percentage of the developer population, the amount of typing and frequency of said typing is drastically falling off a cliff as AI becomes the primary generator of the bulk of content. So the need to never look away diminishes.
Honestly yes. The way AI first workflows have changed over the years, this is the ideal time for this type of feature. iPhone was made was to allow per-app customization and experiences not tied to a fixed keyboard. This brings that vision back again at the right time for it tbh.
The touchbar was too early and didn't deserve to die, it deserved an LLM.
Static shortcut buttons were the wrong bet.
Imagine buttons that rewrite themselves based on whatever you're doing, that's the keyboard that feels right for an AI-native Mac.
@growing_daniel@lucas__crespo My head is not stuck attached to a stick. I can look down and away from my monitor from time to time it’s okay really. You may be permanently attached to your monitor with your eyes but people can look away when they want to. Hope this helps. 🙏🏻
@ZackKorman I’m new to seeing this degree of carelessness. I’m used to people caring more about this stuff in the past. I’m sure you’ve got war stories for days though on the topic.
So let me ask what’s a realistic solution to this at scale? Do we need lobbies for new regulations in place?
Non-cyber people will be like "damn cybersecurity is crazy right now" and then two days later post "gotta give your agent access to prod or you're ngmi."
They don't see the connection between these things, and that's why cybersecurity is hard.
@ZackKorman Dude that post was wild. I’m running out of ways to be shocked by this stuff though. Ai has surfaced more careless behavior than I ever would have believed possible. Even simple things like not giving username and password to others has been completely thrown out the window now..
I’m trying to put together the most comprehensive “don’t let your agent get compromised” and “mitigate the effects of agent compromise” security guide I can
Meanwhile the idiots at YC are literally giving direct access to their production DBs and calling it trust-by-default
Wtf
One night I quietly gave our AI agent full access to YC's production database. It made the agent 10x more useful. That's what convinced me that trust-by-default is the only way to get the most out of agents.
@RhysSullivan No don’t let them do that. That is how you bake hallucinations into tool calls
What you want is a state machine that enforces a clear directional flow of tool calls with predefined reasons for each transition between state nodes
That leads to deterministic auditable behavior 🍻
Man goes to doctor. Says he's depressed about AI. He fears the permanent underclass.
Doctor says, "Treatment is simple. Read Gary Marcus. LLMs are stochastic parrots—they can't reason out of distribution."
Man bursts into tears. "But doctor..." he says, "I am in distribution!"