Can a ServiceNow AI agent reach outside the platform for help when it doesn't have the answer internally? In this episode, Sayan and Sujan answer that with a live build, not just a slide. We walk through registering an external MCP server directly in Studio, then build a resolution assist agent from scratch for an incident management use case: an agent that pulls incident context, reaches out to an external MCP server for documentation, the platform doesn't have and posts the result straight back into the incident's work notes. Along the way, we cover: • Registering an external MCP server in Manage MCP Servers, including OAuth 2.0 and API key authentication. • Building an agent with a mix of internal script tools and an external MCP tool. • How tool discovery works when ServiceNow connects to an MCP server. • A full live test, from incident context to external doc search to a posted work note. If you've been wondering what "ServiceNow as an MCP client" actually looks like in practice, this is the episode that shows you. 0:00 - Introduction: Can ServiceNow agents reach outside the platform? 1:32 - What MCP as client actually means 1:49 - Manage MCP Servers in Studio 2:11 - Registering an external MCP server 2:32 - Authentication: OAuth 2.0 vs API key 3:19 - The use case: resolution assist for support users 3:39 - Creating the agent 4:16 - Adding the first script tool 4:22 - Fetching incident details 4:48 - Setting the tool to supervised 5:19 - Adding the MCP tool and tool discovery 5:42 - Selecting Doc Search 6:03 - Posting results back to work notes 7:03 - Testing the agent 7:46 - Agent reasoning and query confirmation 8:34 - MCP tool invoked, retrieving external docs 9:31 - Posting the resolution to the incident