Most platforms integrate with tools that were built to be integrated. Glove connects to those too — and to the closed, on-prem software your business actually runs on, the kind that never shipped an API. If your operation lives inside it, that's exactly where a shared execution layer belongs.
Glove holds its own state and record — the process runs here first. Integrations are how it reaches the rest of your tools, not what it's made of. Connect what you have; Glove doesn't depend on any of it to run.
Whatever the connection method, the model is the same: every system reads from and writes to a single process state. Glove isn't middleware shuttling data between tools — it's the layer they all coordinate through.
Modern tools connect over MCP — CRM, calendar, billing, docs, chat and voice. Glove Core calls them as bounded actions; you get the tool without handing the model the keys. Anything exposed as an MCP tool works on day one.
Your CRM is one of these tools — connect it if you have one; you don't need one to run.
Any system that can send an HTTP request can start or advance a process — a form submit, a Stripe webhook, an API call, a scheduled job. No conversation required; the event lands on the state like any other turn.
The closed, on-prem tool nobody wants to replace doesn't need to change. Glove sets up a local operator that works it the way your team does — opening the record, filing the report, checking the file — and Glove Core calls it over MCP like any other action. To your process, a fifty-year-old desktop app and a modern SaaS look identical: both are just tools the state can call.
However a tool connects — MCP, webhook or operator — nothing changes about how Glove treats it. The model proposes an action; Glove Core checks it against your rules and the current state; only then does it execute. A legacy operator can't do anything a policy wouldn't allow, same as any API call.
Google, Microsoft 365, WhatsApp, email, webhooks and web forms are connected. Salesforce and HubSpot are rolling out. Anything exposed as an MCP tool works on day one, and anything that can send an HTTP request can start or advance a process.
A local operator that performs the same actions a member of your team would inside your on-prem software: opening the system, navigating to the right screen, entering the data and reading back the result. Glove Core calls it over MCP like any other tool.
No. The operator works the software you already run, exactly as it is. There is no migration and no rip-and-replace.
The same action pipeline as every other tool. The model proposes an action, Glove Core checks it against your rules and the current state, and only then executes. Every action is logged in the same audit trail, and the operator is set up and validated with you before it touches anything live.
A tool with an MCP server or a webhook is a configuration step. A legacy operator is built per system and tuned to how your team works, which is why we roll it out vertical by vertical rather than promising a generic connector.
If it has an API or an MCP server, it very likely already works. If it doesn't, that's our specialty — tell us what your business runs on.