AdlyseAdlyseDocs
Welcome
Getting Started
QuickstartOnboarding Wizard
Essentials
DashboardAd AccountsExplorerReportsSearch TermsDecision Log
AI Studio
Adlyse AISkillsGuidelinesSchedules
Admin
OrganizationTeam
Integrations
OverviewMCP Servers →API Keys
Legacy Docs
OverviewQuickstartCookbookWorkflowVariablesKnowledge BaseAPI Keys (legacy)NodesSelf HostingSelf-Host Auth
  1. Integrations

Integrations

Adlyse is designed to plug into the tools your team already uses. Today there are two first-class integration surfaces; more are on the roadmap.

Available integrations#

  • MCP Servers → — six Model Context Protocol servers that expose Adlyse to external AI clients (Claude Code, Claude.ai, ChatGPT Desktop, or your own orchestration). This is the canonical way for AI agents outside Adlyse to read and write your data. MCP has its own dedicated docs site.
  • API Keys — bearer-token authentication for the MCP servers and any future Adlyse REST endpoints. Also used when Slack / email delivery needs to authenticate back into the workspace.

Connected services (OAuth)#

These aren’t “integrations” in the sense of something you install — they’re the ad platforms and communication channels Adlyse connects to automatically when you onboard:

  • Google Ads, Meta Ads, TikTok Ads — via OAuth from Ad Accounts
  • Slack — for report delivery and notifications (Integrations → Slack → Connect Workspace)
  • Email — report delivery to custom email addresses and invite flows

Roadmap#

On deck for the next release train:

  • Webhooks — push notifications to your endpoints when key events fire (report ready, anomaly detected, decision logged, budget threshold crossed).
  • REST API parity — the same surface as the MCP servers, as plain JSON-over-HTTPS.
  • Zapier / Make connectors — no-code integration for non-engineering teams.
←Previous
Team
Next→
MCP Servers →