App Directory
The Performance Hub AI Agent works inside the software your facility already uses. An administrator connects apps to an agent from the agent's Connected Apps screen in Performance Hub, and from that moment the agent can read from and act in those apps on your behalf. Connections are made per agent, and an app can have several accounts connected at once - for example, multiple inboxes or multiple calendars.
This page is the live directory of every app the agent can connect to. It refreshes automatically twice a week.
How the agent uses connected apps
Every connected app is exposed to the agent through MCP (Model Context Protocol), the open standard for connecting AI agents to tools. Each app publishes a set of tool specifications - the operations the agent can perform, what each one does, and the access it needs. The agent discovers these tools the moment an app is connected, and because discovery happens over MCP, new capabilities added to an integration reach your agent automatically - there is nothing to upgrade or reconfigure when an app gains new tools.
Connection types
Every app in the directory connects in one of a few ways. The badge on each app tells you which applies:
| Badge | What it means for you |
|---|---|
| Always included | Nothing to connect. The service is on for every agent and can be switched off individually. See Built-in Services. |
| One-click connect | A single sign-in from the agent's Connected Apps screen. Performance Hub manages the app registration, so there is nothing to set up first. Google Workspace and Microsoft 365 apps connect this way, individually or via the suite connect. |
| Bring your own OAuth app | You register an OAuth app with the vendor once (Performance Hub shows a step-by-step guide), then sign in through it. Required by vendors that do not allow shared registrations. |
| API key / token | Paste an API key or token from the app's own settings. Performance Hub walks you through where to find it. |
How connecting works
- An administrator opens the agent's Connected Apps screen in Performance Hub.
- They pick an app and either sign in (OAuth) or paste a key, depending on the app's connection type above.
- The agent discovers the app's tools over MCP and can use them immediately - no restart, no configuration.
A few things worth knowing:
- Connections are private to one agent. Connecting an app to one agent does not share it with any other agent in your facility.
- Multiple accounts per app are supported. Connect two inboxes and the agent picks which account to use for each action.
- Built-in services need nothing. They are available from the moment an agent is created - see Built-in Services.
- Disconnecting is immediate. Remove a connection and the agent loses access to that account at once.
What connecting costs
Connected apps are included with your agent subscription at no extra charge: there is no per-integration fee and no charge per tool call to a connected app.
A fair usage policy applies. If an agent's usage of a connected app reaches the app's rate limits, we may charge overage for the excess - and if that ever happens, we notify you automatically so it never comes as a surprise on an invoice.
For how agent usage itself is billed, see Pricing & Directories. To compare the AI models that power agents, see the Model Catalog.
Integration partners
Some integrations are provided through our partnership with Composio - you may see the Composio name on sign-in and approval screens when connecting certain apps.