Two sign-in connections for AI assistants: everyday work with a short list of tools, or setting up, running and auditing the whole workspace.
Your AI assistant can work in Karmaflow.ai as you. You sign in with your own Karmaflow.ai login, choose the workspace, and allow what the assistant may do. From then on it acts with your role's permissions, only while you are a member of the workspace, and everything it changes is recorded as yours, "via" the assistant ("Pat Example via Claude").
There are two addresses to connect to. They use the same sign-in and the same safeguards; they differ in how much of the workspace the assistant can reach.
| Everyday connection | Workspace connection | |
|---|---|---|
| Address | https://mcp.karmaflow.ai/mcp |
https://mcp.karmaflow.ai/mcp/workspace |
| Tools | About 30: contacts, deals, tasks, notes, meetings, helpdesk tickets, documents, analytics tabs | Every tool your role allows, over 200: the everyday ones plus agents, orchestrations, knowledge, sent emails and texts, calls and chats, approvals and audit, spend, inventory, jobs, websites |
| Built for | Day-to-day work with a deliberately small reach | Setting up, configuring, reviewing and auditing the workspace |
| Where you find it | The Karmaflow.ai apps listed in assistant directories, or added by hand | Added by hand as a custom connector or custom app |
| Orientation | The assistant is told how records and permissions work | The assistant is told to read get_workspace_guide first: what this connection may do, which tools do what, and the order to set up an account in |
flowchart TD
Q{What will the assistant do?} -->|Look things up, log notes, move deals, answer tickets| E[Everyday connection<br/>mcp.karmaflow.ai/mcp]
Q -->|Build agents and orchestrations, curate knowledge, review and audit| W[Workspace connection<br/>mcp.karmaflow.ai/mcp/workspace]
E --> L[Your role, the workspace's AI access settings and what you allowed decide what it may do]
W --> L
These are examples. Every business divides the work differently, and the same person may want one connection for some days and the other for others.
The everyday connection suits people whose work is customers and records, where a small, predictable set of tools is the point:
The workspace connection suits the people who set the workspace up, keep it running and watch over what the AI does:
get_agent_promotion_status, and promoting the change when it is right.Nothing here grants extra rights. On either address the assistant can do only what three things allow together:
A workspace admin's own access is never narrowed by the AI access setting. Their role already allows everything.
You need a Karmaflow.ai login in the workspace, and the workspace's sign-in connections switched on. They are on unless a workspace admin turned them off. You do not need an API key.
Claude
ChatGPT
Gemini
Gemini connects as a custom app. Google offers custom apps to personal Google accounts (not work or school accounts), for people 18 or over in the US, in English, with Gemini History on.
Gemini asks you to confirm each action that changes data. To make sure a prompt uses Karmaflow.ai, type @ and pick it.
The address is fixed when you connect: an assistant connected to the everyday address keeps the everyday tools. To change, remove the connection and connect again to the other address.
You keep one connection per assistant and workspace. Where an assistant identifies itself the same way for both addresses, as Claude does, connecting to the second ends the first.
promote_agent makes them live. Orchestrations are saved paused, and switched on once they validate. Prompt components go live when pushed. Proposed knowledge is a draft unless your workspace's AI autonomy settings let it publish.Email signatures, inviting users and changing roles, phone numbers and sending domains, and organisation settings (business profile, time zone, business hours, notification routing) are set in the app for now.
The assistant says to reconnect to allow something. You did not allow that area when you connected. Remove the connection and connect again, allowing it on the consent page.
A tool you expected is missing. Your role does not include it, or the workspace's AI access for that area is None for your role (or Read for a tool that changes things). Ask a workspace admin. On the everyday address, the tool may simply not be in its short list: use the workspace address.
The consent page says your role allows none of what the assistant asks for. The workspace's AI access for external AI agents is None in every area your role uses, or sign-in connections are off. A workspace admin can change either.
Gemini shows no Add a custom app. Your Google account or location is outside Google's current limits (above).