Read your data
These tools mirror Statisfy’s data model, and only read:Work across Statisfy
These tools reach the rest of Statisfy: reports, campaigns, email templates, surveys, knowledge bases, skills, Agent Studio, digital workers, workspace setup, and more. Each call runs as you, within your role.list_api_operations lists only the operations your role and your workspace’s products allow, so Claude isn’t offered one Statisfy would refuse.
Build your portals
If your workspace has Portals, the connector has tools to work on your customer portals. Reading a portal needs Portals access; editing one needs a role that can manage portals (Admin or Builder).How a portal change reaches a preview
Your assistant follows a fixed path, and each step is a separate tool, so you can stop at any point:- Pick the portal. It lists your portals and confirms which one you mean.
- Read. It lists the files and reads the ones it needs.
- Edit the draft. Writes go to your draft, not the live site.
- Validate. A dry run of the save checks, committing nothing.
- Save. Commits the draft and starts a build.
- Build. It checks until the build finishes, or reports the error to fix.
- Deploy a preview. It deploys to a preview URL and shares the link.
- You go live, in Portal Studio, yourself. The assistant can’t publish to your live site.
Edits are made against a specific version of the portal. If the portal changed in the meantime, for example because you edited it in Portal Studio, the write is refused rather than overwriting your work.
Reading the full content of an activity
By default, your assistant sees an activity’s overview, such as its subject, summary, and message count, but not the messages themselves. To see what was actually written, ask for the messages explicitly. For example:- “Show me every message in the email thread with Acme from last Tuesday.”
- “Get the full Email Details for this activity, including the sender, time, and body of each message.”
- “What did the customer say in the latest messages on this support ticket?”
- Subject, sender, recipients, and time sent
- The message body, and the names of any attachments
- A message ID from the source system, for example the email’s Message-ID
What you get is the text Statisfy captured when the activity was synced:
- For email, this is the plain-text version, with quoted earlier replies and signatures removed. Attachments are listed by name only; their contents aren’t included.
- bcc recipients are never returned.
- You only see activities that your Statisfy user can see in the app.
Transport
Statisfy serves MCP over the Streamable HTTP transport from the MCP specification, onPOST https://api.statisfy.com/mcp. Claude and other spec-compliant MCP clients use it automatically when you connect. The older HTTP+SSE transport isn’t supported: GET /mcp returns 405 Method Not Allowed.