Previous: https://youtu.be/xlwypY2B5AM Next: https://youtu.be/aA6HymKtajI Full written series: https://devlink.sn/mcp-server-console-series Everything built so far means nothing until an AI client connects to it. Here I add a custom connector in Claude, run the OAuth flow, and pause on the consent screen, because that's the moment where trust actually gets established. 📘 Step-by-step directions and scripts to copy and paste: https://devlink.sn/mcp-server-console-series ## In this video - Adding a custom connector in Claude's settings - Pasting in the MCP server URL, OAuth client ID, and client secret - Running the OAuth flow against the ServiceNow instance - Why the consent screen and the Application Registry behind it answer the question "what can this AI actually do?" - The first place to look when something isn't working the way you expect ## Timestamps 00:00 - Connecting an AI client 00:21 - Claude settings and Connectors 00:32 - Adding a custom connector 00:45 - URL, client ID, and client secret 01:04 - Running the OAuth flow 01:27 - Why the consent screen matters 02:00 - Connected #ServiceNow #MCP #AI #Claude #OAuth