How to govern every MCP server from one place
Most teams connect AI assistants and agents to business systems one vendor MCP server at a time. Each server ships its own permission model, most expose more tools than the job needs, and the logs live inside each vendor. In this Celigo Sessions launch, Chris Ferraro and Celigo CPO Matt Graney explain what MCP is, why vendor servers leave a governance gap, and how Celigo MCP management puts every MCP server, whether vendor-built, homegrown, or built on Celigo, behind one gateway with per-group tool access, rate limits, IP filtering, and a single audit trail. What you'll learn: ▸ What MCP (Model Context Protocol) is ▸ The difference between AI assistants and agents ▸ The three gaps vendor MCP servers leave open: over-permissioned defaults, no central audit trail, and shadow AI that IT never approved ▸ How to give sales, finance, and support different tool sets from the same NetSuite MCP server ▸ When to swap a vendor tool for a custom one ▸ What "least agency" means in practice ▸ A realistic first step: put every existing MCP server behind one gateway before changing anything else, so you get visibility and a kill switch on day one Live demos: proxying a vendor MCP server and narrowing its tools by user group, swapping in custom tools, and deploying an MCP server template from the Celigo marketplace. CHAPTERS 02:30 Where MCP fits in your AI workflows 04:00 What is MCP? A common language between AI and business apps 06:00 AI assistants vs. agents 08:00 Vendor MCP vs. custom MCP 11:00 Over-permissioned servers, scattered logs, and shadow AI 14:00 Two customers, same problem 14:57 An MCP gateway as one front door for AI access 17:00 What governance means: who calls what, which tools, how often, and the audit trail 22:00 Turning off vendor tools and supplying your own 24:00 Live demo: proxying a vendor MCP server and controlling tools by group 31:00 MCP templates in the marketplace 33:00 Coming soon: an MCP registry with an approval workflow 35:00 Find, control, build: how the pieces fit together 37:00 Faster rollout, lower audit burden, lower token costs 39:00 Standalone gateways and vendor servers vs. Celigo MCP management 40:28 Q&A: can you restrict Salesforce fields and objects? 42:14 How do you stop agents from going rogue? Least agency and guardrails 45:39 "MCP is AI's answer to APIs": why vendor servers are buyer beware 46:53 Does NetSuite role-based access still apply when you proxy? 48:24 How technical is this to set up? 50:37 What's the difference between MCP management and the gateway? 51:51 Rate limits, user quotas, and allowed/blocked IP addresses 53:37 Can you govern homegrown MCP servers? Yes, and where to start Vendor-built, homegrown, or built on Celigo: if it speaks MCP, you can govern it from one place. 🚀 Never miss Celigo Sessions: https://www.celigo.com/webinar_series/celigo-sessions/ 👉 Get a demo: https://www.celigo.com/request-a-demo/ 🔎 Learn more: https://www.celigo.com/platform/mcp-management/ #Celigo #mcpserver #MCPGateway #modelcontextprotocol #aigovernance #enterpriseai #shadowai #netsuite #ipaas #IntegrationPlatform