Overview
The Clari CoPilot integration lets users connect their Clari CoPilot account so Alysio can list users, topics, scoreboards, and calls, and retrieve call details (including optional audio/video signed URLs) on their behalf. Users can ask Alysio to list CoPilot users, topics, scoreboards with filters, calls with filters and pagination, and get details for a specific call—all in natural language. Authentication is not OAuth 2.0; an API Key and API Password (secret) are required in the connection form. Use claricopilot_list_user first when you need user IDs for filtering scoreboards or calls.
Supported capabilities / objects
- Users — List all users in Clari CoPilot (for use as filter IDs in scoreboards and calls).
- Topics — List topics with optional modified-time filters.
- Scoreboards — List scoreboards with pagination (skip, limit) and optional filters (time, rep ID, scorer ID).
- Calls — List calls with pagination and filters (user, attendees, topics, status, type, time, duration, sort); optional includeAudio, includeVideo, includePagination.
- Call details — Get details for a specific call by ID; optional signed URLs for audio and video (valid 4 hours).
Authentication
Method: Not OAuth 2.0. Clari CoPilot connection uses an API Key and API Password (secret). Users must obtain these from their Clari CoPilot account and enter them when connecting Clari CoPilot to Alysio (e.g. in the Clari CoPilot integration form). The MCP sends requests using the stored credential.
Redirect URI: Not applicable—Clari CoPilot connection does not use OAuth 2.0.
Required credentials (both)
- API Key — Enter your Clari CoPilot API Key (form field: API Key).
- API Password — Enter your Clari CoPilot API Password (secret). The form may label this as “API Password”; both key and password are required to authenticate.
Token handling
- The API Key and API Password are stored as part of the Clari CoPilot connection.
- The system uses them to authenticate requests to the Clari CoPilot API.
- Each user/tenant has their own credential; the MCP uses the appropriate credential so calls are isolated per connection.
- If credentials change (e.g. key rotated, password reset), the user must update the connection in Settings → Integrations.
- On disconnect, Clari CoPilot tools are unavailable until the user reconnects with valid credentials.
Credential justification
| Credential | Purpose |
|---|
| API Key | Identifies the application or user for Clari CoPilot API access. |
| API Password | Authenticates the request; required together with the API Key. |
Connection required: Users must connect Clari CoPilot in Alysio and provide both API Key and API Password before Clari CoPilot tools work. No OAuth 2.0 flow—credentials are entered in the Clari CoPilot integration form.
Credential security: Keep the API Key and API Password confidential. Rotate or regenerate them in Clari if compromised and update the connection in Alysio.
The Clari CoPilot MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.
| Tool | Description | Example user prompts |
|---|
claricopilot_list_user | Lists all users in Clari CoPilot; use returned user IDs when filtering scoreboards or calls. | ”List Clari CoPilot users”, “Who are the users in CoPilot?” |
claricopilot_list_topics | Lists topics with optional filters by modified time (filterModifiedGt, filterModifiedLt). | ”List CoPilot topics”, “Topics updated after last week.” |
claricopilot_list_scoreboards | Lists scoreboards with pagination (skip, limit) and optional filters (time, rep ID, scorer ID); use list_user for user IDs. | ”List scoreboards for this rep”, “Show recent scoreboards.” |
claricopilot_list_calls | Lists calls with pagination and filters (user, attendees, topics, status, type, time, duration, sort); can include audio/video URLs and pagination metadata. | ”List my Zoom calls from last month”, “Calls for user X with audio links.” |
claricopilot_get_call_details | Gets details for a specific call by ID; optionally includes signed URLs for audio and video (valid 4 hours). Use list_calls to find the call ID. | ”Get details for call 12345”, “Call details with recording link.” |
App Behavior
- API calls are made on-demand only when the user asks something that requires Clari CoPilot data (e.g. users, topics, scoreboards, calls, call details). There is no background sync; each request triggers the relevant Clari CoPilot API call using the user’s stored credential.
Example flow
- User asks: “List scoreboards for Jane and show the last 20.”
- Alysio routes the request to the Clari CoPilot MCP.
- The MCP may call
claricopilot_list_user to resolve Jane’s user ID, then claricopilot_list_scoreboards with filterScorerId or filterRepId and limit=20 (and skip=0).
- The request is sent using the user’s stored API Key and API Password.
- The MCP returns the scoreboard list; Alysio presents the results in chat.
Troubleshooting
Common issues
- Clari CoPilot not connected — User has not completed the connection form with API Key and API Password. Fix: In Settings → Integrations, connect Clari CoPilot and enter API Key and API Password (both required).
- 401 Unauthorized — API Key or API Password invalid or revoked. Fix: In Clari CoPilot, verify or regenerate the API key and password, then update the connection in Alysio.
- Filter by user fails — Scoreboard or call filters expect user IDs, not emails. Fix: Call
claricopilot_list_user first and use the returned user IDs (e.g. filterRepId, filterScorerId, filterUser) in list_scoreboards or list_calls.
- Call details need call ID — get_call_details requires a call ID. Fix: Use
claricopilot_list_calls to find the desired call, then call claricopilot_get_call_details with that ID. For audio/video links, set includeAudio or includeVideo to true; URLs are valid for 4 hours.
Support
