--- title: "Seamless.AI MCP server for AI agents - actionlake" description: "Give Claude 66 Seamless.AI actions through one MCP server: contacts, companies, lists. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/seamless-ai updated: 2026-10-23 --- Connectors · CRM & sales # Seamless.AI MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Seamless.AI and the rest of your systems. It gives your agent 66 Seamless.AI actions (31 reads, 28 writes and 7 that wait for a confirmation) and holds the Seamless.AI credential itself, so the agent never does. It paces Seamless.AI's limits and records every call. [Connect Seamless.AI free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "seamless_ai.lists.list", intent: "check which Seamless.AI account is connected" } # Lists: list · read · 1 upstream call ``` - 66 actions in one signed file - 31 read look, never change - 28 write create and update - 7 wait for a yes destructive, confirmed first Set up ## Connect Seamless.AI in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Seamless.AI. API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` Seamless.AI API key ``` account { op: "connections.requirements", service: "seamless_ai" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "seamless_ai.lists.list" } # lists: list · read · 1 upstream call check { action: "seamless_ai.contacts.update_batch", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Seamless.AI at a glance **Sign-in** API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` **Limits we pace to** 60 calls a minute, per connection **API covered** Seamless.AI API v2 (contact and company search, research, org data, lists, campaigns, email) API client/v2`api.seamless.ai` **Built from** Seamless.AI's documentation, read 23 October 2026[gist.githubusercontent.com](https://gist.githubusercontent.com/JustinAlia/6ff38a671f5f79895444b77c57f3afff/raw/v2-openapi.json) [docs.seamless.ai](https://docs.seamless.ai/api-catalog/overview) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 31 of 31 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 2, so ask can line Seamless.AI up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Seamless.AI. 66 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest. - **31** read look, never change - **28** write create and update - **7** destructive wait for a confirmation 1. ### Prospecting 66 31 read · 28 write · 7 destructive Contacts: list · Companies: list · Contacts: update batch · Companies: update batch Top actions ## The Seamless.AI API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 14 of Seamless.AI's 14 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `seamless_ai.contacts.list` Contacts: list | Get a list of contacts from your orgs Seamless.AI API v2 `GET /api/client/v2/contacts` (`getContacts`). | read | `crm.contact.list` 177 connectors | | `seamless_ai.companies.list` Companies: list | Get a list of companies from your orgs Seamless.AI API v2 `GET /api/client/v2/companies` (`getCompanies`). | read | `crm.company.list` 162 connectors | | `seamless_ai.contacts.update_batch` Contacts: update batch | Applies an update to a batch of your saved contacts. | write | `crm.contact.update` 159 connectors | | `seamless_ai.companies.update_batch` Companies: update batch | Applies an update to a batch of your saved companies. | write | `crm.company.update` 137 connectors | | `seamless_ai.lists.list` Lists: list | Returns all lists (tags) belonging to the authenticated user. | read | `crm.contact_list.list` 34 connectors | | `seamless_ai.lists.create` Lists: create | Creates a new list (tag) for the authenticated user. | write | `crm.contact_list.create` 29 connectors | | `seamless_ai.activity.list` Activity: list | Returns the organization's activity feed (emails, calls, and other engagement events), optionally filtered by contact, campaign, or free-text search. | read | `crm.activity.list` 21 connectors | | `seamless_ai.calls.log` Calls: log | Logs a call outcome for a contact, optionally associating a disposition, sentiment, call script, duration, and the task it was made from. | write | `comm.call.create` 38 connectors | | `seamless_ai.lists.delete` Lists: delete | Deletes a list (tag) owned by the authenticated user. | destructive | `crm.contact_list.delete` 24 connectors | | `seamless_ai.emails.get` Emails: get | Retrieves a single email (draft or sent) by its ID. | read | `comm.email.get` 26 connectors | | `seamless_ai.company_research.create` Company research: create | Research companies by search result IDs from `/search/companies` and/or direct company identifiers (`domain`, `companyName`). | write | this connector | | `seamless_ai.contact_research.create` Contact research: create | Research contacts by searchResultId from contact search results or Contact enrich Seamless.AI API v2 `POST /api/client/v2/contacts/research`… | write | this connector | Try it ## Prompts to paste into Claude. Each one names the Seamless.AI actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Find the Seamless.AI contacts with no email address, so we can clean them up. calls `seamless_ai.contacts.list` 2. Write write Contacts: update batch in Seamless.AI. Show me exactly what you will send before you save it. calls `seamless_ai.contacts.update_batch` Governance for Seamless.AI ## Destructive actions wait for a yes. 7 Seamless.AI actions are destructive. These are all of them: - Lists: delete `seamless_ai.lists.delete` - Tasks: delete `seamless_ai.tasks.delete` - Campaigns: delete `seamless_ai.campaigns.delete` - Templates: delete `seamless_ai.templates.delete` - Campaign steps: delete `seamless_ai.campaign_steps.delete` - Saved searches: delete `seamless_ai.saved_searches.delete` - Campaign contacts: remove `seamless_ai.campaign_contacts.remove` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do seamless_ai.lists.delete confirm_policy: **human** Lists: delete? **intent:** the user asked me to lists: delete run suspended · waiting for a named person · key _seamless-ai-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "seamless-ai-agent", allowed_actions: ["seamless_ai.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "seamless_ai.lists.delete", approver: "lead@example.com" }, { match: "seamless_ai.tasks.delete", approver: "lead@example.com" }, { match: "seamless_ai.campaigns.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Seamless.AI only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Seamless.AI costs on actionlake. Every Seamless.AI action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Seamless.AI refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 66 Seamless.AI actions - 9 actions page each page of a long list is one call - 31 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Seamless.AI action. 66 actions by area: the id your agent calls, what it does, and its effect. **Prospecting 66** - `seamless_ai.activity.list` Activity: list read - `seamless_ai.call_dispositions.list` Call dispositions: list read - `seamless_ai.call_sentiments.list` Call sentiments: list read - `seamless_ai.calls.log` Calls: log write - `seamless_ai.campaign_contacts.add` Campaign contacts: add write - `seamless_ai.campaign_contacts.list` Campaign contacts: list read - `seamless_ai.campaign_contacts.remove` Campaign contacts: remove destructive - `seamless_ai.campaign_steps.create` Campaign steps: create write - `seamless_ai.campaign_steps.delete` Campaign steps: delete destructive - `seamless_ai.campaign_steps.execute_action` Campaign steps: execute action write - `seamless_ai.campaign_steps.list` Campaign steps: list read - `seamless_ai.campaign_steps.update` Campaign steps: update write - `seamless_ai.campaigns.clone` Campaigns: clone write - `seamless_ai.campaigns.create` Campaigns: create write - `seamless_ai.campaigns.delete` Campaigns: delete destructive - `seamless_ai.campaigns.execute_action` Campaigns: execute action write - `seamless_ai.campaigns.get` Campaigns: get read - `seamless_ai.campaigns.get_metrics` Campaigns: get metrics read - `seamless_ai.campaigns.list` Campaigns: list read - `seamless_ai.campaigns.update` Campaigns: update write - `seamless_ai.companies.list` Companies: list read - `seamless_ai.companies.search` Companies: search read - `seamless_ai.companies.update_batch` Companies: update batch write - `seamless_ai.company_research.create` Company research: create write - `seamless_ai.company_research.poll` Company research: poll read - `seamless_ai.contact_research.create` Contact research: create write - `seamless_ai.contact_research.poll` Contact research: poll read - `seamless_ai.contact_statuses.list` Contact statuses: list read - `seamless_ai.contacts.list` Contacts: list read - `seamless_ai.contacts.search` Contacts: search read - `seamless_ai.contacts.update_batch` Contacts: update batch write - `seamless_ai.credits.get` Credits: get read - `seamless_ai.email_accounts.list` Email accounts: list read - `seamless_ai.email_footers.list` Email footers: list read - `seamless_ai.emails.create_draft` Emails: create draft write - `seamless_ai.emails.get` Emails: get read - `seamless_ai.emails.send` Emails: send write - `seamless_ai.emails.send_bulk` Emails: send bulk write - `seamless_ai.emails.send_draft` Emails: send draft write - `seamless_ai.emails.send_preview` Emails: send preview write - `seamless_ai.emails.update_draft` Emails: update draft write - `seamless_ai.engagement_statuses.list` Engagement statuses: list read - `seamless_ai.features.get` Features: get read - `seamless_ai.lists.create` Lists: create write - `seamless_ai.lists.delete` Lists: delete destructive - `seamless_ai.lists.get` Lists: get read - `seamless_ai.lists.list` Lists: list read - `seamless_ai.lists.update` Lists: update write - `seamless_ai.locations.search` Locations: search read - `seamless_ai.me.get` Me: get read - `seamless_ai.saved_searches.create` Saved searches: create write - `seamless_ai.saved_searches.delete` Saved searches: delete destructive - `seamless_ai.saved_searches.get` Saved searches: get read - `seamless_ai.saved_searches.list` Saved searches: list read - `seamless_ai.saved_searches.update` Saved searches: update write - `seamless_ai.tasks.create` Tasks: create write - `seamless_ai.tasks.delete` Tasks: delete destructive - `seamless_ai.tasks.execute_action` Tasks: execute action write - `seamless_ai.tasks.get` Tasks: get read - `seamless_ai.tasks.list` Tasks: list read - `seamless_ai.tasks.update` Tasks: update write - `seamless_ai.templates.create` Templates: create write - `seamless_ai.templates.delete` Templates: delete destructive - `seamless_ai.templates.get` Templates: get read - `seamless_ai.templates.list` Templates: list read - `seamless_ai.templates.update` Templates: update write Questions ## The Seamless.AI MCP server, answered. **Is there a Seamless.AI MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 66 Seamless.AI actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Seamless.AI. **What do I need to connect Seamless.AI?** Seamless.AI API key. The free call account { op: "connections.requirements", service: "seamless_ai" } lists exactly what to paste. **Can an AI agent delete or change things in Seamless.AI?** Only if its key allows it, and only with an explicit confirmation. 7 Seamless.AI actions are destructive, including lists: delete, tasks: delete and campaigns: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Seamless.AI API limit?** actionlake paces every call to the limits in the Seamless.AI service file: 60 calls a minute per connection. Repeated reads are answered from cache (31 Seamless.AI actions can be), which never reaches Seamless.AI. **What does a Seamless.AI action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (9 Seamless.AI actions page). Cache hits, searches, dry runs and calls Seamless.AI refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Seamless.AI API does it cover?** The Seamless.AI API v2 (contact and company search, research, org data, lists, campaigns, email) API client/v2 at api.seamless.ai. It is built from Seamless.AI's documentation as read on 23 October 2026. 66 actions in 1 area, each one in the signed service file (version 1.0.0). **Does actionlake keep my Seamless.AI data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Seamless.AI credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Seamless.AI Shares the most action names with - [Recruit CRM 12](https://actionlake.com/connectors/recruit-crm) - [Freshsales 9](https://actionlake.com/connectors/freshsales) - [Google Contacts 8](https://actionlake.com/connectors/google-contacts) - [PhantomBuster 3](https://actionlake.com/connectors/phantombuster) - [Cognism 2](https://actionlake.com/connectors/cognism) - [Explorium AgentSource 2](https://actionlake.com/connectors/explorium-agentsource) Joins with, on shared entities - [ConnectWise PSA 2](https://actionlake.com/connectors/connectwise-psa) - [HaloPSA 2](https://actionlake.com/connectors/halopsa) - [Genesys Cloud CX 2](https://actionlake.com/connectors/genesys-cloud-cx) - [Simpro 2](https://actionlake.com/connectors/simpro) - [Acumatica Cloud ERP 2](https://actionlake.com/connectors/acumatica-cloud-erp) - [Exact Online 2](https://actionlake.com/connectors/exact-online) Browse - [All CRM & sales connectors](https://actionlake.com/connectors/category/crm-and-sales) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Seamless.AI; the name is the vendor's own. Counts are from the Seamless.AI service file, version 1.0.0. ## Give your agent Seamless.AI today. [Connect Seamless.AI free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/seamless-ai More: https://actionlake.com/llms.txt