TRUSTED IDP
ANALYTICS
Amazon Redshift is a fully managed cloud data warehouse that enables fast, cost-effective analysis of structured and semi-structured data at scale.
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="redshift")
mcp = MultiServerMCPClient({
"redshift": {
"url": "https://mcp.scalekit.com/redshift",
"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: "redshift" });
const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/redshift
// 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: "redshift" });
const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/redshift
// 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="redshift")
# Connect to MCP at https://mcp.scalekit.com/redshift
# Pass: Authorization: Bearer + token
.svg)
// shared token
audit → bot_service_account
// scalekit
audit → user_abc ✓
Does the agent access AWS Redshift 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 AWS Redshift 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 AWS Redshift?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches AWS Redshift.
What happens when a user revokes AWS Redshift 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 SQL execution respect Redshift grants?
Yes. execute_sql and schema inspection run under the connected Redshift credential's grants, so schema and table permissions hold. Scalekit vaults the credential and scope-checks every statement pre-call.
