Saut MCP for developer tools
Connect Saut to your existing tools with the Model Context Protocol server.
The Model Context Protocol is the emerging standard for letting models talk to external systems in a structured way. As of today, Saut is exposed as a first-class MCP server. Any tool that speaks MCP — Claude Desktop, Cursor, the Anthropic API, Zed, and a growing list of editors — can now query Saut directly without going through a brittle scraping layer.
What you can do with it
- Pull voices, sentiment, and trajectory data for any poll the workspace has access to.
- Create polls from inside the editor, with the model itself drafting the question.
- Subscribe to alert events and react to them in code, without writing a webhook handler.
- Run cohort comparisons across regions or platforms from a single tool call.
Auth and scoping
Every MCP connection is scoped to a workspace API key. The key controls what the connected agent can read and what it can mutate, and every call is logged to the workspace audit trail. Revoking a key terminates every active MCP session that key was holding open within a few seconds.
Get started
The connection URL and configuration snippets for every supported client live in the workspace settings under Integrations. The protocol itself is unversioned — Saut tracks the public MCP spec and will support breaking changes at the spec level, not at the client level.