Questions teams actually ask.
Grouped for the people evaluating Hexa: the business and ops view, the technical and IT view, and the bridge, one technical person setting it up for a non-technical team.
Business & ops
Can I use my AI to automate a workflow?
Yes. Hexa connects your AI client to your real tools and runs the multi-step work end to end, then saves it as a reusable workflow your team can run with one sentence.
Will my AI automation still work without the person who built it?
Yes. A Hexa workflow lives in your organization, not one person's chat history. Teammates run it on their own accounts, so it does not evaporate when someone leaves.
How do I turn a one-off AI report into something my whole team runs every week?
Do it once in a conversation. Hexa captures it as a workflow in your voice and format; after that it is one sentence, for you and anyone you share it with.
Can non-technical teammates use it?
Yes. One technical person connects the tools once. Teammates click a link, sign in with their own account, and run the workflows. No JSON, no setup.
Is my data used to train models?
Hexa does not train models on your data. Content is processed only to resolve and run the tasks you invoke. See the Privacy Policy for sub-processors and data handling.
Technical & IT
Isn't this just MCP?
Hexa is an MCP server, the one that makes the rest unnecessary. Raw MCP is single-player and stateless: a config file per person, limited to tools that ship a server. Hexa is one endpoint for the whole team, turns any API into a tool, and remembers the workflows. See Skills vs MCP vs workflows.
Can I turn any REST API into an MCP tool without writing code?
Yes. Describe the API and the AI authors the capability; you build and host no server. Tools that already ship an MCP server connect directly. More on Connect anything.
How do you keep MCP credentials out of chat and out of git?
Credentials are entered out-of-band in the browser and held server-side. No key transits the chat, and there is nothing to commit to git. All access routes through one credential seam. See Security & governance.
Can a Claude Teams admin assign a connector to specific members?
Not in Claude today; it is an open feature request. In Hexa a connector is shared once but keyed per person, so each teammate connects with their own credential and acts as themselves. See Hexa vs Claude Teams.
What is the difference between a Claude Skill and a Hexa workflow?
A Skill shapes how the AI reasons; it holds no credentials, gates nothing, and leaves no audit trail. A Hexa workflow governs what the AI is allowed to do in your systems and records every action.
Does Claude's org Capabilities toggle control individual connectors?
It toggles whole capability classes on or off org-wide, and its network-egress allowlist explicitly does not apply to MCP connectors. Hexa governs the individual capability with an allow / ask / deny policy and a per-action audit trail.
Setting it up for a team
If I build a workflow for myself, can a teammate run it without seeing my credentials?
Yes. Share the workflow and they run it on their own credential. They never see yours; the approval gate and audit trail carry each person's own identity.
Can one technical person set up AI tool access for a whole non-technical team?
That is the intended path. The technical person connects the tools and authors the capabilities once; everyone else clicks a link and runs the workflows as themselves.
Which AI clients does Hexa support?
Claude (Desktop, Cowork, and Code) is fully supported today. Support for more MCP-capable AI clients is coming soon.
Still have a question?
Start free and see it on your own tools, or ask us directly.