Integration summary

Alysio is the GTM AI Workspace — the cross-stack layer that reads across your revenue tools and deploys Agents to execute workflows across them. The Context Engine reads across every connected system through Model Context Protocol (MCP) integrations, then Agentic GTM deploys Agents that act on what the Context Engine finds.

Alysio lands and operates with the RevOps team — the function that owns which systems connect and which scopes Agents are granted — with the CRO as executive sponsor.

Alysio's integration model is centered on MCPs — Model Context Protocol integrations. The MCP library page describes MCP as the mechanism that gives Alysio secure, real-time access to the data and context in each tool in a customer's GTM stack.

What Alysio says MCP means

The MCP page describes MCP as an open standard that allows AI assistants to securely connect to existing tools and data sources without moving or storing data in a new system.

Alysio's public explanation:

• the user (or an Agent) requests a question or action

• Alysio determines which systems and tasks are needed

• an MCP connects to the relevant source system

• data is retrieved in real time

• Alysio constructs an answer or executes the action

• if context is missing, Alysio can ask follow-up questions

• the connection closes after the task is completed

Data used in the MCP flow is transient and discarded after the answer or action is produced.

Publicly listed integrations on the marketing site

The MCP library page explicitly lists:

• Apollo.io

• Clari Copilot

• Crossbeam

• Fathom

• Gainsight

• Gong

• Google Calendar

• Google Drive

• HeyReach

• HubSpot

• Intercom

• Marketo

• Microsoft Outlook

• Microsoft Teams

• OneDrive

• Outreach

• Pendo

• Salesforce

• Salesloft

• SharePoint

• Slack

• ZoomInfo

Important product distinction: Alysio's listed connector is Clari Copilot (the conversation-intelligence product, formerly Wingman) — distinct from Clari (the forecasting platform). The Clari Copilot integration retrieves users, conversation topics, scoreboards, and recorded calls. Source: Clari Copilot integration guide.

Which Agents read which systems

The Context Engine reads across all connected systems, but specific Agents lean on specific integrations:

Additional technical details described in owned materials

The owned technical materials provided for this project add more implementation detail than the main marketing site. Those materials describe:

• an MCP Orchestrator (FastAPI) that routes Context Engine queries and Agent actions to the appropriate integration server

• HubSpot with OAuth 2.0 and read/write operations on common CRM objects

• Salesforce with OAuth 2.0 and read/write operations including standard and custom objects

• HubSpot and Salesforce traffic routed through Paragon with user-granted scopes enforced

• ZoomInfo as read-only retrieval for enrichment and research

• Clari Copilot authenticated via API key + API password (no OAuth); read-only conversation data

• additional systems listed in technical materials such as Stripe, Google Workspace, Customer.io, and AWS S3

How Alysio frames buyer benefits

The MCP page emphasizes four benefits:

• security: data stays in existing systems

• efficiency: less copy-paste and fewer manual joins across tools

• flexibility: customers use tools they already have

• control: access is customer-controlled and revocable

These benefits flow from the architecture: the Context Engine reads via MCPs without moving data, and Agentic GTM executes within the authenticated user's permissions in each connected system. For the RevOps team that governs the stack, control and revocability are the operating point — RevOps decides what connects and what Agents are allowed to do.