Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Prospect, enrich and run outbound campaigns.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Seamless MCP server connects Seamless.AI B2B sales prospecting to Claude, ChatGPT and any MCP-compatible agent. It exposes 54 tools across 11 domains covering contact and company search, data enrichment, list management, outbound campaigns, email sending and call logging. Sign-in is OAuth, and 33 of the 54 tools change something rather than read it.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
insufficientCredits.mcp.all is the only application scope the resource descriptor advertises, so a user cannot grant read without also granting the 27 write and 6 destructive tools. Seamless does define a separate publicAPI.v1.all scope for its REST API, so the platform distinguishes surfaces — it simply does not scope this one by permission.get_my_contacts and get_my_companies accept a date range of at most 30 days, so a longer backfill needs several calls.waitForResults will stall having already spent the credits.inputSchema, no live safety annotations and no live resource or prompt listing appear here. Tool names come from Anthropic's directory snapshot; risk tiers, parameters and licence gates come from Seamless's own documentation. Where the two could be compared — the tool list — they agreed exactly.Yes, but only the two research tools do. Seamless documents that enrichment consumes research credits while search and reads of records already in your organisation do not. That makes `research_contacts` and `research_companies` the metered calls, and Seamless labels both `write` rather than `read` for exactly that reason — they are billable side effects, not free lookups.
One, and it is all-or-nothing. The server's RFC 9728 descriptor advertises `scopes_supported` of exactly `mcp.all`, and its `www-authenticate` challenge names the same scope, both verified live on 2026-08-20. There is no read-only grant to choose at the consent screen, so approving the connector approves every tool your Seamless licence already permits.
Yes. Six of the 54 tools write outbound email, including `send_email`, `send_bulk_email` and `send_email_draft`, and Seamless's own documentation warns that sends go to recipients on the public internet and should require explicit user approval. Those tools need a Connect licence, so accounts without Connect will not see them listed.
Business contact data about third parties. Seamless documents `research_contacts` as returning verified email addresses and phone numbers, and its privacy policy lists names, addresses, telephone numbers and email addresses among the personal data it collects from partners and public sources. The people described did not supply that data to you, which is a compliance consideration your organisation owns.
Your licence does not include them. Seamless enforces access per request and documents that your client lists only tools you are allowed to call, so campaigns, tasks, templates, email, calls and activity all require a Connect licence. Campaigns and tasks need Connect (full) specifically. MCP access must also be enabled separately on the account.
Six, and Seamless labels each one `destructive` rather than merely `write`. They are `delete_campaign`, `delete_campaign_step`, `delete_list`, `delete_saved_search`, `delete_task` and `delete_template`. Seamless states that destructive operations cannot be undone and recommends requiring explicit approval before any of them runs in an agent workflow.
Sixty requests per minute per endpoint, shared across your whole organisation. Seamless documents that every API key and user under one org draws on the same quota, that each endpoint gets its own window, and that exceeding it returns HTTP 429. The `X-RateLimit-Limit` header on each response reflects the actual limit for that endpoint.
www-authenticate challenge at mcp.seamless.ai (2026-08-20) · retrieved 2026-08-20docs.seamless.ai/robots.txt publishes Content-Signal: ai-train=yes, search=yes, ai-input=yes — synthesis expressly permitted by the publisher (retrieved 2026-08-20) · retrieved 2026-08-20Connect Seamless once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.