Earl's back but it's still Travis' show. DEAL WITH IT EARL Part 1 was... a learning experience. 🍿 After a minor fight with AI-generated code, a ZBooted instance, and pivoting on the fly from Subflows to Scripted REST APIs, Travis is BACK (and still squatting on Earl’s stream) to finish what we started: giving Claude actual power over a ServiceNow Knowledge Base via Model Context Protocol (MCP). In Part 2, we’re taking our basic draft-creation setup and turning it into a real, functional workflow. We'll fix the field-mapping blunders, test reading and updating articles, and see if we can push this MCP server past simple "create" calls into true knowledge management. 🎯 What We’re Covering in Part 2: Fixing the Plumbing: Correcting our payload mappings so Claude actually writes to the right fields (RIP text vs. article body). Expanding Tool Capabilities: Adding GET and UPDATE tools so Claude can read existing KB articles and edit them live. Troubleshooting MCP Schema Sync: Dealing with schema updates, parameters, and keeping Claude in sync with ServiceNow. The Human-in-the-Loop Strategy: How to structure AI permissions safely so Claude doesn't rewrite your entire KB unsupervised. Bring your questions, drop your own MCP experiments in the chat, and let’s see if we can get this running cleanly before Earl comes back and revokes Travis's stream key. 🔔 Subscribe for more ServiceNow developer streams & live coding chaos 💬 Chat live: Drop your MCP, REST API, or Claude integration questions below 👋 Leave a comment: Let Earl know if Travis should be allowed back for Part 3!