{"resourceId":"servicenow-brazil-ga-kickstart-mcp-ai-supervision-20261105","versions":[{"version":"external-16d5cf92acd7274c233434fbec2d2b7f2bc21143f658c89d340aa33f3e976b01","resource":{"id":"servicenow-brazil-ga-kickstart-mcp-ai-supervision-20261105","title":"Kickstart Your ServiceNow Brazil Release Guide (Part 1 of 4)","organization":"ServiceNow (Community article by ServiceNow employee)","sector":"Enterprise platform release management; applies to all ServiceNow customers including public sector","geography":"Global","publishedAt":"2026-11-05 (posted ~10 hours before retrieval; marks Brazil GA)","publicationDate":"2026-11-05","eventDate":"2026-11-05","sourceName":"ServiceNow Community (Upgrades and Patching blogs)","sourceLabel":"Vendor employee upgrade/release guide","sourceUrl":"https://www.servicenow.com/community/upgrades-and-patching-blogs/kickstart-your-servicenow-brazil-release-guide-part-1-of-4/ba-p/3617254","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","data-security","operating-model"],"finding":"Brazil reached General Availability on 2026-11-05. The kickstart guide frames Brazil as moving from working alongside AI to supervising autonomous AI, opening governed actions to AI agents through MCP servers. It warns MCP servers are multiplying across ITSM, ITOM, SPM, HRSD and Process Intelligence (CMDB and Service Mapping in Controlled Availability), and that Platform Owners must decide which AI clients may connect before enabling them. Legacy LLM models are no longer selectable for new AI skills, agents or agentic workflows. Catalog-role ACL removals on request tables and other access changes require pre-upgrade testing; many production upgrades are expected in December.","sledRelevance":"Why-now: Brazil GA day. Agencies and universities on ServiceNow must plan MCP client allow-lists, AI model migration off legacy LLMs, and request-ACL regressions before December production upgrades. No SLED-specific deployment metrics; guidance is vendor upgrade advice.","evidence":"Vendor-employee community kickstart post for Brazil GA. Operational claims (MCP availability, legacy LLM restriction, catalog ACL changes) are stated as release facts but not independently verified against full product release notes in this edition.","architectureImplications":"More product MCP servers become available for external AI clients; CMDB/Service Mapping MCP still Controlled Availability. Build Agent enablement and Lux UI adoption are separate optional tracks.","governanceImplications":"Platform Owners need an explicit decision process for which AI clients may connect to each MCP server and who may use Build Agent before users discover it.","securityPrivacyImplications":"Expanding MCP surface increases agent tool risk if clients are enabled without allow-lists; Vault Console default sensitive-data alerts affect work-note handling. Legacy model cutover for new agents needs inventory of existing published assets that may continue on older models.","caveats":"Vendor upgrade guide; full PREPARE impact matrix linked as 'coming soon' in places; not a measured SLED outcome study.","streamIds":["servicenow"],"roles":{"sales":"Use Brazil GA as an upgrade-governance conversation, not a feature dump. For SLED customers already on ServiceNow, MCP server expansion and the legacy LLM cutover create a concrete readiness agenda before December production moves. Evidence is vendor guidance only, so sell a Brazil upgrade readiness workshop that covers MCP client decisions and catalog ACL regressions rather than promising autonomous IT outcome numbers from the release marketing materials.","engineering":"Engineers should inventory installed apps against Brazil notes, list every MCP server entitlement and allowed AI clients, identify agents still bound to legacy LLMs for new builds, and regression-test sc_request and sc_req_item access after catalog-role ACL removals. Treat CMDB and Service Mapping MCP as Controlled Availability only. Pilot Lux solely in sub-production first whenever customized portals or workspaces exist in the estate.","delivery":"Delivery work is a Brazil PREPARE sprint covering the change-impact matrix, MCP allow-list decisions, legacy-model inventory, request ACL user remediation, and sub-production upgrade tests. Interpretation: acceptance means completed test evidence before any production cutover. The platform owner leads with security and catalog owners as named co-sponsors. Primary risk is enabling MCP clients without allow-lists or breaking request access for catalog-only roles."},"roleDetails":{"sales":{"customerProblem":"Public-sector ServiceNow customers face a Brazil GA upgrade with expanding MCP/AI surfaces and access changes without a clear readiness plan.","stakeholders":["ServiceNow platform owner","CISO","Service catalog owner","Agency CIO"],"discoveryQuestions":["When is your Brazil production upgrade planned?","Which MCP servers are you entitled to enable?","Which AI clients could connect today?","Who still relies only on catalog roles for request access?"],"valueHypothesis":"A structured readiness workshop may reduce upgrade regressions and ungoverned MCP exposure.","potentialEngagement":"Brazil upgrade readiness assessment focused on MCP, ACL and AI-model cutover.","unsupportedClaims":["Brazil autonomous AI outcomes are proven in SLED","All MCP servers are generally available","Legacy models stop working for existing published assets"]},"engineering":{"fit":"Fits any ServiceNow customer planning Brazil upgrade who uses or will use AI agents/MCP.","architectureIntegration":"Product MCP servers (ITSM/ITOM/SPM/HRSD/Process Intelligence; CMDB/Service Mapping CA) plus Otto naming and optional Lux UI.","prerequisites":["Target Brazil release notes","Entitlement check per MCP server","Sub-production instance"],"constraints":["CA for some MCP servers","December upgrade congestion","Deprecations require remapping"],"security":"Decide AI-client allow-lists before enabling MCP; remediate request ACLs; review Vault Console sensitive-data alerts.","proofOfValue":["MCP inventory with allow-list decisions documented","Request ACL regression tests pass","New agents not selecting deprecated legacy models"]},"delivery":{"work":"Run PREPARE checklist: MCP, ACL, model, Lux and deprecation tests in sub-production.","dependencies":["Release notes","Security approval","Catalog owner user remediation"],"ownership":"Platform owner with security and catalog co-owners.","skillsAdoption":"Train admins on MCP controls and Otto naming changes.","governanceCheckpoints":["MCP client approval","Upgrade go/no-go with test evidence","Build Agent access decision"],"acceptanceCriteria":["Proposed: 100% entitled MCP servers have allow-list decisions","Proposed: zero known catalog-role request access breakages in test"],"risks":["Enabling MCP without client controls","Catalog ACL lockouts","Incomplete legacy-model inventory"]}},"retrievedAt":"2026-11-06T04:08:00Z","enrichedAt":"2026-11-06T04:14:10Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Upgrade testing load rises for platform, security and service-catalog owners; December upgrade wave compresses skill preparation.","procurementImplications":"Confirm product-tier entitlements for each MCP server before enabling; Controlled Availability items may need separate enrollment.","operatingModelImplications":"Shift from ad-hoc AI enablement to supervised autonomous AI with pre-upgrade access/MCP checklists and named owners for test evidence.","sourceVerification":{"openedUrl":"https://www.servicenow.com/community/upgrades-and-patching-blogs/kickstart-your-servicenow-brazil-release-guide-part-1-of-4/ba-p/3617254","referenceExcerpt":"ITSM, ITOM, SPM, HRSD and Process Intelligence now offer MCP servers (CMDB and Service Mapping in Controlled Availability).","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}