Pre-built Agent-Ready Connectors
Browse and select from hundreds of pre-built tools in the Workbench, covering popular SaaS platforms like GitHub, Google Workspace, Jira, Asana, Notion, and more. These connectors are:Ready to Use
No configuration required, just select and enable
Production-tested
Built and maintained by the xpander connector generator agent.
Regularly Updated
Keep pace with API changes and new features
You can also generate your own connectors by providing an OpenAPI/Swagger specification. This allows you to create private connectors for your internal APIs or custom home-grown tools.
MCP (Model Context Protocol) Integration
Connect tools to your agents using the Model Context Protocol:🔌 Remote MCPs
Use a remote MCP to connect your agent to an MCP server hosted externally - either in your own infrastructure or by a SaaS provider. How it works: You provide a URL to a running MCP server and select which tools to attach to the agent. xpander will connect to it at runtime and allow your agent to call the selected tools.🧱 Local MCPs
Use a local MCP to run the MCP server directly alongside your agent within the xpander cloud environment. How it works: You define the command that runs the MCP server process. xpander launches it as part of the agent’s lifecycle, connects to it automatically, and provides the tools from the MCP server to the agent.Custom Tools
Register your own functions directly in the agent’s code using the@register_tool
decorator for complete control over tool behavior and integration.
Once you configure any of these options in the UI or code, the tools become available to your agent automatically through the backend configuration.
agno_agent.tools
property contains all available functions, seamlessly combining cloud-managed connectors with your local custom tools.
Authentication
xpander provides flexible authentication options for your connectors. You can choose between:- Integration user authentication - Agents that use this connector use the same predefined credentials (useful for shared services)
- End-user authentication - Each user authenticates individually when the agent needs to access their data (supported on Slack agents)
- No authentication - Use connectors that don’t require authentication

Tool Dependencies
Tool dependencies control the execution order of your agent’s tools. When you set a dependency, Tool B will only run after Tool A completes successfully, while Tool A can still run independently. This is useful for workflows where one tool needs data from another or if you want to make sure a tool never runs before a different tool is invoked. How to set dependencies:- Click the top connection point of the tool that must wait (Tool B)
- Drag the line to the bottom connection point of the tool it depends on (Tool A)
- The dependency will be created automatically
Send Email
tool to only be available after the Calendly Get Availability Schedule
tool is called.

Tool Scheme Advanced Tab
Individual tool details and configurations are available in the Workbench by clicking the Settings button next to each tool.The Details tab shows the original, generated function calling description that defines the tool’s purpose and behavior. This serves as a reference for the tool’s intended use.
This information is especially useful when you’re working with multiple similar tools and need to understand the exact purpose of each one.
