Perisclaw plugin & MCP server
Use Perisclaw from ChatGPT, Codex, Claude, and other compatible AI tools.
You can use your Perisclaw WhatsApp from ChatGPT, Codex, Claude, Cursor, and other compatible AI clients. Ask it to “summarize my unread chats,” “reply to Sarah,” or “find the address Priya sent last month,” and it works through your existing assistant.
In ChatGPT, Codex and Claude, Perisclaw is an installable plugin. The plugin bundles two parts: Perisclaw’s live WhatsApp connector, powered by its MCP server, and a skill that teaches the client safe WhatsApp workflows. Other AI clients can connect directly to the same MCP server.
This is the mirror image of connecting apps: there, Perisclaw uses your other tools; here, your other tools use Perisclaw.
ChatGPT and Codex
Install the Perisclaw plugin from the Plugins directory, connect your Perisclaw account, and choose Read only or Read & write access. The public listing appears after OpenAI approves it.
During the developer preview, enable developer mode and add the production MCP URL shown on the MCP page in the Perisclaw web app. This preview connection uses the same consent screen and WhatsApp tools as the plugin.
Claude
Add the Perisclaw plugin from Claude's directory, connect your Perisclaw account, and choose Read only or Read & write access. It works in Claude on the web, desktop and mobile, in Cowork, and in Claude Code. The public listing appears after Anthropic approves it. The plugin's source is public at periskope-org/perisclaw-plugin.
Until then, add Perisclaw as a custom connector as described below.
Other MCP clients
Clients such as Claude Desktop and Claude.ai support one-click connectors:
- 1
Add Perisclaw's connector
In your AI client, add a new connector or MCP server and paste the Perisclaw MCP address from the MCP page in the web app.
The client shows Perisclaw as a new connection. - 2
Sign in
The client opens a Perisclaw login in your browser. Because you are already signed in to the web app, you just see a consent screen. New to Perisclaw? Create your account and connect your WhatsApp in that same window.
The consent screen names the client requesting access. - 3
Choose what it can do
Pick an access level, Read only or Read & write, then approve.
The client can now use your WhatsApp tools.
Choose the right access level
| Access level | What the client can do |
|---|---|
| Read only | Search and read your chats, contacts, groups, and Automations. Cannot send or change anything. The safe default. |
| Read & write | Everything in Read only, plus sending messages, reacting, managing chats, groups, labels, and contacts. |
What you can do from your AI client
- Catch up: “Summarize everything I missed in my work groups today.”
- Search: “Find the address Priya sent me last month.”
- Reply (with Read & write): “Reply to Sarah that Tuesday at 3 works.”
- Organize (with Read & write): “Label all the unanswered client chats ‘follow up.’”
The plugin’s bundled skill resolves recipients before acting, treats message content as data rather than instructions, and asks before sending or making destructive changes. Standalone coding clients such as Claude Code or Cursor can layer the same open Perisclaw workflow skill on top of a plain MCP connection.
Attachments
Ask for a file on a message, like “download the PDF in that invoice.” Files up to 10 MB arrive directly in your AI client.
To send a file, ask for it, like “send report.pdf to Priya.” Files can be up to 25 MB. Clients that run on your computer, like Claude Code, Codex, and Cursor, upload the file for you. In ChatGPT, attach the file to your message. Any client can also send a file from a public link.
Staying in control
- Scoped to you: a connection only ever reaches your own WhatsApp; it cannot touch anyone else’s.
- Sends are still gated: messages sent from an AI client go through the same permission checks as everything else.
- See every grant: the web app labels each connected client as Read only or Read & write, and flags clients that still have live sessions at both levels.
- Revoke anytime: remove a connection from the web app and the client immediately loses access.
- Stays signed in: a connected client stays signed in while you use it. Cursor asks you to sign in again every 30 days.
For the bigger picture on what your assistant can and cannot touch, see Privacy & security and Permissions & access.