Connect tools and integrations
Connect external services, HTTP APIs, and MCP tools to a Viber agent.
Tools let your agent do more than answer. They can read or update an external system, make an HTTP request, or call a tool exposed by a Model Context Protocol (MCP) server.
Open Build > Tools to manage these capabilities.
Choose the right capability
| Capability | Purpose | Viber location |
|---|---|---|
| Channel | Where people talk to the published agent. | Deploy > Channels |
| Integration | Actions in another service, such as creating a CRM record. | Build > Tools |
| HTTP Request | A custom request to an external HTTP API. | Build > Tools |
| MCP server | Tools exposed by a Model Context Protocol server. | Build > Tools |
| Credential | A secret that authorizes one of these connections. | The capability’s configuration screen or external authorization flow |
Channels and tools serve different purposes. A service available under Build > Tools is not automatically available as a deployment channel under Deploy > Channels.
Use the live catalog under Build > Tools to see the integrations, actions, and setup options currently available.
Connect an integration
- Find the service under Build > Tools.
- Add the integration.
- If Viber displays Configure, complete the required authorization or settings.
- Confirm that the integration is enabled before using one of its actions.
An integration that requires setup is not connected merely because it was added. Zero-configuration integrations can become enabled immediately; other integrations remain in Needs setup until configuration succeeds.
Disabling an integration preserves its configuration. Uninstalling it removes the connection and should be treated as a destructive action.
Tell the agent when to use a tool
A connected integration makes its actions available to the agent, but it does not make the agent call them automatically.
Reference the relevant action in Instructions or a Playbook, then describe when it should be used. A globally referenced action is available without a Playbook. An active Playbook adds its referenced actions to the global actions.
Test a tool
Test a tool before publishing the agent:
- Confirm that the integration is enabled and configured.
- Confirm that the relevant action is referenced in Instructions or a Playbook.
- Test a representative request in Preview or a flow test.
- Inspect the tool call, its inputs, and its result.
If the agent does not call the tool, check whether the behavior clearly describes when to use it. If the call fails, inspect the returned error and confirm the tool’s authorization and configuration.
HTTP Request tools
Use an HTTP Request when the agent must call an API that does not fit a catalog integration. Configure the method, URL, parameters, body, headers, and authentication in the HTTP Request editor.
Supported authentication options include no authentication, bearer tokens, basic authentication, and API keys.
MCP servers
Connect an MCP server when it exposes a set of compatible tools. Configure the server URL and its supported authentication under Build > Tools, then enable the individual tools the agent should use.
Protect credentials
Never paste API keys, passwords, one-time codes, or other secrets into the Vibe conversation. Enter them only in the relevant configuration or authorization flow.
Complete provider authorization and enter credentials only in the relevant tool configuration. Saved secrets are not read back into the editor. Leave an existing secret field blank when the UI indicates that the saved value should be preserved.