OAUTH 2.1
PARTNER ECOSYSTEM
Crossbeam MCP gives agents authenticated access to your partner ecosystem: find account overlaps, surface ecosystem activity, and pull co-selling context under the rep's own credential.
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
// Crossbeam tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["crossbeammcp"], toolNames: [
"crossbeammcp_search_crossbeam_knowledge",
"crossbeammcp_get_list_link",
"crossbeammcp_find_overlaps"] },
pageSize: 100,
});
const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Which of our partners also work with Globex, and who can intro us?" }] });import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();
const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["crossbeammcp"] }, pageSize: 100,
});
const res = await openai.chat.completions.create({
model: "gpt-5",
messages: [{ role: "user", content: "Which of our partners also work with Globex, and who can intro us?" }],
tools,
});
// Execute the tool call with the user's vaulted Crossbeam credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();
const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["crossbeammcp"] }, pageSize: 100,
});
const msg = await anthropic.messages.create({
model: "claude-sonnet-5",
max_tokens: 1024,
messages: [{ role: "user", content: "Which of our partners also work with Globex, and who can intro us?" }],
tools,
});
// Tool call runs with the user's vaulted Crossbeam credential
await sk.tools.executeTool(msg.content, "user_123");import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";
const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["crossbeammcp"] }, pageSize: 100,
});
const agent = new Agent({
name: "crossbeam_agent",
model: "gemini-2.5-pro",
instruction: "Manage Crossbeam for the signed-in user.",
tools,
});
await agent.run("Which of our partners also work with Globex, and who can intro us?");
.svg.png){kind=icon}
.svg)
.svg)
// shared token
audit → bot_service_account
// scalekit
audit → user_abc ✓
Does the agent access Crossbeam 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 Crossbeam OAuth token 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 Crossbeam?
Yes. Pass a tool name filter to listScopedTools so the sales agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Crossbeam.
What happens when a user revokes Crossbeam 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 Crossbeam permissions?
Yes. Every call runs as the authorizing user. Native roles, sharing settings, and scope restrictions in Crossbeam apply to each request, and actions log to the audit chain.
