Before a renewal call, an account manager checks HubSpot for the deal and contacts, the help desk for open tickets, and asks finance whether the customer is current. After the call, they go back to HubSpot to update the deal. Every step is small; together they are why preparation gets skipped and records go stale.
They already use Claude or ChatGPT for everything else. The question IT asks is how to let the assistant into HubSpot and the ERP without handing it a master key.
What it takes to say yes
- The assistant gets only the tools it needs: read invoices, read and update deals, no delete.
- No HubSpot token or ERP password pasted into a prompt.
- IT can see who uses it and what each call did.
- The same setup works for Claude, ChatGPT and in-house agents.
How engini makes it work
You create an engini MCP server that exposes only chosen connections and tools, for example read companies, deals and tickets in HubSpot, update deals, and read invoices in NetSuite. People add it to Claude or ChatGPT and sign in through engini over OAuth. engini shows who uses each MCP server and records every run under the user who triggered it.
engini acts with the permissions of the connected account. For each person to act as themselves in HubSpot, each needs their own connection; one shared address where every employee signs in as themselves is not offered. For in-house agents on the SDK, CLI or REST API, a toolset scopes the calls, enforced on the server.
HubSpot
NetSuite