BEARER TOKEN
CRM & SALES
Connect to ChiliPiper MCP. Schedule meetings, manage routing rules, track distributions, and automate handoffs from your AI agents.
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient
client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="chilipipermcp")
mcp = MultiServerMCPClient({
"chilipipermcp": {
"url": "https://mcp.scalekit.com/chilipipermcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";
const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "chilipipermcp" });
const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/chilipipermcp
// Pass: Authorization: Bearer + tokenimport Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";
const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "chilipipermcp" });
const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/chilipipermcp
// Pass: Authorization: Bearer + tokenfrom google.adk.agents import LlmAgent
from scalekit import ScalekitClient
client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="chilipipermcp")
# Connect to MCP at https://mcp.scalekit.com/chilipipermcp
# Pass: Authorization: Bearer + token
.svg)
.svg.png){kind=icon}
// shared token
audit → bot_service_account
// scalekit
audit → user_abc ✓
Does the agent access ChiliPiper 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 ChiliPiper bearer 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 ChiliPiper?
Yes. Pass a tool name filter to listScopedTools so the productivity agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches ChiliPiper.
What happens when a user revokes ChiliPiper 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.
Whose calendar do scheduled meetings land on?
The authorizing user's. Booking, routing, and handoff actions run under that user's ChiliPiper seat, so distribution rules and meeting ownership stay accurate.
