What started as an experiment has become a very useful little infrastructure. In continuously expanding out my AI-native system, over time I found myself trusting it for more and more different tasks. I had been using it completely headless, but I started to feel that having a small screen would really enhance it's ability to stay in the loop with me, and would also serve as a clear starting point for an Agent OS that controls the entire machine this level, which has been going very well so far (will have updates on that soon). There's so many things I could get into about controlling this from your phone through Termius, and the benefits of being able to throw over tasks to it. Just the ability to use it as a machine that's always on, and invoke Claude Code via terminal on it for cron jobs has been a great convenience. So in total, so far it's earned itself a face. Let's see if it earns itself a voice too.

Thanks to a great idea from Ray Deck, I have reduced the number of tools in the snappy.ai Xano MCP from ~180 tools and ~150,000 tokens to ~1000 tokens and 3 core tools: 1. Gemini Flash Powered Search - "What tools do I have?" (Semantic search across all tools - e.g., "create table", "list functions") 2. Info - "Tell me more about that specific tool" (returns parameters, examples, docs) 3. Execute - "Do it" (runs the tool with the right parameters) Now the initial handshake costs only ~1000 tokens instead of 150,000. Claude discovers tools as needed rather than loading everything upfront. This pattern should work for any MCP with dozens or hundreds of tools. Instead of exposing everything at once, create a search/discovery layer that lets Claude Code find what it needs when it needs it!

I’ve been working on MCP extensively over the last few months - including building Snappy Xano MCP (mcp.snappy.ai) and also an MCP for UniVerse/Multi-Value. Recently I have also been working on creating ‘MCP Friendly’ endpoints, which really opened my eyes to a whole new side of MCP building. Through the encouragement of Ray Deck, I am starting a weekly call for those interested in chatting about MCP and picking my brain about it: https://lu.ma/3fki6vo5 It will be on Wednesdays at 1:00PM Eastern Time, and you are all very welcome to join!

If you use Xano, this is basically a life hack that will save you WEEKS of development time. I show how to build database tables and endpoints in seconds using the (Snappy) Xano MCP + Claude-Code. Not all of these features are available for every Xano account (I am testing some Xano beta features) - but 90% of them are, and this blew my mind when I finally got it working. I think it's worth a watch!

After weeks of work, I'm thrilled to share that Snappy MCP for connecting Claude to Xano is finally working! What is it? Snappy MCP is a remote Model Context Protocol server that: - Securely stores your Xano API key - Provides OAuth authentication - Runs continuously on edge servers - Maintains persistent connections - Requires zero setup or code Why I built this: I needed a way to manage multiple Xano API connections without constantly editing config files, risking exposure of keys, or dealing with connection drops. This solution absorbs all that complexity. - The simple dashboard - API key storage - Connection in Cloudflare Playground - Integration with Claude Desktop - Persistent authentication What's coming: The beta launches next week with support for 40+ Xano operations, including: - Database management - Table operations - API endpoint generation - Record manipulation - System administration Who needs this: - Xano developers using Claude - Teams sharing AI access to Xano - Anyone tired of API key management Comment if you'd like to be part of the Beta! And if you'd like to check out the video I shared on LinkedIn, here is the link! Likes and shares are hugely appreciated!: https://www.linkedin.com/feed/update/urn:li:activity:7329160420450004993/ Thank you everyone for your support!