Connect
Tools
Tools give your agents actions they can take, such as sending an email, adding a row to a spreadsheet or posting a message in Teams. Connect a ready-made integration, bring your own API, or plug in an MCP server, then attach the tool to any agent. Open the page from Connect → Tools in the left menu.
1.Find a tool
The tabs at the top sort the tools, and each shows how many it holds:
| Tab | What it shows |
|---|---|
| Tools | The ready-made integrations you can connect |
| MCP | The MCP servers you’ve added |
| Custom | The tools you’ve built from your own APIs |
| Connected | The tools you’ve connected and can attach to agents |
Type in Search tools to find a tool by name, and select the refresh button to reload the list. Select Learn more beside the title for a short explanation of tools.
Each card shows the tool’s name, what it does and a tag.
2.Tool tags
A tool’s tag tells you what kind of tool it is and where it comes from, so you can quickly see how it will behave in a workflow.
| Tag | What it means |
|---|---|
| Native | A built-in tool provided by Studio itself, such as date and time utilities, HTTP requests, calculators, access to workflow state, or integrations Studio manages. Native tools need little setup and run directly inside Studio. |
| Template | A prebuilt starting point for a common task, so you don’t have to build it from scratch. You customize it for your use, for example by connecting it with an access token from that service. |
| Custom | A tool you created yourself |
| MCP | A tool provided by an MCP (Model Context Protocol) server |
| Subworkflow | Another workflow that agents can call as a tool |
| Connected or Integration | A tool backed by an external app or API |
3.Ready-made tools
The Tools tab includes integrations for:
| Category | Tools |
|---|---|
| Gmail, Outlook, Email (SMTP) | |
| Files and documents | Google Drive, OneDrive, SharePoint, Notion, Confluence |
| Spreadsheets and databases | Google Sheets, Excel Online, Airtable |
| Calendars | Google Calendar, Calendly |
| Tasks and projects | ClickUp, Todoist, Asana, monday.com |
| Messaging | Microsoft Teams, Slack, Discord, Telegram, WhatsApp, Twilio SMS, Twitter / X |
4.Add your own tool
Select + New at the top right and choose the type of tool to add: a custom tool built on your own API, or an MCP server. Custom tools appear in the Custom tab, and MCP servers in the MCP tab.
Add a custom tool
A custom tool lets an agent call your own API, described by an OpenAPI specification.
Fill in the form:
- Name: A name for the tool, such as “Weather API”.
- Base URL (optional): The address of your API. It overrides the server named in the spec.
- Description: What the API does. The agent reads it to decide when to call the tool, so be specific.
- OpenAPI spec: Paste your OpenAPI 3.x specification, in JSON or YAML. Select use example to see a sample.
- Authentication: How the tool signs in to your API: None, Bearer token, API key (header), Basic (username:password) or Static query param(s). Choose None if the API doesn’t need it.
Select Preview to check your spec. Studio lists the operations it found, such as 1 operation found: GET search /search. Each operation is an action the agent can call.
Select Add tool.
Connect an MCP server
An MCP server gives an agent a set of tools hosted elsewhere.
Fill in the form:
- Name (optional): A name for the connection.
- Server URL: The server’s address, such as
https://…/mcp. - Auth: How Studio signs in to the server: none, bearer or header.
- Bearer token: The token to use, if you chose bearer.
- Header name and Header value: The
header to send, such as
X-API-Keyand its value, if you chose header. - Use this connection by default for MCP Server blocks: Tick this to have new MCP Server blocks in workflows use this connection.
Select Add connection.
5.Attach a tool to an agent
Open the agent and go to its Tools section.
Select Add tool and choose the tool.
Attach the credentials the tool should use.
For a tool that sends, changes or deletes something, turn on approval. Each time the agent wants to use the tool, a request goes to Approval Flows, and the agent waits until it is approved.
The agent decides when to use each tool, based on its instructions and the task.