Skip to main content
A Jaaxis MCP or CLI connection belongs to one organization. It can reach every agent there on which you have Assistant permission, including agents shared into that organization.

Choose access

During sign-in, use Choose an organization and approve the intended organization. The old full-account and selected-agent choices no longer apply. Assistant requires the agent’s Inbox, Training & Preview, and Connect & Settings permissions. Turning any of those off also turns Assistant access off. Later permission changes take effect without reconnecting. A connection does not gain access to agents in your other organizations. Name the target agent when requesting work; similar display names are not enough to assume the right target.

Change access

To choose a different organization, reconnect through your client’s Jaaxis sign-in flow. To change which agents are available inside the organization, ask a member with Members permission to update your permissions in Organization settings → Members. See Members and sharing for the permission controls. The organization owner always has full access.

What each connection can do

The remote MCP runs supported Jaaxis commands and reads authorized agent resources. It cannot edit an agent’s setup files. Use the Dashboard Assistant or the local Jaaxis CLI with a coding agent for configuration work. There is no Jaaxis Ask/Auto approval mode. External clients use their own permission controls. A permitted action may already be live when it returns; read the result before repeating it.

Who pays

Agent work uses the owning organization’s credits, including work on a shared agent. The Dashboard Assistant’s own AI work uses its chat’s organization. Credits are not pooled across organizations.

Two different MCP endpoints

  • https://api.jaaxis.com/mcp operates your authorized Jaaxis organization.
  • https://docs.jaaxis.com/mcp searches public help pages and cannot operate your organization.
Never paste tokens or third-party secrets into an AI prompt. Use Jaaxis secure fields. Removing access cannot undo messages already sent or changes already made.