People and companies; enriched contact and firmographic data; Apollo contacts and accounts; lists; sequences and enrollment; connected email accounts; one-off emails; tasks; and sequence, email, and engagement analytics.
Apollo
Included as a prospecting and sales-engagement surface whose first-party MCP can search and enrich people or companies, manage Apollo records and lists, build sequences, enroll contacts, send one-off email, manage tasks, and query engagement analytics under the authorizing user’s workspace access.
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Search companies, people, saved contacts, sequences, lists, tasks, and connected email accounts; enrich people or companies; retrieve company job postings; show task details; and query outreach and engagement analytics.
Edit profile settings; create or update accounts, contacts, lists, and sequences; add or remove records from lists; enroll or remove contacts from sequences; send one-off emails; create tasks; and complete or skip tasks. Bulk delete and other destructive actions are not supported.
The standalone endpoint uses browser-based OAuth 2.0 with no API key. Access is scoped to the Apollo user and workspace that authorize the connection; the assistant cannot exceed that user’s permissions, plan features, sequence access, connected mailboxes, or available credits.
Apollo recommends client approval for credit-consuming actions, searching before enrichment, checking for an existing contact before creation, and listing email accounts before sequence enrollment. Connections can be revoked in account or connected-app settings.
People search does not return full email or phone details; enrichment is required and consumes credits. Search may paginate. Tool availability varies by plan, workspace permission, client support, rollout, API limits, and credit balance. Apollo prohibits AI model training with MCP data and requires training to be disabled in the client.
Agent access
MCP support
Support: Official MCP server
Read scope: Use no-credit people/contact searches for initial qualification, then invoke explicitly approved enrichment when verified email, phone, or fresh firmographic data is needed. Analytics, sequence, task, list, and mailbox queries remain bounded by workspace access.
Write scope: Apollo MCP can change records and lists, draft or update sequences, start or stop sequence enrollment, send email with custom To/Cc/Bcc, and change task status. These actions act in the selected workspace and sending context; no bulk-delete capability is documented.
Authentication: OAuth 2.0 at the standalone remote MCP endpoint, completed in a browser for the selected Apollo account and workspace; this differs from direct Apollo API access by user API key.
Approval boundary: Require confirmation before enrichment that spends credits, any contact or account creation or update, list membership changes, sequence creation or enrollment, task completion or skipping, and every email send. For outreach, show workspace, sender mailbox, contact association, all recipients, sequence, and message content.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Apollo.io ships them.
Single-platform patterns
- GTM research, enrichment, and outbound cockpit
- Account journey room
- Pipeline-quality debugger
- Customer expansion cockpit
Multi-platform compositions
- Apollo + marketing or intent platform: account journey room
- Apollo + conversation or support system + analytics or warehouse: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.