Built-in plugins are precise: someone wrote and tested the connector. MCP is general: any compliant server exposes tools and resources an agent can call without Enverif shipping bespoke code.
Enverif supports both. Its MCP client and manager let you configure servers per workspace, with the transport, authentication model and exposed tools recorded alongside the connection.
We deliberately do not publish a catalogue of "built-in" MCP servers we have not built. A server is either configured by you, verified against a documented Enverif version, or listed as a community project — never presented as something it is not.
The practical guidance: use a built-in plugin where one exists, and MCP where you need reach into a system that Enverif does not connect to directly.
Put your first AI employee to work this week.
Start on Enverif Cloud, or clone the repository and self-host. Approvals are on by default either way.