From my experience building Dollarland (dollar-land.vercel.app) with a LangChain/OpenAI backend, it usually depends on how the tool-calling schema is defined in the manifest.
In most current implementations, plugins act as an abstraction boundary. The main agent usually sees the 'Plugin' as a single tool (a 'super-tool') and delegates the specific MCP calls to a sub-agent or a controller within that plugin.
If you expose every underlying MCP tool individually to the main agent, you run into 'Context Window Bloat' where the agent gets confused by too many options. Keeping them 'hidden' behind the plugin interface is actually better for agentic stability in a production environment.
From what I have seen, plugins usually act as an abstraction layer — the main agent interacts with the plugin, not each underlying MCP tool directly. It keeps things cleaner and easier to manage, especially when multiple tools are involved.
From my experience building Dollarland (dollar-land.vercel.app) with a LangChain/OpenAI backend, it usually depends on how the tool-calling schema is defined in the manifest.
In most current implementations, plugins act as an abstraction boundary. The main agent usually sees the 'Plugin' as a single tool (a 'super-tool') and delegates the specific MCP calls to a sub-agent or a controller within that plugin.
If you expose every underlying MCP tool individually to the main agent, you run into 'Context Window Bloat' where the agent gets confused by too many options. Keeping them 'hidden' behind the plugin interface is actually better for agentic stability in a production environment.
From what I have seen, plugins usually act as an abstraction layer — the main agent interacts with the plugin, not each underlying MCP tool directly. It keeps things cleaner and easier to manage, especially when multiple tools are involved.
I've recently started using Codex and installed Figma MCP. The outputs were really good. I achieved a 90% success rate, and I fixed the rest myself.