Connect ChatGPT, Claude or another AI assistant to Spun

Spun can be connected to the AI assistant you already use, such as ChatGPT or Claude, through MCP (Model Context Protocol). Once connected, you can ask that assistant about your WhatsApp conversations, groups, contacts and digests in its own chat window, and it reads the answers straight from your Spun workspace.

This page covers what the connection gives you, which key and permissions to pick, how group messages tell you who wrote them, and how the monthly call allowance works.

At a glance

• Start read-only. The Read-only analyst key preset lets the assistant read but never send.
• Group sender identity needs two permissions: Read Contacts and Read Groups. The read-only preset has both.
• Every inbound group message names its sender: the phone number, your contact name for that number, and whether WhatsApp hid the number.
• Hidden-number members are marked hidden and carry a stable key instead of a number, so the assistant can still group their messages.
• Digests are cheap to read: reading a prepared digest answer is one call, however many messages it covers.
• Each plan includes a monthly number of calls. Beyond it, each call uses 20 AI tokens from your balance.

What MCP gives you

MCP is an open standard that lets an AI assistant use tools from another product. With Spun connected, the assistant can, for example:

• read the messages in a chat or a group and summarize them,
• look up contacts and labels,
• read the prepared answers of your chat digests,
• check its own permissions and your usage for the month.

The list of supported assistants, the server address and the step-by-step setup for each one are on spun.com/mcp. This guide explains what you see once you are connected.

Step 1: Choose the key and its permissions

An organization manager creates the key in Settings → AI Assistant (MCP). Assistants that sign in with your Spun account (for example a custom connector in Claude) ask for the organization and access level on a consent screen instead; the same permissions apply.

1. Pick a preset. The three presets are Read-only analyst, Assistant, no sends and Assistant with sends.

2. For analysis, choose Read-only analyst. It lets the assistant read conversations, contacts, labels, campaigns, groups, tasks and team members, and it cannot send anything.

3. Two permissions decide whether the assistant sees who wrote a group message:

   • Read Contacts
   • Read Groups

   A key needs both. Read-only analyst already has both. A key without them still reads group messages, but without the sender fields described below. The AI Assistant (MCP) settings tab offers the presets only; to pick permissions one by one, create the key on the Webhooks page under Manage API Keys instead.

You can delete a key at any time from Settings → AI Assistant (MCP). An assistant using it loses access immediately.

Who wrote each group message

When the assistant reads messages from a group, every inbound message carries four sender fields:

Field	What it holds
sender_phone	The sender's phone number with the country code, for example +972501234567. Empty (null) when WhatsApp hides the number, or when your organization's AI privacy level is set to keep phone numbers away from AI.
sender_contact_name	The name of the matching contact in your Spun contacts, or null when the sender is not a contact. Only a contact name counts here, never the profile name the member set in WhatsApp.
sender_hidden	true when WhatsApp hides this member's number, otherwise false.
sender_key	Present only when sender_hidden is true: a stable key for that member, such as hm_3f9a1c07b2e84d61.

The profile name the member set in WhatsApp is in the separate sender field, as before. Like message text, names are passed to the assistant marked as untrusted content, so the assistant treats them as data and never as instructions.

Here is one inbound group message from a hidden-number member, shortened:

{
  "message_id": "884213",
  "direction": "inbound",
  "type": "text",
  "body": { "source": "whatsapp_message", "trust": "untrusted_external_content", "text": "Room 12 is ready" },
  "timestamp": "2026-10-14T06:42:10.000Z",
  "sender": { "source": "contact_field", "trust": "untrusted_external_content", "text": "Dana" },
  "sender_phone": null,
  "sender_contact_name": null,
  "sender_hidden": true,
  "sender_key": "hm_3f9a1c07b2e84d61"
}

Telling staff from customers. Save your team as contacts with a label such as "Employee" (the group chats guide shows how). The assistant can then match sender_contact_name or sender_phone against that label and split your team's messages from everyone else's.

Messages your own number sent, and older history imported without a sender, do not carry these fields.

Hidden-number members

WhatsApp can hide a group member's number from everyone in the group, you included. Spun keeps working when WhatsApp hides the number.

• No fake numbers, ever. sender_phone stays empty for a hidden-number member; no number is filled in.
• A stable key instead. sender_key stays the same for the same member across every group and every report in your organization, so the assistant can count and group that member's messages. It is not a WhatsApp id, it cannot be turned back into one, and a different organization never gets the same key for the same person.
• Counted, not dropped. Hidden-number members are counted and labelled in every report, never silently dropped.

Link once, and the name follows. When you know who a hidden-number member is, link them to a contact in Spun. If they have written to you directly, open that chat, find the Not identified yet card in its contact panel, and choose Link to a contact or Add as new. From then on sender_contact_name carries the contact's name for that member, past messages included.

An organization manager can also tell Weave who a hidden member is in plain words, for example: "The member shown as ~Layla in the Reservations Review group is Layla Haddad." Name both the member and a contact you already have. Weave shows a confirmation card with the link it is about to make, and nothing changes until you confirm it. Weave never links a member on its own guess and never creates a contact from a link, and you can undo the link from the contact panel.

Spun does not look up a hidden member's number. Nothing is looked up in bulk; Spun only keeps what WhatsApp sends with normal message traffic. More on this in Analyze Your WhatsApp Group Chats.

Reading digests over MCP

A chat digest keeps a standing question answered as messages arrive, for example "What is still open in the partner groups?". The assistant reads a digest's prepared answer with the get_chat_summary tool.

• One call, however many messages. Reading the prepared answer counts as one call, whether it covers ten messages or ten thousand. For a daily report across hundreds of groups, this is the cheapest way to get it into ChatGPT or Claude.
• Nothing is recomputed. get_chat_summary returns the stored answer with its evidence and how fresh it is. It never starts new AI work.
• Listing and setting up. list_chat_summaries lists your digests. With a key that may change data, the assistant can also create or edit one with define_chat_summary and update_chat_summary.

Keeping digests up to date has its own monthly allowance of messages analyzed, shown on the pricing page. When it is used up, automatic refreshes pause until the next month, and a refresh you start yourself still runs.

Monthly call allowance

Each plan includes a monthly number of connected-AI calls for the organization:

Plan	Included calls per month
Starter	500
Pro	2,000
Max	Unlimited

What counts. A call is one tool use by the assistant that reads your data. These never count:

• checking the key's permissions, the usage summary, the business overview and delivery status,
• a call that failed,
• calls that change data, such as sending a message or creating a task. Those follow their own rules.

Beyond the allowance. Each further call uses 20 AI tokens from your organization's balance, so a busy month is not cut off while tokens remain. If the balance cannot cover the next call, the assistant gets a plan_limit_reached answer that says the month's included calls are used up and the token budget cannot cover more right now. To continue, add tokens or upgrade the plan in Settings → Plan & Usage. The allowance starts again at the beginning of the next month.

Emails before you run out. Organization managers are emailed when the organization reaches 90% of its monthly call allowance, and when it reaches 90% and 100% of its monthly AI tokens. These emails follow the budget alerts setting.

Where to see your usage

• Settings → AI Assistant (MCP). Under Show tool usage, the line Connected AI calls this month shows how many calls you have used and how many your plan includes.
• Settings → Plan & Usage. The plan comparison table shows each plan's call allowance and digest allowance next to its AI tokens.
• Ask the assistant. It can check the month's usage itself with the usage summary tool.

Privacy

The assistant sees only what the key's permissions allow, and a read-only key never sends anything. If your organization's AI privacy level keeps phone numbers away from AI, sender_phone stays empty for everyone and the contact name is still shown. Tell your staff that their group messages are analyzed, in line with your local data-protection rules.

Related

• Analyze Your WhatsApp Group Chats
• Weave AI Assistant
• Chat Digests
• Pricing