# Grok, or any MCP client, with your WhatsApp chats > Circles lets Grok read the WhatsApp chats you choose, as a remote MCP server with a token. Make a token, add Circles where Grok takes remote MCP servers, and ask. **To connect Grok to WhatsApp:** link your number in Circles, make a token under *New token*, and add `https://app.usecircles.app/api/mcp` as a remote MCP server with the header `Authorization: Bearer circ_...`. Grok then reads the chats you opened, and the same config works for other MCP clients; Circles is free for 2 chats, or $29 a month on Pro (₪99 in Israel) with 14 days free, as of October 2026. Source: https://usecircles.app/en/agents/grok · Updated 2026-10-27 ## Looking for Grok inside WhatsApp? Many people searching for "Grok WhatsApp" want a number to chat with Grok in WhatsApp. Circles has no such number. It gives Grok your WhatsApp: the chats you open, to read, and to write in only where you allow. You keep asking Grok where you always do. ## Three steps, one paste 1. **Link your WhatsApp in Circles**: Start your trial, then link your number as a linked device: a code typed on your phone, or a QR on your computer. Same number, same WhatsApp on your phone. History arrives in about 5 to 15 minutes, and you can connect your agent meanwhile. 2. **Make a token**: On Circles' Agents page, choose *New token*, pick Grok (or Other), keep MCP, and choose what it allows. The token starts with `circ_` and is shown once. 3. **Add Circles as a remote MCP server**: Wherever your Grok setup takes a remote MCP server or a custom connector: the address `https://app.usecircles.app/api/mcp` and the header `Authorization: Bearer circ_...`. Menu names change; the Circles app shows the current steps. Grok can add remote MCP servers as custom connectors. Connect it with a token in the header, like any remote MCP client. Connecting by the address alone, with a sign-in, has not been tried yet. ## The config, for Grok or any MCP client Three things: the address, the transport, the header. ``` Server URL: https://app.usecircles.app/api/mcp Transport: HTTP (remote MCP) Header: Authorization: Bearer circ_... ``` ## The same, as JSON A client that reads JSON takes what Circles' *Copy config* gives it: ``` { "mcpServers": { "circles": { "url": "https://app.usecircles.app/api/mcp", "headers": { "Authorization": "Bearer circ_..." } } } } ``` Circles answers each request over plain HTTP POST, one message in and one out. Clients that speak MCP over HTTP connect. A client that only knows the older SSE transport cannot connect. Clients that support OAuth with dynamic registration can try the address alone and approve on Circles' page. ## What to ask Grok Invented examples, real shapes. - **"What is the street group saying about the road works?"**: Grok reads the group since a date, voice notes as text, and gives you the gist. - **"Which chats need an answer from me today?"**: `activity` shows what moved; Grok reads only those. - **"Find the photo of the parking permit Yossi sent"**: Grok fetches the photo and looks at it itself. Circles does not describe images. - **"Tell the running group I'm out on Thursday"**: Only if that group is open for sending and the token allows it. ## What Grok can and cannot do here **Grok can:** - See which chats you opened, and which of them moved since a time, with counts and no text (`allowed_chats`, `activity`). - Catch up and search, in one chat or all of them, with senders by name and voice notes already transcribed (`catch_up`, `search`). - See who you talk with and who is in a group, by the name you saved; group member lists never include numbers (`people`, `group_members`). - List the documents sent in your chats and open a photo, PDF or file, up to 50 MB (`documents`, `get_media`). Grok opens the file and reads it itself. - Send a message or a file, only in chats you opened for sending and within your daily cap (`send`). **Grok cannot:** - See a hidden chat. It is not listed, not searchable, and never named, not even in a refusal. - Send in a chat you opened for reading only, go past the daily cap (default 5 across all your agents), or have a send retried automatically. - Reply with a quote or react with an emoji. Those exist only in the [HTTP API](https://usecircles.app/en/whatsapp-api-personal-number). - Keep access after you disconnect it. Disconnecting ends it at once, and every request it made stays in your activity log. ## Questions and answers ### Can Grok read my WhatsApp? Yes, with Circles: add Circles as a remote MCP server with a token, and Grok reads the WhatsApp chats you opened, from your personal number. ### Is this a Grok WhatsApp number? No. Circles gives Grok your chosen WhatsApp chats to read, and to write in only where you allow. ### Can Grok connect with the address alone? Not tried yet. Grok adds remote MCP servers as custom connectors; connect it with a token in the header, like any remote MCP client. ### Does this work with other MCP clients? Yes, any client that takes a remote MCP server over HTTP with a custom header. Make a token under *Other*, and give it the address and header above. ### Can Grok send WhatsApp messages? Only if the token allows sending, and only in chats you opened for sending, within your daily cap. A send is never retried automatically. ## Keep reading - [Every agent](https://usecircles.app/en/agents): How each one connects, side by side. - [The HTTP API](https://usecircles.app/en/whatsapp-api-personal-number): For agents that do not speak MCP. - [What the agent can reach](https://usecircles.app/en/security): Per-chat permissions and the activity log. --- 14 days free. Link your number, pick the chats, then connect Instinct with one tap or Claude, ChatGPT and Codex with one address. Start: https://usecircles.app/start?agent=grok&lang=en