Clarify MCP

Live

API KEY

CRM

Every contact, company, and relationship signal your team tracks lives in Clarify. Clarify MCP gives your agent authenticated access to CRM data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Clarify MCP 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.
Clarify MCP
agent · Acme Q3
Run
Find all contacts at Series B companies we haven't reached out to in 30 days.
S
clarify_contacts_list
79ms
CRM agent
12 contacts at 4 Series B companies with no activity in 30+ days. Top accounts: Nexus AI (3 contacts, last touch 42d), Orbit Data (3 contacts, 38d), Pulse Labs (3 contacts, 35d), Drift Works (3 contacts, 31d).
Sources: 12 contacts, 4 companies
clarifymcpmcp
12 contacts
18:29
Message Claude...

Tools your crm agent reaches for on Clarify MCP, scoped per user.

CALL ANY TOOL
List contacts and companies, create and update records, add notes, and track relationship activity.
clarify_contacts_list
List contacts
List contacts with search and filter options.
Parameters
Name
Type
Required
Description
query
string
Optional
Search query
limit
integer
Optional
Max contacts
clarify_contact_get
Get contact
clarify_contact_create
Create contact
clarify_companies_list
List companies
clarify_company_get
Get company
clarify_note_create
Create note
Build your Agent
Drop the toolkit in, point it at the user, and your crm agent can use Clarify MCP 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: ["clarifymcp"], toolNames: ["clarify_contacts_list", "clarify_contact_get", "clarify_contact_create"] },
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: ["clarifymcp"], toolNames: ["clarify_contacts_list", "clarify_contact_get", "clarify_contact_create"] },
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: ["clarifymcp"], toolNames: ["clarify_contacts_list", "clarify_contact_get", "clarify_contact_create"] },
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/clarifymcp",
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 Clarify MCP.
Search & recall
Copy the prompt
Copied
Find contacts at [company name].
Copy the prompt
Copied
List companies in [industry] sector.
Copy the prompt
Copied
Search for [person name] in Clarify.
Copy the prompt
Copied
Which contacts have had no activity in 30 days?
Action & updates
Copy the prompt
Copied
Create a contact: [name], [email], [company].
Copy the prompt
Copied
Add a note to [contact]: [text].
Copy the prompt
Copied
Update the title of [contact] to [title].
Copy the prompt
Copied
Create a company: [name], [domain].
Pipeline & reporting
Copy the prompt
Copied
Which companies have no contacts?
Copy the prompt
Copied
Contacts added this week.
Copy the prompt
Copied
List all companies with deal value above [$amount].
Copy the prompt
Copied
Which contacts are at Series B companies?
SEE HOW AUTH WORKS
Users authorize Clarify MCP once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Clarify MCP
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
Clarify MCP
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
Clarify MCP
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
Clarify MCP
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 crm agents and MCP connectors. Working code, live demos, fork what fits.
GTM
CRM AI agent
Log calls, update opportunity stages, and surface stalled deals across HubSpot or Salesforce. No manual data entry.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
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.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// 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.
Clarify MCP today. Others 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 Clarify MCP 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 Clarify MCP api key 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 Clarify MCP?
Yes. Pass a tool name filter to listScopedTools so the CRM agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Clarify MCP.
What happens when a user revokes Clarify MCP 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.
Does the agent respect Clarify workspace member permissions?
Yes. Every call runs as the authorizing user with their Clarify role. Contact and company visibility, field access, and workspace scoping all apply. Cross-workspace data is denied at the source.
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"": {
""clarifymcp"": {
""url"": ""https://mcp.scalekit.com/clarifymcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.clarifymcp]
url = ""https://mcp.scalekit.com/clarifymcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""clarifymcp"": {
""url"": ""https://mcp.scalekit.com/clarifymcp"",
""type"": ""http""
}
}
}