Organization Tools

The Tools page (/admin/tools) brings together the external capabilities an organization can offer its agents. It manages integrations from the Composio catalog, HTTP/API tools that call your own endpoint, and MCP servers that publish a set of tools.

Activating a tool for the organization does not add it to agents automatically. Activation defines what can be used; each agent receives only the tools, accounts, and actions selected in its own configuration.

Access and permissions

The route requires View tools. The permission contract is:

• View tools: inspect integrations, accounts, and settings;
• Create and edit tools: activate and connect integrations, edit actions, and create or change HTTP/API tools and MCP servers;
• Delete tools: remove integrations and custom tools.

Current permission limitation

Some account and selection actions are still displayed — and may be accepted — for members who only have View tools. Until the product is corrected, grant this permission only to people authorized to manage integrations. A read-only user should also avoid the checkboxes in the list, which can cause an interface error.

How the list is organized

Everything lives in a single list, with a search box at the top that filters by name. Your organization’s tools come first, in bands showing how many each one holds:

• Connected: active, authenticated integrations, ready to use;
• Disconnected: activated integrations that lost their authentication or have not received it yet — a newly activated tool shows Awaiting authentication;
• Available: the rest of the catalog released to your organization.

Custom tools sit above the list, under Custom Tools.

The list only shows integrations the platform has finished configuring. If a catalog integration does not appear, it has not been released to your organization yet.

Activate and connect a Composio integration

Activation and authentication are separate steps:

1. Use the search box to find the integration under Available.
2. Select its card to open Configure tool.
3. If more than one authentication method is available, choose the displayed method.
4. Click Activate. The integration moves to the top of the list.
5. Open the active integration and click Connect now.
6. When credentials are required, complete authorization or data entry on the secure page hosted by Composio. When finished, the browser returns to SquadOS and the account appears under Accounts.

Tools without authentication connect directly, without an external page. If the external flow is abandoned before completion, no new connected account is created.

Manage accounts

An integration can have several accounts, such as two Gmail addresses or two Slack workspaces. Open an active tool and find Accounts. Each row shows the account name and its active, pending, or error state.

From an account’s actions menu, you can:

• Rename it so the intended agent or team is clear;
• Reconnect it to replace the credential for that same account;
• Disconnect it to revoke the connection without removing the integration from the organization;
• Remove it to delete the account and remove its agent assignments;
• use Add account to connect another account for the same service.

Reconnect the correct account

Use Accounts → Actions → Reconnect on the account row. This flow preserves the account identity and its agent assignments. The general Reconnect button at the top of the tool has a known limitation and may create a parallel account.

Removing the entire integration also removes its agent assignments. Review the impact before confirming.

Limit available actions

An integration may expose many actions. On the active tool, use Edit actions to define which actions are available to the organization:

1. open the integration in the list;
2. click Edit actions;
3. select at least one action and save.

This selection is the organization’s upper limit. In each agent’s configuration, you then select only the actions that agent should use. When the organization does not define a list, every action published by the integration is available for selection on the agent.

Add the tool to an agent

After preparing the tool at the organization level:

1. open the agent and go to Tools;
2. choose Add tool;
3. select the integration, HTTP/API tool, or MCP server;
4. for Composio, choose the account and actions allowed for the agent;
5. for MCP, choose which discovered tools the agent can use;
6. save the agent and test a request that requires the tool.

An agent never receives every activated capability automatically. Prefer the smallest action set required for its role.

Custom HTTP/API tools

In the Custom Tools section, click New Tool and select HTTP / API Tool. The form lets you define:

• display name, internal name, and usage description;
• URL and GET, POST, PUT, PATCH, or DELETE method;
• no authentication, bearer token, API key, or custom-header authentication;
• parameters through the visual editor or JSON Schema;
• JSON body, headers, and fixed or AI-provided path and query values;
• a timeout from 1 to 300 seconds;
• optional conversation metadata and lead-identity injection.

Credentials are stored on the server and must not be written in descriptions, schemas, or public values. Use the test panel before saving.

Editing a tool already used by agents displays a warning. Removal may be blocked while agents are attached; remove those assignments first.

MCP servers

In New Tool, select MCP Server. Enter its name, description, usage instructions, URL ending in /mcp, authentication when required, and whether the lead identity may be sent to the server.

Click Connect & discover. SquadOS tests the connection and lists the tools published by the server. When adding the MCP server to an agent, select only the discovered subset that it needs.

Bulk actions

Checkboxes let you Activate several integrations at once, or Disconnect and Remove several that are already in the organization. The selection stays in the band where you ticked the first item: selecting under Available disables the checkboxes on your active tools, and the other way around — each action applies to one band only. The bar tracks item-by-item processing. These actions change organization integrations and should only be used by someone with the corresponding permission.

Quick troubleshooting

• Integration missing from the list: it may already be active, higher up, or the platform has not released it to the organization yet.
• Awaiting authentication: open the tool and use Connect now.
• Account in error: reconnect it from that account’s menu, not the general button.
• Tool missing from the agent: confirm that it is active for the organization, its account is connected, and its tool or action was added to the agent.
• MCP has no tools: run Connect & discover again and confirm the URL, authentication, and server availability.
• HTTP/API is failing: test the URL, method, authentication, parameters, body, and timeout in the tool form before testing through the agent.