Connect an AI assistant to Biosphere

An AI assistant that supports custom MCP connectors can read your Biosphere business and prepare changes within the permissions you approve. Configure → AI connections gives you the address to connect, lists the applications you have connected and lets you revoke them. It also holds the Scout model setting.

Connect an assistant

1. Open Configure, then AI connections.
2. Under Remote MCP endpoint, select the Copy URL button.
3. In the other assistant, add a custom MCP connector and paste the address.
4. When the assistant sends you to Biosphere, sign in if asked. The Connect an MCP application screen shows the requesting application, the Business it will access and the Permissions it asks for.
5. Select the Authorize and return button. Biosphere sends you back to the assistant.

To stop instead, select Cancel connection.

What a connected assistant can do

• By default an assistant can only read. It can search your Knowledge documents and Biosphere help and read what your own access allows, such as catalog, inventory, contacts, orders, imports, background jobs and the audit log.
• With the listed proposal permissions, an assistant can prepare product edits, inventory counts, decisions about which existing record an imported record matches, or catalog item merges. The connect screen lists the permissions it asks for.
• Preparing a change does not apply it. Open its review in Biosphere, check the exact proposed values and consequences, then confirm or cancel it with your signed-in Biosphere account. Only confirmation applies that reviewed change; an assistant cannot confirm its own proposal. See Review prepared changes.
• An assistant cannot directly change records, send messages, use staff tools or reach another business. Your current access is checked on every request, including when you confirm a change.
• What the assistant reads is shared with it under that assistant’s own data policies.

Read permissions have names such as catalog:read. Optional proposal permissions are identity_proposals:write, catalog_proposals:write and inventory_proposals:write. Ordinary business-write permissions are not granted to connected assistants.

See and revoke connections

Connected applications lists each application with when it was connected, when it was last used and the access it has.

1. Select the Revoke access button beside the application.
2. Confirm with the dialog’s Revoke access button.

The application loses access to this business. You can connect it again later.

Choose the Scout model

Every active business has Scout. Scout model at the top of the page chooses how Scout produces new responses. Claude Sonnet 5.5 is the default; Claude Opus 5.5, OpenClaw, Muse Spark 1.3 and budget Gemini 3.1 Flash Lite are also available. Models marked Not configured cannot be chosen. Every model supports the same files, and a change applies to new responses. If Claude is unavailable, Scout uses Muse Spark 1.3 for that response. Your selected model stays the same.

Automatic import plans

Scout automatically prepares a draft plan when an import needs interpretation. Preparation waits in Background jobs and needs no enabling step. Review the plan in Inbox before approving its proposed changes. A failed plan offers Try again.

See the technical reference

Open Developer details at the bottom of the page for the list of Biosphere capabilities, with each one’s permission and inputs. Each connected application sees only the tools its own access allows.

What to know

• Calls from connected assistants appear in Agent activity.
• Biosphere cannot count the tokens an outside assistant uses.