Intercom

Live

OAUTH 2.0

CUSTOMER SUPPORT

Every customer conversation, contact, and support ticket your team handles lives in Intercom. Intercom MCP gives your agent authenticated access to customer data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Intercom 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.
Intercom
agent · Acme Q3
Run
List all open high-priority conversations unassigned for more than 4 hours.
S
intercom_conversations_list
79ms
Support agent
7 open conversations unassigned 4+ hours. Top: billing dispute (6h, $2K account), login loop bug (5h, enterprise), API key reset (4.5h), data export failure (4.5h), onboarding stuck (4h).
Sources: 7 open conversations, unassigned
intercommcp
7 conversations
18:29
Message Claude...

Tools your support agent reaches for on Intercom, scoped per user.

CALL ANY TOOL
List and reply to conversations, search contacts, assign tickets, and retrieve full message history.
intercom_conversations_list
List conversations
List Intercom conversations with status, assignee, and tag filters.
Parameters
Name
Type
Required
Description
state
string
Optional
State: open, closed, snoozed
assigned_to
string
Optional
Admin ID filter
tag_id
string
Optional
Tag filter
limit
integer
Optional
Max conversations
intercom_conversation_get
Get conversation
intercom_conversation_reply
Reply to conversation
intercom_contacts_search
Search contacts
intercom_contact_get
Get contact
intercom_conversation_assign
Assign conversation
Build your Agent
Drop the toolkit in, point it at the user, and your support agent can use Intercom 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: ["intercom"], toolNames: ["intercom_conversations_list", "intercom_conversation_get", "intercom_conversation_reply"] },
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: ["intercom"], toolNames: ["intercom_conversations_list", "intercom_conversation_get", "intercom_conversation_reply"] },
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: ["intercom"], toolNames: ["intercom_conversations_list", "intercom_conversation_get", "intercom_conversation_reply"] },
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/intercom",
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 Intercom.
Triage & escalation
Copy the prompt
Copied
List all open conversations unassigned for 4+ hours.
Copy the prompt
Copied
Find conversations from [account name].
Copy the prompt
Copied
Show me all conversations tagged [tag].
Copy the prompt
Copied
Which conversations are snoozed until today?
Action & replies
Copy the prompt
Copied
Reply to conversation [id]: [text].
Copy the prompt
Copied
Assign conversation [id] to [admin].
Copy the prompt
Copied
Add a private note to [conversation id]: [note].
Copy the prompt
Copied
Close conversation [id] with reason [reason].
Contacts & reporting
Copy the prompt
Copied
Search contacts by email [email].
Copy the prompt
Copied
Get conversation history for [contact].
Copy the prompt
Copied
How many open conversations by team?
Copy the prompt
Copied
List conversations with CSAT score below 3.
SEE HOW AUTH WORKS
Users authorize Intercom once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Intercom
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
Intercom
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
Intercom
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
Intercom
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 support agents and MCP connectors. Working code, live demos, fork what fits.
SUPPORT
Support ticket automation (Google ADK)
Google ADK agent that classifies Zendesk tickets, pulls Notion context, and posts to Slack. End-to-end ticket handoff.
SUPPORT
Support triage agent
Read Zendesk tickets, fetch runbooks from Notion, and route to the right Slack channel with a drafted response.
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.
Intercom 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 Intercom 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 Intercom oauth 2.0 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 Intercom?
Yes. Pass a tool name filter to listScopedTools so the support agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Intercom.

What happens when a user revokes Intercom 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.

Can the agent reply to conversations assigned to other agents?
Depends on the authorizing user's Intercom role. Admins can send from any inbox; agents typically operate on their own assigned conversations. Team permissions and assignment rules apply at every call.

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"": {
""intercom"": {
""url"": ""https://mcp.scalekit.com/intercom"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.intercom]
url = ""https://mcp.scalekit.com/intercom""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""intercom"": {
""url"": ""https://mcp.scalekit.com/intercom"",
""type"": ""http""
}
}
}