Skip to content

Integrations Overview

Building an agent is half the job. This section covers the other half: putting agents and tools where your users already work.

All channels call the same runtime with the same per-user permission checks, so choosing a channel is a user-experience decision, not a security trade-off. See the Architecture overview for how the channels converge.

Every channel authenticates in one of two OAuth modes: user-initiated (the request runs as the signed-in person, with their permissions) or machine-to-machine (the request runs with the role assigned to the OAuth client). How you authenticate changes what you see explains the difference. Whichever channel you choose, built-in tool calls count toward the same usage metering.

SlackNative appBusiness users asking questions where they already chat.User-initiated OAuth PluginsAgent SkillsDevelopers using Claude Code, Gemini CLI, Codex, and similar tools.User-initiated OAuth ClaudeMCPAlation context and agents in Claude Desktop and Web.User-initiated OAuth ChatGPTMCPAlation context in ChatGPT via connectors.User-initiated OAuth Copilot StudioMCPPublishing agents into M365 Copilot and Teams.User-initiated OAuth CursorMCPCatalog context while you code.User-initiated OAuth VS CodeMCPCatalog context in VS Code chat.User-initiated OAuth LibreChatMCPSelf-hosted chat UI over Alation tools and agents.User-initiated OAuth n8nMCPWorkflow automation calling Alation tools.User-initiated or machine-to-machine OAuth Snowflake CortexMCPAlation context in Cortex Agents via an MCP connector.User-initiated OAuth Any MCP clientMCPAnything that speaks the Model Context Protocol.User-initiated or machine-to-machine OAuth REST APIHTTPCalling agents from your own applications and pipelines.Machine-to-machine OAuth Python SDKPythonEmbedding Alation tools in your own agent stack.Machine-to-machine OAuth