Seamless
by Seamless
Prospect, enrich and run outbound campaigns from your AI assistant. 54 tools across 11 domains, 33 of which write — including sending email to the public internet. OAuth offers exactly one scope: mcp.all.
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.
Connect Seamless via MCP
https://mcp.seamless.ai/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Seamless Tools & Capabilities (54)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Research spends purchased credits. Seamless's credit table marks the research endpoints as consuming credits and marks search, org-data reads, polling and OAuth calls as not consuming them. An agent looping over a large result set can therefore run down a paid balance without any tool looking obviously expensive. Running out returns HTTP 422 with code
insufficientCredits. - The consent screen offers nothing to narrow.
mcp.allis 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 separatepublicAPI.v1.allscope for its REST API, so the platform distinguishes surfaces — it simply does not scope this one by permission. - Rate limits are organisation-wide. Sixty requests per minute per endpoint, shared across every API key and user in the org, with 429 on exceeding it. Seamless advises polling research results at 2–5 second intervals rather than in tight loops, and says custom limits are a sales conversation.
- Most of the surface needs a Connect licence. Only 17 of the 54 tools — search, research, user, lists and saved searches — are documented as available to all users. The other 37 sit behind Connect or Connect (full).
- MCP access is a separate switch. Seamless documents an "MCP Server access is not enabled" error distinct from Connect licensing, resolved only by an administrator.
- Historical reads are capped at 30 days.
get_my_contactsandget_my_companiesaccept a date range of at most 30 days, so a longer backfill needs several calls. - Research is asynchronous by default. It returns request identifiers rather than results; an agent that forgets to poll or to set
waitForResultswill stall having already spent the credits. - We could not read tool schemas. The endpoint returned HTTP 401 to our anonymous handshake, so no
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.
Frequently asked questions
Does the Seamless MCP server spend credits when an agent calls a tool?
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.
What OAuth scopes does the Seamless MCP server ask for?
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.
Can the Seamless connector send email to real people?
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.
What kind of personal data does Seamless MCP return?
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.
Why can I not see the campaign or email tools in my MCP client?
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.
How many Seamless MCP tools delete data permanently?
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.
What rate limits apply to the Seamless MCP server?
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.
Sources
- Seamless MCP documentation overview (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless MCP risk tiers (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless MCP access control (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless MCP authentication (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless MCP resources (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless MCP tool reference, 11 domain pages — and siblings (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless rate limits and credits (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless API HTTP status codes (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless documentation index — and (retrieved 2026-08-20) · retrieved 2026-08-20
- Seamless.AI privacy policy (retrieved 2026-08-20) · retrieved 2026-08-20
- Live RFC 9728 resource metadata and
www-authenticatechallenge atmcp.seamless.ai(2026-08-20) · retrieved 2026-08-20 - Anthropic Connectors Directory entry (snapshot 2026-08-16; tool names, tier, endpoint) · retrieved 2026-08-16
- Seamless support
docs.seamless.ai/robots.txtpublishesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis expressly permitted by the publisher (retrieved 2026-08-20) · retrieved 2026-08-20
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Seamless
- Tools
- 54
- Domain
- mcp.seamless.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.