Chorus

Live

BASIC AUTH

MEETING INTELLIGENCE

AI

Every recorded call, transcript, and rep coaching note your team captures lives in Chorus. Chorus MCP gives your agent authenticated access to conversation data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Chorus account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Chorus
agent · Acme Q3
Run
Find calls where pricing came up in the past 7 days and summarize the objections.
S
chorus_search_transcripts
89ms
Sales intelligence agent
4 calls flagged. Acme: too expensive vs Globex. Initech: per-seat pricing pushback. Stark: needed annual prepay discount. Umbrella: budget cycle mismatch.
Sources: 4 calls, 3 reps, Oct 24 to Oct 31
chorusmcp
4 calls
18:29
Message Claude...

Tools your sales intelligence agent reaches for on Chorus, scoped per user.

CALL ANY TOOL
Search transcripts, surface topics, and pull AI-attributed insights from sales calls.
chorus_conversation_get
Get conversation
Retrieve a single Chorus conversation by ID, including transcript, tracker matches, participants, linked CRM account/deal, recording details, and engagement metrics.
Parameters
Name
Type
Required
Description
conversation_id
string
Required
Unique identifier of the conversation.
chorus_conversations_list
List conversations
chorus_engagement_get
Get engagement
chorus_engagements_filter
Engagements filter
chorus_team_get
Get team
chorus_teams_list
List teams
chorus_user_get
Get user
chorus_users_list
List users
chorus_users_search
Search users
Build your Agent
Drop the toolkit in, point it at the user, and your sales intelligence agent can use Chorus from the first run.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["chorus"], toolNames: ["chorus_calls_list", "chorus_call_get", "chorus_call_topics"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["chorus"], toolNames: ["chorus_calls_list", "chorus_call_get", "chorus_call_topics"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["chorus"], toolNames: ["chorus_calls_list", "chorus_call_get", "chorus_call_topics"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/chorus",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Chorus.
Search & recall
Copy the prompt
Copied
Find calls mentioning [keyword] this week.
Copy the prompt
Copied
List all calls with [account name].
Copy the prompt
Copied
Show transcripts where [objection] came up.
Copy the prompt
Copied
Which reps had the most calls this month?
Insights & summaries
Copy the prompt
Copied
Summarize the last call with [account].
Copy the prompt
Copied
Get topics from [call name].
Copy the prompt
Copied
Compare topics across calls with [account].
Copy the prompt
Copied
Find next-step commitments in [call].
Coaching & reporting
Copy the prompt
Copied
Which calls had highest engagement scores?
Copy the prompt
Copied
List coaching opportunities for [rep].
Copy the prompt
Copied
Show all calls where [competitor] was mentioned.
Copy the prompt
Copied
Rank reps by talk-to-listen ratio this week.
SEE HOW AUTH WORKS
Users authorize Chorus once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Chorus
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Chorus
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Chorus
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Chorus
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other sales intelligence agents and MCP connectors. Working code, live demos, fork what fits.
GTM and RevOps Teams
CRM AI agent
Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.
GTM and RevOps Teams
Sales call prep agent
Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.
GTM and RevOps Teams
Deal intelligence agent
Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Test other agents
Same per-user auth pattern across other sales intelligence agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Deal intelligence agent
Score Gong call risk with an LLM, cross-reference the Attio record, and DM each owner their at-risk deals in Slack.
SALES
Sales call prep agent
Read tomorrow's calls from Google Calendar, mine Granola notes and Attio history, and deliver each rep a prep brief in Slack.
GTM
CRM AI agent
Turn each Granola call transcript into a HubSpot record update, a drafted Gmail follow-up, and a Slack recap.
GTM
Competitive intelligence briefing agent
Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Coaching data loses rep attribution
A shared Chorus API key looks fine in a demo. In production, every call retrieved looks like it came from a service account. Audit logs break. Per-rep scoping breaks. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared bot API key
token = "chorus_api_shared_xxx"
audit → bot_service_account
rep_filter → broken

// scalekit · per-user
token = resolve(user_id)
audit → user_abc
scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Chorus today. Gong, Salesforce, HubSpot tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Chorus as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Chorus basic auth stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Chorus?
Yes. Pass a tool name filter to listScopedTools so the sales intelligence agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Chorus.

What happens when a user revokes Chorus access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Which calls can the agent search across?
Only calls the authorizing user can see in Chorus. Manager scope surfaces team calls; IC scope stays per-rep. Recording permissions and CRM contact scope all apply at every search.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""chorus"": {
""url"": ""https://mcp.scalekit.com/chorus"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.chorus]
url = ""https://mcp.scalekit.com/chorus""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""chorus"": {
""url"": ""https://mcp.scalekit.com/chorus"",
""type"": ""http""
}
}
}