Quickly surface conversations, scorecards, playlists, and user details from your recorded Chorus meetings with reusable, MCP-powered nodes.
Chorus MCP unifies engagements, conversations, playlists, scorecards, and users into one searchable data source so your coaching and revenue workflows stay in sync.

​
What is Chorus MCP?

Chorus MCP generates a tailor-made node that speaks the Chorus API. Describe the data you need, and the AI creates a node that returns structured data ready for any workflow. Build once, reuse anywhere.

​
What Can It Do for You?

  • Search recorded meetings or calls with filters like date, duration, participants, and trackers
  • Pull rich conversation details for coaching or QA
  • Discover playlists for onboarding, enablement, or training
  • Review scorecards by recipient, reviewer, or initiative to monitor performance
  • List users with roles and team assignments for security and access audits

​
Available Tools

ToolWhat It DoesExample Use
Get MeGet authenticated user details including profile, permissions, and team assignments”Return structured data for the authenticated user including name, email, role, permissions, and team assignments”
Get EngagementsGet conversations or meetings with advanced filtering by type, duration, participants, dates, and tracker information”Search engagements within start date to end date for type meeting type, and return engagement id, title, start time, duration, and participants”
Delete EngagementDelete a specific engagement or conversation by ID”Using engagement id, delete the engagement and return deletion status”
Get ConversationFetch detailed conversation data by ID with customizable field selection”Using engagement id, fetch conversation details and return title, duration in minutes, participants, trackers, and recording URL”
Get PlaylistsFetch playlists with filtering by type, ownership, subscription status, and sorting options”Find playlists owned by owner email and return playlist id, name, type, and item count”
Get ScorecardsFetch scorecards with filtering by recipients, reviewers, initiatives, and submission dates”Find scorecards for recipient user email submitted between start date and end date, and return scorecard id, status, reviewer, and submitted date”
Get UsersFetch all users from Chorus with profile information, roles, and team assignments”Return structured data for users including name, email, role, and team assignments”

​
How to Use

1

Create Your Chorus MCP Node

Go to your node library, search for Chorus, and click “Create a node with AI”
2

Add Your Prompt

Drag the Chorus node to your canvas and add your prompt in the text box. Use variables like date range, meeting type, or user email so the node is reusable.
3

Test Your Node

Run the node to view results. If everything looks good, keep going. If not, check the troubleshooting tips below.
4

Save and Reuse

Once your Chorus node works as expected, save it to your library and drop it into any future workflow.

​
Example Prompts

Here are some prompts that work well with Chorus MCP: Find Recent Meetings: 
Search engagements in `start date` to `end date` with type `meeting type`, and return engagement id, title, start time, duration, and participants as structured data
Get Conversation Details: 
Using `engagement id`, fetch conversation details and return title, duration in minutes, participants, trackers, and recording URL as structured data
Playlist Discovery: 
Find playlists owned by `owner email` and return playlist id, name, type, and item count as structured data
Scorecard Review: 
Find scorecards for recipient `user email` submitted between `start date` and `end date`, and return scorecard id, status, reviewer, and submitted date as structured data
User Directory Snapshot: 
Return structured data for users including name, email, role, and team assignments
Delete an Outdated Engagement: 
Using `engagement id`, delete the engagement and return deletion status as structured data
Start simple. First create a node to find engagements and return engagement IDs. Then create a second node to pull conversation details by ID. This keeps each step fast and easy to debug.

​
Troubleshooting

If your Chorus MCP node isn’t working as expected, try these best practices:

​
Keep Prompts Simple and Specific

  • Good: “Search for meeting title in date range and return engagement id and start time”
  • Less Efficient: “Find meetings in date range, summarize key points, and post to Slack”
For best results, break multi-step tasks into separate nodes. Chorus MCP works best with focused, single-action prompts.

​
Match What Chorus Can Do

  • Good: “Find scorecards for user email in date range and return scorecard id, status, and reviewer”
  • Less Efficient: “Find scorecards and write them to a Google Sheet”
Chorus MCP excels at retrieving structured data from Chorus. For writing to spreadsheets, combine it with Google Sheets Writer in your workflow.

​
Break Complex Tasks Into Steps

Trying to do everything in one prompt might cause timeouts and slow responses: 
Search for all engagements in `date range`, get each conversation's details, summarize takeaways, and email results to `recipient email`
Break this into smaller nodes:
1

Step 1: Get Engagements

Search engagements in date range and return engagement id, title, and start time
2

Step 2: Get Conversation Details

Using engagement id list, fetch conversation details and return title, duration in minutes, participants, and trackers
3

Step 3: Summarize Insights

Using conversation details, generate a short summary per engagement with the Ask AI node
Connect these nodes sequentially in your workflow. Outputs from each step become inputs for the next, keeping everything modular and maintainable.

​
Focus on Data Retrieval

Chorus MCP is great at getting information from Chorus. For analysis or content creation, connect it to other nodes. Example:
  • Good prompt: “Using engagement id, fetch conversation details and return title, participants, and duration”
  • Less Efficient: “Fetch conversation details and create a 3-bullet summary”
Use Ask AI for summaries or analysis, Gmail Sender for emails, and Slack Message Sender for Slack messages. Chorus MCP focuses on returning accurate structured data from your Chorus instance only.

​
Troubleshooting Node Creation

​
Need More Help?