Tools and integrations (builder)

Configure what an agent can call — built-in tools, internal tools, Composio actions, and MCP servers.

Admins only. Members can run and observe; only admins can edit.

The Tools section of the builder is where you pick what the agent can call. Four categories: built-in, internal, Composio, and MCP.

The four categories

Category	What it is	Configured by
Built-in	Tools shipped by Opisense (e.g., `search_kb`, `read_file`, `search_org_contacts`).	Enable / disable per agent.
Internal	First-party tools attached via the Add tool dialog.	Per-agent selection.
Composio	Actions from connected Composio integrations.	Per-agent picker across connected integrations.
MCP	Tools exposed by connected MCP servers (Model Context Protocol).	Per-server picker.

Built-in tools are toggleable per agent. Disabling a built-in keeps the agent focused on its role. All four catalog agents start with the same built-ins enabled; you can prune them when building or editing a custom agent.

Adding internal tools

The Add tool dialog lists every internal tool registered in the org. Select one to add it to the agent's draft. The activity log records the change.

Composio actions

For each connected Composio integration, you can pick specific actions to expose to the agent. Only active connections appear in the picker — disconnected or expired integrations are filtered out.

MCP servers

MCP (Model Context Protocol) servers connected to your org expose sets of tools. For each server, you can select which tools the agent should see. This is useful for narrowing a broad server to only the tools relevant to the agent's role.

How the addable-tools catalog works

The addable-tools catalog is fetched from the Mastra editor route when the editor loads. It refreshes automatically when you toggle integrations. If a tool you expect isn't in the list, check /settings/integrations for the connection status.