Attention

Live

API KEY

CALL INTELLIGENCE

Every sales call, transcript, and AI insight your team captures lives in Attention. Attention MCP gives your agent authenticated access to call data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Attention 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.
Attention
agent · Acme Q3
Run
Which deals had competitor mentions in the last 7 days and what objections came up?
S
attention_insights_search
88ms
Call intelligence agent
3 deals flagged with competitor mentions. Acme ($120K): pricing objection vs Globex. Initech ($85K): feature gap on SSO. Umbrella ($60K): timeline concerns.
Sources: 3 calls, 2 reps, Oct 24 to Oct 31
attentionmcp
3 calls
18:29
Message Claude...

Tools your call intelligence agent reaches for on Attention, scoped per user.

CALL ANY TOOL
Search calls and transcripts, surface insights, and pull AI summaries from sales conversations.
attention_calls_list
List calls
List recorded calls with optional filters for rep, account, and date range.
Parameters
Name
Type
Required
Description
rep_email
string
Optional
Filter by sales rep email
account_id
string
Optional
Filter by account
start_date
string
Optional
ISO 8601 start
end_date
string
Optional
ISO 8601 end
attention_call_get
Get call
attention_call_transcript
Get transcript
attention_call_summary
Get summary
attention_insights_search
Search insights
Build your Agent
Drop the toolkit in, point it at the user, and your call intelligence agent can use Attention from the first run.
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: ["attention"], toolNames: ["attention_calls_list", "attention_call_get", "attention_call_transcript"] },
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: ["attention"], toolNames: ["attention_calls_list", "attention_call_get", "attention_call_transcript"] },
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: ["attention"], toolNames: ["attention_calls_list", "attention_call_get", "attention_call_transcript"] },
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/attention",
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 Attention.
Search & recall
Copy the prompt
Copied
Find all calls mentioning [competitor name].
Copy the prompt
Copied
List calls with [account name] this month.
Copy the prompt
Copied
Show me transcripts where [objection] came up.
Copy the prompt
Copied
Which deals had risk flags this week?
Insights & summaries
Copy the prompt
Copied
Summarize the last 5 calls with [account].
Copy the prompt
Copied
Get action items from [call name].
Copy the prompt
Copied
What objections appeared in calls this week?
Copy the prompt
Copied
Show coaching opportunities for [rep name].
Reporting & coaching
Copy the prompt
Copied
Compare win rates by objection type.
Copy the prompt
Copied
List reps with most competitor mentions.
Copy the prompt
Copied
Which calls scored highest on next-step clarity?
Copy the prompt
Copied
Show all calls where pricing came up.
SEE HOW AUTH WORKS
Users authorize Attention once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Attention
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
Attention
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
Attention
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
Attention
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 call intelligence agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
SALES
Sales call prep agent
Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Call insights attributed to a bot, not the rep
A shared Attention API key looks fine in a demo. In production, every call insight and coaching signal retrieved looks like it came from a service account. Rep-level attribution breaks. Scalekit resolves the actual user's token so every Attention action is attributed correctly.
// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Attention today. Gong, Chorus, Fathom 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
Frequently Asked Questions
Does the agent access Attention 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 Attention api key stored?
Can I limit what the agent is allowed to do in Attention?
What happens when a user revokes Attention access?
Which calls can the agent surface insights for?
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"": {
""attention"": {
""url"": ""https://mcp.scalekit.com/attention"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.attention]
url = ""https://mcp.scalekit.com/attention""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""attention"": {
""url"": ""https://mcp.scalekit.com/attention"",
""type"": ""http""
}
}
}