Claude Code Mastery is live in the classroom. Six modules covering agent skills, the Claude API, MCP configuration, and remote execution from your phone. Each module pairs an Anthropic Academy foundation course with a practical lesson. The Anthropic courses cover the theory. The practical lessons show how to apply it on a real machine with real files. Weekly meetup every Wednesday at 1 PM Eastern. Check-ins, concept walkthroughs, live Q&A, and accountability. Recording posted after each session. Start here: https://www.skool.com/snappy/classroom When you finish all six modules and the four Anthropic Academy courses, post with #claude-code-complete and your email to claim your certificate.

Two months heads-down. No posts, no noise. Here's why. I've been building the agentic systems that Claude Code itself now uses — skills, MCPs, orchestration patterns, the whole stack for controlling real AI agents on real work. Not demos. Not threads. Systems that ship. Snappy's positioning is sharper now: Build and control agents to get huge results. Not "MCP integration." Not "Xano MCP." Those are tools inside the bigger thing. The bigger thing is agentic building — developers and technical founders learning to stand up agents they actually control, using skills, MCPs, Claude Code, Xano, and the rest of the stack, so the work compounds instead of evaporating. If you've been here a while, you'll notice changes over the next week: - The AG Grid / WeWeb module is coming down. It's no longer the point. - The classroom is being rebuilt around four tracks: Agentic Building 101, Skills That Compound, MCP as a Power Tool, and Build & Control Agents End-to-End. - MCP Wednesday is back on. - All roads point to snappy.ai. YouTube, newsletter, blog, LinkedIn, Xano — one stack, one direction. Here's what I want from you this week: 1. Drop a comment with the one agentic system you're stuck building. Be specific. "I want an agent that does X, and it keeps breaking at Y." 2. If you're new, post in Introductions. Tell me what you're shipping and what stack you're on. 3. If you've been lurking — come back. The wave is about to break and I'd rather you ride it with a system than watch it from the shore. You built it. You're stuck. Let's fix that, live on your screen. Without the hype tax. I burn the hours so you don't. See you in the feed. — Robert

I used to restart Claude sessions all the time because I'd hit context limits or need to switch tasks. Every restart meant re-explaining my setup, tech stack, and what I was building. Then I started treating MCP servers like my 'external brain'. Instead of cramming everything into chat context, I built a simple MCP that reads my project docs, database schemas, and recent decisions from files. Now Claude just asks the MCP when it needs context. Now I can work on the same project across 10+ sessions without losing continuity. Claude remembers everything because the MCP remembers everything. Anyone else structuring their MCP servers this way? Would love to hear other patterns people are using.

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!

With the news of OpenAI leaning more into MCP - we now have THREE versions of the snappy.ai Xano MCP available for our users! mcp.snappysaas.com = uses the Snappy SDK to make it easier for AI Agents to build like an EXPERT in XanoScript, through a proprietary system of multi-layered autofixing and automatic AI review! raw.snappysaas.com = does NOT uses the Snappy SDK, for those who prefer to use raw XanoScript, which has its strengths in many cases! readonly.snappysaas.com = read only tools, for observability, and providing services such as a Slack Bot that can triage issues/answer client queries using it's advanced ability to gain insight automatically. Here is a changelog with some of the recent changes I have made in the last week: 🚀 New Features TypeScript Client Generator Tool (Beta Testing) - Automatically generate TypeScript clients for your Xano APIs - Type-safe interfaces with pagination support - Reduces integration time to frontend interfaces Enhanced Debugging System - Real-time debugging tips and context relevant suggestions - 80% faster error resolution by AI Agent - Interactive guidance for common XanoScript mistakes System Optimization - Reduction in response sizes (faster loading) - Removed 10 outdated tools for context performance - Fixed dynamic pagination issues XanoScript Capability - Implemented and enhanced function call syntax issues - Resolved Raw XanoScript API parameter formatting problems - Corrected "Unknown" function ID errors --- These updates are automatically available to all users!