Success.ai MCP server
Yes. Success.ai publishes an official MCP server at https://mcp.success.ai/mcp. It's hosted. It offers 131 tools. We last checked it on 22 Nov 2026.
Official: answers MCP requests at mcp.success.ai, on Success.ai's own domain success.ai. Checked 22 Nov 2026. Maintained by Stuart Brameld.
Key facts
As of 22 Nov 2026, Success.ai's official MCP server scores 55/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 131 tools.
How the Agent Readiness Index works · Wrong? Suggest a correction
Success.ai MCP server review
55/100
Success.ai's MCP server scores 55/100 on MartechDB's Agent Readiness Index: usable by AI agents, with gaps.
The good
Hosted by Success.ai: connect by URL, with nothing to install
Answered 100% of our checks in the last 90 days
The bad
Nothing we've found.
Not checked yet: how you sign in; a docs page listing its tools; what agent access costs. Anything not checked scores nothing.
Official MCP server
Success.ai MCP server
- Address
- https://mcp.success.ai/mcp
- Runs
- Hosted
- Sign-in
- Official MCP Registry
- Not listed
- How we know it's official
-
- Answers MCP requests at mcp.success.ai, on Success.ai's own domain success.ai.
- Tools
- 131 tools · listed 7 Oct 2026
- First seen
- 1 Oct 2026
- Last checked
-
Reachable ·
16 Nov 2026: reachable17 Nov 2026: reachable18 Nov 2026: reachable19 Nov 2026: reachable20 Nov 2026: reachable21 Nov 2026: reachable22 Nov 2026: reachable
- Uptime
- 100% · 55 of 55 checks reachable since 1 Oct 2026
Success.ai MCP server tools (131)
As the server lists them. Names and descriptions are the vendor's own.
-
test-api-keyTest API KeyUse this first when connecting to Success.ai or troubleshooting authentication. It checks whether the supplied Success.ai V2 API key is valid and returns the workspace name for that key. This is read-only and does not change account data.
-
get-rate-limitsGet Rate LimitsCheck the current API rate-limit quota for the authenticated workspace. Use this before running many Success.ai operations or after the user sees rate-limit errors. This is read-only and only reports limit status.
-
get-accounts-listGet Accounts ListList sending email accounts connected to the authenticated workspace. Use this before attaching senders to a campaign or checking whether a sender exists. This is read-only.
-
get-account-statusGet Account StatusGet connection and warmup status for one sending email account. Use this before enabling warmup, pausing warmup, or troubleshooting why a campaign cannot send. This is read-only.
-
get-account-vitalsGet Account VitalsCheck DNS and deliverability setup signals for one or more sending accounts, such as MX, SPF, DKIM, and DMARC. Use this when the user asks whether sending accounts are technically ready. This is read-only.
-
enable-warmupEnable WarmupEnable warmup for one sending email account. This changes account warmup state, so ask the user whether to proceed before running it.
-
pause-warmupPause WarmupPause warmup for one sending email account. This changes account warmup state, so ask the user whether to proceed before running it.
-
delete-accountDelete AccountDelete one or more sending email accounts from the workspace. This is destructive and may affect campaigns using those senders, so ask the user whether to proceed before running it.
-
list-campaignsList CampaignsList campaigns in the authenticated workspace with pagination. Use this whenever the user gives a campaign name and another tool needs a campaignId, or when the user asks to browse campaigns. Results are capped at 50 per request. This is read-only.
-
get-campaign-statusGet Campaign StatusGet the current status of one campaign, such as whether it is draft, active, paused, or otherwise not ready to send. Use list-campaigns first if the user provides a campaign name instead of an ID. This is read-only.
-
get-campaign-namesGet Campaign NamesGet campaign name/details for one campaign ID. Use list-campaigns first if the user provides a campaign name instead of an ID. This is read-only.
-
get-campaign-accountsGet Campaign AccountsShow which sending email accounts are attached to a campaign. Use this before launching when a campaign may be missing a sender, or when the user asks what account will send the emails. This is read-only.
-
set-campaign-nameSet Campaign NameRename an existing campaign. Use list-campaigns first if the user gives a campaign name instead of an ID. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
set-campaign-accountsSet Campaign AccountsReplace the full sending-account list for a campaign. Use get-accounts-list to find available senders and get-campaign-accounts to inspect the current campaign senders first. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
add-campaign-accountAdd Campaign AccountAdd one sending account to a campaign without replacing existing senders. Use get-accounts-list first if the user has not provided a connected sender email. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
remove-campaign-accountsRemove Campaign AccountsRemove one or more sending accounts from a campaign. Use get-campaign-accounts first if the user has not provided exact sender emails. This modifies campaign sender configuration, so ask the user whether to proceed before running it.
-
set-campaign-scheduleSet Campaign ScheduleSet or update a campaign's date range and sending windows. Use this when the user asks to schedule campaign sending. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
create-campaignCreate CampaignCreate a new draft campaign in Success.ai using a campaign name and IANA timezone. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
create-campaign-sequenceCreate Campaign SequenceCreate an email or LinkedIn sequence step in a campaign. Use this after a campaign exists and the user provides or approves the message content. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
create-variantCreate VariantCreate an A/B test variant for an existing sequence step. Use this when the user asks for an alternate subject/body for a sequence. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
update-sequenceUpdate SequenceUpdate the wait-days delay for an existing campaign sequence step. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
delete-sequenceDelete SequenceDelete a campaign sequence step and its variants. Remaining steps may be reordered. This is destructive, so ask the user whether to proceed before running it.
-
delete-variantDelete VariantDelete one sequence variant. The API may reject deleting the last remaining variant. This is destructive, so ask the user whether to proceed before running it.
-
pause-campaignPause CampaignPause an active campaign so it stops sending new emails. Use list-campaigns first when the user gives a campaign name. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
launch-campaignLaunch CampaignLaunch a campaign so it can start sending according to its configured schedule. The campaign must already have leads, at least one sequence, and a sending account. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
get-campaign-summaryGet Campaign SummaryGet a high-level performance summary for one campaign, including lead totals and engagement/status counts. Use this when the user asks how a specific campaign is doing. If the user gives a campaign name, call list-campaigns first to find the campaignId. This is read-only.
-
get-campaign-countGet Campaign CountGet email activity counts for a date range, such as sent, opened/read, replies, and contacted leads. Use this for time-bounded reporting across campaigns or for one campaign when campaignId is supplied. Dates must be values accepted by the Success.ai API. This is read-only.
-
get-account-warmup-summaryGet Account Warmup SummaryGet warmup summary data for one sending account over a date range, including inbox, received, sent, spam, and spam-rescued counts. Dates must use the format accepted by the Success.ai API, such as MM-DD-YYYY. This is read-only.
-
get-account-campaign-countGet Account Campaign CountGet current-day email campaign stats by sending account, including sent, opened, replied, and clicked counts. When email is omitted, the API returns stats for all accounts in the workspace. This is read-only.
-
search-peopleSearch PeopleFind prospects in the Success.ai people database using filters such as job title, location, industry, company domain, technology, and keywords. Use this when the user asks to find leads or contacts. This can consume Success.ai credits based on perPage and dataOptions, so ask the user whether to proceed before running it. Keep perPage small unless the user asks for more.
-
search-companiesSearch CompaniesFind companies/accounts in the Success.ai company database using filters such as company keywords, domains, technologies, industries, locations, revenue, and employee ranges. Use this when the user asks to find target companies rather than individual people. This can consume Success.ai credits based on perPage and dataOptions, so ask the user whether to proceed before running it.
-
prepare-searchPrepare SearchPrepare a structured people or company search from a natural-language request. Use this first for broad search requests, then ask the user whether to proceed before running the returned search tool. People/contact/lead/prospect or role-based requests route to people search; other requests route to company search. This does not call the Success.ai API or consume credits.
-
get-contactGet ContactLook up one contact by email address, optionally within a specific campaign. Use this before changing a contact's campaign status or when the user asks for details about a known email address. This is read-only.
-
add-contactsAdd ContactsAdd up to 500 contacts directly to a campaign. Use this when the user provides contact data and wants it added to a campaign without first creating a list. This modifies campaign lead data, so ask the user whether to proceed before running it.
-
delete-contactsDelete ContactsDelete contacts from a campaign by email address. This removes campaign contacts, so ask the user whether to proceed before running it.
-
update-contact-statusUpdate Contact StatusChange one contact's status inside a specific campaign, for example to Interested, Not Interested, Unsubscribed, or Meeting Booked. Use get-contact first if you need to verify the contact email. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
update-contact-variablesUpdate Contact VariablesUpdate existing custom variables for a contact in a campaign. Use this when the variable keys already exist and the user wants to change their values. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
set-contact-variablesSet Contact VariablesSet or add custom variables for a contact in a campaign. Use this when new variable keys may need to be created. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
remove-contact-variablesRemove Contact VariablesRemove custom variable keys from a contact in a campaign. This modifies contact data, so ask the user whether to proceed before running it.
-
verify-peopleVerify PeopleVerify one person's email address and return deliverability details. This may consume Success.ai verification credits, so ask the user whether to proceed before running it.
-
verify-people-batchVerify People BatchSubmit a batch of email addresses for people verification. This may consume Success.ai verification credits, so ask the user whether to proceed before running it.
-
list-people-verification-batchesList People Verification BatchesList people verification batches saved for the authenticated workspace. This is read-only.
-
download-people-verification-batch-reportDownload People Verification Batch ReportDownload a CSV report for all people verification batches, or for one batch when batchId is supplied. This is read-only.
-
start-data-enrichmentStart Data EnrichmentStart a data enrichment job for leads and save results into an existing list. This starts background work and may consume credits, so ask the user whether to proceed before running it.
-
list-data-enrichment-jobsList Data Enrichment JobsList enrichment jobs or fetch a specific job by jobId. This is read-only.
-
export-data-enrichment-jobExport Data Enrichment JobExport enrichment job results in JSON, CSV, XLS, or Excel format. This is read-only.
-
download-data-enrichment-originalDownload Data Enrichment OriginalDownload the original input for an enrichment job. This is read-only.
-
get-data-license-overviewGet Data License OverviewGet Success.ai data license overview information. This is read-only.
-
get-data-sourcesGet Data SourcesGet Success.ai data source information. This is read-only.
-
get-data-processingGet Data ProcessingGet Success.ai data processing methodology information. This is read-only.
-
get-data-updatesGet Data UpdatesGet Success.ai data updates and maintenance information. This is read-only.
-
get-data-securityGet Data SecurityGet Success.ai data security and compliance information. This is read-only.
-
get-all-listsList All ListsList people or company lists in the authenticated workspace. Use this to find a listId before reading list contents, adding leads from a list to a campaign, or checking whether a list already exists. This is read-only.
-
get-list-detailsGet List DetailsGet metadata for one people or company list, such as list type and contact/company count. Use this after get-all-lists when you need to verify the selected list before reading or sending it. This is read-only.
-
get-leads-from-listGet Leads From ListRetrieve contacts from a people list with pagination and optional search. Use this to preview leads before adding them to a campaign or when the user asks what contacts are in a list. Keep limits small unless the user asks for more. This is read-only.
-
get-companies-from-listGet Companies From ListRetrieve companies from a company list with pagination and optional search. Use this to preview company/account records before acting on a company list. Keep limits small unless the user asks for more. This is read-only.
-
create-people-listCreate People ListCreate an empty people/contact list in the authenticated workspace. Use this when the user asks to create a contact list or when a workflow needs a destination list for found leads. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
create-company-listCreate Company ListCreate an empty company/account list in the authenticated workspace. Use this when the user asks to create a company list or when a workflow needs a destination list for found companies. This modifies Success.ai data, so ask the user whether to proceed before running it.
-
send-list-to-campaignSend List To CampaignAdd contacts from a people list into a campaign. Use this after you have both listId and campaignId, commonly after creating/searching a list or after get-all-lists. Keep limit scoped unless the user asks to send the whole list. This modifies campaign lead data and may enqueue background processing, so ask the user whether to proceed before running it.
-
delete-people-listDelete People ListDelete a people/contact list and its contacts from the authenticated workspace. Master lists cannot be deleted. This cannot be undone, so ask the user whether to proceed before running it.
-
delete-company-listDelete Company ListDelete a company/account list and its company entries from the authenticated workspace. Master lists cannot be deleted. This cannot be undone, so ask the user whether to proceed before running it.
-
add-leads-to-listAdd Leads To ListAdd up to 500 contacts to a people list. Use this when the user provides contact records and wants them stored in an existing people list. This modifies Success.ai list data, so ask the user whether to proceed before running it.
-
add-companies-to-listAdd Companies To ListAdd up to 500 company records to a company list. Use this when the user provides company data and wants it stored in an existing company list. This modifies Success.ai list data, so ask the user whether to proceed before running it.
-
remove-leads-from-listRemove Leads From ListRemove specific contacts from a people list by contact ID. This is a soft delete from the list, so ask the user whether to proceed before running it.
-
remove-companies-from-listRemove Companies From ListRemove specific companies from a company list by company ID. This is a soft delete from the list, so ask the user whether to proceed before running it.
-
export-listExport ListExport contacts or companies from a list in JSON or CSV format with optional pagination or row-range selection. This is read-only.
-
api-test-api-keyAPI: Test your API keyPurpose: Test your API key. Details: Verify that your API key is valid and retrieve your workspace information. API request: GET /v2/authenticate. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-rate-limitsAPI: Rate limitsPurpose: Rate limits. Details: Check your current rate limit status and remaining quota for requests per minute, hour, and day. API request: GET /v2/ratelimit/limits. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-list-campaignsAPI: List campaignsPurpose: List campaigns. Details: The "List campaigns" section allows users to retrieve a list of campaigns associated with their account. Users can view details such as campaign IDs and names, enabling them to manage and track their marketing efforts effectively. Pagination options are available for handling large sets of campaign data. API request: GET /v2/campaign/list. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-campaign-namesAPI: Get campaign namesPurpose: Get campaign names. Details: Retrieves campaign names and IDs for quick lookup. API request: GET /v2/campaign/get/name. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-campaign-statusAPI: Get campaign statusPurpose: Get campaign status. Details: This section allows users to retrieve the status of a specific campaign using its ID. By accessing this information, users can track the progress and performance of their campaigns without the need to navigate through multiple screens or interfaces. This feature streamlines the monitoring process and provides quick access to essential campaign status data. API request: GET /v2/campaign/get/status. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-campaign-accountsAPI: Get campaign accountsPurpose: Get campaign accounts. Details: Get the list of sending accounts associated with a campaign. API request: GET /v2/campaign/get/accounts. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-set-campaign-nameAPI: Set campaign namePurpose: Set campaign name. Details: Update the name of a campaign. API request: POST /v2/campaign/set/name. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-set-campaign-accountsAPI: Set campaign accountsPurpose: Set campaign accounts. Details: This endpoint sets the campaign's sending accounts to emails in the account_list. To add or remove a single sending account, skip to the next section. API request: POST /v2/campaign/set/accounts. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-add-campaign-accountAPI: Add sending account to campaignPurpose: Add sending account to campaign. Details: Add a single sending account to the specified campaign. API request: POST /v2/campaign/add/account. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-remove-campaign-accountsAPI: Remove sending accounts from campaignPurpose: Remove sending accounts from campaign. Details: Remove multiple sending accounts from the specified campaign. API request: POST /v2/campaign/remove/accounts. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-launch-campaignAPI: Launch campaignPurpose: Launch campaign. Details: Launch a campaign to start sending emails to leads. This endpoint activates the campaign and begins execution based on the configured schedule and settings. API request: POST /v2/campaign/launch. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-pause-campaignAPI: Pause campaignPurpose: Pause campaign. Details: Pause an active campaign to temporarily halt email sending. This allows you to make adjustments or assess performance before resuming the campaign. API request: POST /v2/campaign/pause. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-set-campaign-scheduleAPI: Set campaign schedulePurpose: Set campaign schedule. Details: Set or update the schedule for a campaign, including start/end dates and daily sending windows. API request: POST /v2/campaign/set/schedules. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-create-campaignAPI: Create new campaignPurpose: Create new campaign. Details: Create a new campaign with the provided details such as campaign name and timezone. API request: POST /v2/campaign/create. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-create-campaign-sequenceAPI: Create sequences for campaignPurpose: Create sequences for campaign. Details: Create a new campaign sequence with email or LinkedIn message content. API request: POST /v2/campaign/sequence-create. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-create-variantAPI: Create variant for campaign sequencePurpose: Create variant for campaign sequence. Details: Create a new variant (A/B test version) for an existing campaign sequence. API request: POST /v2/campaign/variants-create. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-update-sequenceAPI: Update campaign sequence wait daysPurpose: Update campaign sequence wait days. Details: Update the wait days for a specific campaign sequence. API request: PUT /v2/campaign/sequences/{id}. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-delete-sequenceAPI: Delete a campaign sequencePurpose: Delete a campaign sequence. Details: Delete a specific campaign sequence along with all its variants. Remaining sequences will be automatically reordered. API request: DELETE /v2/campaign/sequences-delete. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-delete-variantAPI: Delete a sequence variantPurpose: Delete a sequence variant. Details: Delete a specific variant from a sequence. Cannot delete the last remaining variant. API request: DELETE /v2/campaign/variants-delete. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-get-accounts-listAPI: List accountsPurpose: List accounts. Details: This endpoint fetch a paginated list of accounts associated with the provided API key. API request: GET /v2/account/list. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-account-statusAPI: Get account statusPurpose: Get account status. Details: Fetch the current status, including the warm-up status, of an account by its email. API request: GET /v2/account/status. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-account-vitalsAPI: Check account vitalsPurpose: Check account vitals. Details: This endpoint allows you to quickly check if the MX, SPF, DKIM, and DMARC records have been properly set for a list of domains. API request: POST /v2/account/vitals. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-enable-warmupAPI: Enable warmupPurpose: Enable warmup. Details: This endpoint enables the warmup process for the specified account. API request: POST /v2/account/warmup/enable. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-pause-warmupAPI: Pause warmupPurpose: Pause warmup. Details: This endpoint pause the warmup process for the specified account. API request: POST /v2/account/warmup/pause. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-delete-accountAPI: Delete accountPurpose: Delete account. Details: This endpoint delete the specified account. API request: DELETE /v2/account/delete. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-get-campaign-summaryAPI: Get campaign summaryPurpose: Get campaign summary. Details: Retrieve the lead status summary and analytics data for a given campaign, including total leads, contacted status, engagement metrics, and completion rates. API request: GET /v2/analytics/campaign/summary. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-campaign-countAPI: Get campaign countPurpose: Get campaign count. Details: Retrieve email engagement count data for a specific campaign within a date range, including emails sent, read, leads contacted, and replies received. API request: GET /v2/analytics/campaign/count. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-account-warmup-summaryAPI: Get account warmup summary dataPurpose: Get account warmup summary data. Details: Retrieve warmup summary data for an email account within a date range, separating outbound sent placement from inbound spam rescue counts. API request: GET /v2/analytics/account/warmup/summary. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-account-campaign-countAPI: Get email campaign stats for the current dayPurpose: Get email campaign stats for the current day. Details: Retrieve email engagement statistics for the current day, including sent, opened, replied, and clicked counts. If an email is provided, it returns stats for that specific account; otherwise, it returns stats for all accounts in the workspace. API request: GET /v2/analytics/account/campaign/count. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-add-contactsAPI: Add contacts to a campaignPurpose: Add contacts to a campaign. Details: Upload a list of contact objects to add to a campaign. - **A maximum of 500 contacts can be uploaded at once.** - **Only the `email` field is required.** API request: POST /v2/contact/add. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-get-contactAPI: Get or search for a contactPurpose: Get or search for a contact. Details: Retrieve contact details by email address. If `campaignId` is provided, returns the contact from that specific campaign. If left blank, returns the contact data from all campaigns matching the email. API request: GET /v2/contact/get. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-delete-contactsAPI: Delete contacts from a campaignPurpose: Delete contacts from a campaign. Details: Delete specific contacts from a campaign by providing a list of email addresses. API request: POST /v2/contact/delete. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-update-contact-statusAPI: Update contact statusPurpose: Update contact status. Details: Update the status of a specific contact within a campaign. **Possible values for newStatus:** **Basic types:** - `Active` - `Completed` - `Unsubscribed` **Additional types (marks sequence as Completed):** - `Interested` - `Meeting Booked` - `Meeting Completed` - `Closed` - `Out of Office` - `Not Interested` - `Wrong Person` You can also send custom label text (case-insensitive). API request: POST /v2/contact/update/status. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-update-contact-variablesAPI: Contact Variable | UpdatePurpose: Contact Variable | Update. Details: Update existing variables for a contact in a campaign. All keys must already exist. API request: POST /v2/contact/data/update. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-set-contact-variablesAPI: Contact Variable | SetPurpose: Contact Variable | Set. Details: Set or add custom variables for a contact. Can create new variables that don't exist. API request: POST /v2/contact/data/set. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-remove-contact-variablesAPI: Contact Variable | DeletePurpose: Contact Variable | Delete. Details: Remove specific custom variables from a contact. API request: POST /v2/contact/data/remove. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-search-peopleAPI: People SearchPurpose: People Search. Details: This endpoint searches for People and returns fields based on the requested data options. If dataOptions is omitted or no reveal option is enabled, workEmailReveal is applied by default. Credit charges per returned lead: - workEmailReveal: 1 credit - fullContactAndCompany: 4 credits. This includes workEmailReveal. - mobilePhoneReveal: 8 credits API request: POST /v2/mixed_people/search. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-search-companyAPI: Company SearchPurpose: Company Search. Details: This endpoint searches for organizations and returns fields based on the requested data option. Exactly one company data option is required. Credit charges per returned company: - basic: 1 credit. Returns full_contact_company_enrichment, id, name, company, companyName, domain, linkedin_url, industry, raw_address, country, state, city, and employee_count. - full: 4 credits. Returns all company fields. API request: POST /v2/company/find. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-verify-peopleAPI: People VerificationPurpose: People Verification. Details: This endpoint verifies a single person's email address and returns deliverability status, domain information, and toxicity score. API request: POST /v2/people_verification/verify. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-verify-people-batchAPI: Batch People VerificationPurpose: Batch People Verification. Details: Submit a batch of email addresses for people verification. API request: POST /v2/people_verification/verify/batch. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-list-people-verification-batchesAPI: List People Verification BatchesPurpose: List People Verification Batches. Details: List all people verification batches saved for the authenticated workspace. API request: GET /v2/people_verification/verify/batch. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-download-people-verification-batch-reportAPI: Download People Verification ReportPurpose: Download People Verification Report. Details: Download a CSV report for all people verification batches or a single batch when batchId is provided. API request: GET /v2/people_verification/verify/batch/download. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-data-enrichment-startAPI: Start enrichment jobPurpose: Start enrichment job. Details: Start enrichment using JSON array of leads. File upload is not supported. API request: POST /v2/data-enrichment/enrich. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-data-enrichment-list-jobsAPI: Enrichment job detailsPurpose: Enrichment job details. API request: GET /v2/data-enrichment/jobs. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-data-enrichment-exportAPI: Export enrichment resultsPurpose: Export enrichment results. API request: GET /v2/data-enrichment/jobs/{jobId}/export. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-data-enrichment-download-originalAPI: Download original enrichment inputPurpose: Download original enrichment input. API request: GET /v2/data-enrichment/jobs/{jobId}/download-original. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-datalicenseAPI: Data License OverviewPurpose: Data License Overview. Details: **Data License Overview** At **Success.ai**, we provide massive people and company datasets, as well as intent, job postings and IP web traffic de-anonymization data through **various licenses**. Whether you need our entire dataset or a custom subset, we can tailor a solution to meet your specific needs. To learn more, speak with one of our **Data Consultants**. **The Value of a Success.ai License** 1. **On-Premise Data Access**: During the license period, you have the right to use the data on your premises in any way, as long as it complies with our **Terms and Conditions**. 2. **Fastest Refresh Rate in the Industry**: We refresh our people and company data **continuously**, ensuring you always have the most up-to-date information. Updated files are delivered within a **maximum range of 4 to 8 weeks**, so your data stays current and actionable. 3. **Unmatched Data Coverage**: Our dataset offers the largest **global coverage** with a focus on *…
-
api-get-datasourcesAPI: Data SourcesPurpose: Data Sources. Details: **Data Sources** **Primary Sources** Our dataset is compiled from multiple sources to ensure comprehensive coverage and accuracy: - Publicly Available Business Information - Professional networking platforms, like LinkedIn - Company websites and directories - Business social media profiles - Public business registries and databases **Web Data Collection** - Structured data from public web sources - Manifestly public data as defined under GDPR Article 9.2(e) **Third-Party Data Providers** - Partnerships with reputable data aggregators - Business information services **User-Contributed Data** - Opt-in business contact information - Professional information shared within our platform API request: GET /v2/datasources. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-dataprocessingAPI: Data Processing MethodologyPurpose: Data Processing Methodology. Details: **Data Processing Methodology** **Data Extraction and Standardization** - Automated tools for public web data collection - API-based extraction from partner platforms - Bulk imports from data partnerships **Standardization Procedures** - Field normalization across sources - Country-specific formatting standardization - Company and industry classification mapping - Job title normalization and hierarchy classification **Data Enrichment** - Entity Resolution and Matching - Identify and merge duplicate records - Cross-validation across sources - Probabilistic and deterministic matching - Data Augmentation - Bespoke algorithms for enrichment - Company hierarchy mapping - Contact role and seniority classification - Technology stack enrichment API request: GET /v2/dataprocessing. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success…
-
api-get-data-updatesAPI: Data Updates and MaintenancePurpose: Data Updates and Maintenance. Details: **Data Updates and Maintenance** **Refresh Frequency** - Continuous, Daily refresh - Updates every 4-8 weeks **Update Methodology** - Continuous monitoring - Delta detection - Event-triggered updates **Historical Versioning** - Point-in-time recovery - Change history tracking - Audit trails API request: GET /v2/dataupdates. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-datasecurityAPI: Data Security and CompliancePurpose: Data Security and Compliance. Details: **Data Security and Compliance** **Privacy Compliance** * **GDPR Compliance** * Processing based on legitimate interests (GDPR Article 6.1(f)) * Processing of manifestly public data (GDPR Article 9.2(e)) * Data subject rights honored (access, erasure, rectification, portability) * **CCPA Compliance** * Consumer rights honored * Disclosure of collection practices * Opt-out mechanisms **Data Security Measures** * **Storage Security** * Data encryption at rest and in transit * Secure cloud platforms (Azure) * Compliance with industry-leading security standards * **Access Controls** * IP restriction for server access * Web application firewalls * Secure authentication practices **Technical Specifications** **Data Schema** | **Field Category** | **Example Fields** | **Description** | |-------------------|-------------------|-----------------| | Identity | Full Name, Email, Phone | Contact identification information | | Professional | Job Titl…
-
api-create-people-listAPI: Create a people listPurpose: Create a people list. Details: Create a new list to store individual contacts (people). Each workspace can have multiple people lists. API request: POST /v2/list/create/people. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-create-company-listAPI: Create a company listPurpose: Create a company list. Details: Create a new list to store company information. Each workspace can have multiple company lists. API request: POST /v2/list/create/company. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-delete-people-listAPI: Delete a people listPurpose: Delete a people list. Details: Delete a people list and all its contacts. This action cannot be undone. Master lists (default lists created for each workspace) cannot be deleted. API request: POST /v2/list/delete/people. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-delete-company-listAPI: Delete a company listPurpose: Delete a company list. Details: Delete a company list and all its entries. This action cannot be undone. Master lists (default lists created for each workspace) cannot be deleted. API request: POST /v2/list/delete/company. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-get-list-detailsAPI: Get list detailsPurpose: Get list details. Details: Retrieve detailed information about a specific list including its type, contact count, and timestamps. API request: GET /v2/list/get. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-all-listsAPI: List all listsPurpose: List all lists. Details: Retrieve a paginated list of all lists in your workspace. You can filter by list type (people or companies) and search by name. API request: GET /v2/list/all. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-leads-from-listAPI: Get leads from a people listPurpose: Get leads from a people list. Details: Retrieve contacts from a people list with pagination support. You can search and filter contacts within the list. This endpoint returns detailed contact information including emails, names, titles, companies, and other profile data. **Features:** - Pagination with customizable offset and limit - Search across email, name, company, and title fields API request: GET /v2/list/leads. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-get-companies-from-listAPI: Get companies from a company listPurpose: Get companies from a company list. Details: Retrieve company records from a company list with pagination support. You can search and filter companies within the list. This endpoint returns detailed company information including names, domains, industries, locations, and other company data. **Features:** - Pagination with customizable offset and limit - Search across name, domain, website, industry, and location fields API request: GET /v2/list/companies. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
-
api-add-leads-to-listAPI: Add leads to a people listPurpose: Add leads to a people list. Details: Add individual contacts (leads) to a people list. You can add up to 500 contacts at once. Duplicate detection is enabled by default based on email addresses. **Note:** Each list can contain a maximum of 10,000 contacts. API request: POST /v2/list/add/leads. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-add-companies-to-listAPI: Add companies to a company listPurpose: Add companies to a company list. Details: Add company records to a company list. You can add up to 500 companies at once. Duplicate detection is enabled by default based on company domain or name. **Note:** Each list can contain a maximum of 10,000 companies. API request: POST /v2/list/add/companies. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-remove-leads-from-listAPI: Remove leads from a people listPurpose: Remove leads from a people list. Details: Remove specific contacts from a people list by their contact IDs. This is a soft delete operation - the contacts are marked as deleted but not permanently removed. API request: POST /v2/list/remove/leads. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-remove-companies-from-listAPI: Remove companies from a company listPurpose: Remove companies from a company list. Details: Remove specific companies from a company list by their company IDs. This is a soft delete operation — the companies are marked as deleted but not permanently removed from the database. API request: POST /v2/list/remove/companies. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-send-list-to-campaignAPI: Send leads from a list to a campaignPurpose: Send leads from a list to a campaign. Details: Add contacts from a list directly to a campaign. This operation is asynchronous — contacts are queued and processed in the background. **Range Selection Options (choose one approach):** - `offset` + `limit` → pagination-style selection - `start` + `end` → specific row range (1-based index) **Filtering & Controls:** - `search` → filter contacts by name, email, company, etc. - `queryHash` → filter using a saved query identifier - `skipDuplicates` → skip contacts already added to the campaign - `bounceCheck` → verify email deliverability before adding API request: POST /v2/list/send-to-campaign. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: this can modify Success.ai data. Ask the user whether to proceed before running it.
-
api-export-listAPI: Export listPurpose: Export list. Details: Export contacts from a list in JSON or CSV format. **Supported Formats:** - `json` → Structured JSON response with metadata - `csv` → Downloadable CSV file **Range Selection (choose one approach):** - `offset` + `limit` → pagination-style export - `start` + `end` → specific row range (1-based index) **Limits:** - Maximum 10,000 records per request - For larger lists, use multiple requests with pagination API request: GET /v2/list/export. Use this api-* tool when a more specific curated tool does not cover the user's request. Safety: read-only from the MCP server perspective; it should not modify Success.ai data.
Connect your AI to Success.ai
Add the official Success.ai MCP server to Claude, ChatGPT or your editor.
Connect Success.ai MCP to Claude
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it Success.ai, paste the address below and click Add.
Connect Success.ai MCP to ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it Success.ai and paste the address below.
ChatGPT usually only connects to servers with self-serve sign-in or none.
Connect Success.ai MCP to Cursor
Opens Cursor if it's installed. If nothing happens, use the JSON below.
Connect Success.ai MCP to VS Code
Opens VS Code if it's installed. Otherwise add the JSON settings from the Cursor tab to your .vscode/mcp.json.
Success.ai MCP server questions
Does Success.ai have an official MCP server?
Yes. Success.ai publishes its MCP server itself. Its address is on Success.ai's own domain (mcp.success.ai). MartechDB only lists servers a vendor publishes, never community copies.
What is the Success.ai MCP server URL?
The address is https://mcp.success.ai/mcp.
How do I connect Success.ai MCP to Claude, ChatGPT or Cursor?
In Claude, add https://mcp.success.ai/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http successai https://mcp.success.ai/mcp
What can the Success.ai MCP server do?
It offers 131 tools, including test-api-key, get-rate-limits, get-accounts-list, get-account-status and get-account-vitals (as listed on 7 Oct 2026). 67 are marked read-only and 20 can delete or overwrite data.
Is the Success.ai MCP server in the official MCP Registry?
No. Success.ai hasn't published it to the official MCP Registry.
Is the Success.ai MCP server working?
Yes. It answered our most recent check. We last checked it on 22 Nov 2026.
What are the alternatives to Success.ai's MCP server?
In Prospecting & lead data, the most agent-friendly alternatives with an official MCP server are Boomerang (97/100), Crossbeam (94/100), Seamless.ai (94/100), Poggio (94/100) and Scalelist (94/100). Success.ai scores 55/100 on the same index.
Alternatives to Success.ai's MCP server
Vendors in Prospecting & lead data with an official MCP server, the most agent-friendly first. Success.ai scores 55/100.
Boomerang
getboomerang.ai
Crossbeam
crossbeam.com
Seamless.ai
seamless.ai
Poggio
poggio.io
Scalelist
scalelist.com
Use with AI
Connect your AI to MartechDB
Then ask it about Success.ai, or any of the 1,850 marketing tools with an official MCP server. Free, no sign-in.
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it MartechDB, paste the address below and click Add. There's no sign-in.
The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.
Claude Code
Run this in your terminal:
ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it MartechDB, paste the address below and choose No authentication.
Developer mode is on Plus and Pro plans, and on Business, Enterprise and Edu if an admin allows it.
API
The same data as JSON, with no sign-in. See the OpenAPI description for every endpoint and field.
CLI
Search the directory and print the command to connect a vendor's server, from your terminal. Needs Node 18 or later. View on npm
Show that your MCP server is verified
If you work at Success.ai, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.
Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.