Plugin Architecture

A Plugin Architecture allows third-party code or capabilities to extend a core platform — without modifying the core itself. In AI, plugin architectures let LLMs invoke external tools, APIs, data sources, and computations. The pattern originated in browsers (Netscape plugins, browser extensions) and software (Photoshop plugins, IDE extensions) and has now reached AI broadly: OpenAI's GPT plugins (introduced March 2023, later evolved into GPTs and Actions), ChatGPT's tools, Microsoft Copilot plugins, Google Gemini extensions, Anthropic's MCP (Model Context Protocol), and Claude's tool use. Plugins enable LLMs to access real-time information (weather, stocks), perform computations (code execution, math), connect to enterprise systems (Salesforce, SAP, Workday), and chain into specialized capabilities. Risks include security concerns about plugin behavior, data leakage to third-party providers, and dependency on plugin reliability. AI governance, AI compliance, and AI risk management programs treat plugins as third-party AI components requiring vendor review — supporting responsible AI through controlled plugin authorization across enterprise AI deployments worldwide.

Centralpoint Has a Plugin Architecture for Tools and Skills: Oxcyon's Centralpoint AI Governance Platform extends through tools and skills across OpenAI, Gemini, Llama, and embedded models — all behind your firewall. Centralpoint meters every plugin call, keeps prompts and skills on-prem, and embeds plugin-driven chatbots into your portals via one JavaScript line.


Related Keywords:
Plugin Architecture,,