The Audienca MCP server speaks streamable HTTP and authenticates over OAuth 2.0. Claude Code needs the address and nothing else — the server advertises its own tools and schemas.
claude mcp add --transport http audienca https://api.senseaition.com/audienca-api/mcp Run this in the project where you want Audienca available. Without a scope flag the server is added for this project only.
claude mcp add --transport http audienca https://api.senseaition.com/audienca-api/mcp Start Claude Code and run /mcp. The server answers the first call with 401, Claude Code flags it and opens the OAuth flow in your browser. Pick the scopes you want to grant.
/mcp Ask Claude to list your projects. If the tools are wired up, the answer comes from your account, not from a guess.
List my Audienca projects. The server understands two scopes. Grant only the first if the assistant should never change anything — reading reviews and drafting replies still works, because drafts go through your approval either way.
audienca:read Read projects, inquiries, resources and automation rules.
audienca:write Create and change projects, resources, drafts and automation rules.
A .mcp.json in the repository root makes the server available to everyone who clones it — Claude Code and Cursor pick it up automatically. The type field is mandatory: an entry with a url but no type is read as a stdio server and skipped.
{
"mcpServers": {
"audienca": {
"type": "http",
"url": "https://api.senseaition.com/audienca-api/mcp"
}
}
} Every tool ships a full JSON schema, so an agent can discover parameters without documentation. Names are stable.
Finish the job: pick a draft, revise it, send it
Numbers and themes instead of fetching one by one
Reviews, comments and messages
With a mandatory preview before anything changes
Who changed what, and whether it was revised
Where reviews come from, and whether a channel went silent
One project per business or client
The documents answers are grounded in
Rules for what runs unattended
Beyond tools, the server ships MCP prompts: ready-made questions your client offers as a shortcut, so nobody has to know which of the 51 tools answers them. Each one needs only a project; time ranges default sensibly.
warum_schlechte_bewertungen was_hat_sich_verschlechtert schlechte_bewertungen_als_liste kanalvergleich testimonials_finden wer_beschwert_sich betriebsueberblick MCP is an open standard, so the server is not tied to one client. What differs is only where you paste the address.
Settings, then Connectors. Add a custom connector with the URL below; ChatGPT runs the OAuth flow itself.
Settings, then MCP. Add the server as type "http" with the same URL. Cursor also reads a .mcp.json from the repository root.
Settings, then Connectors, then Add custom connector. Same URL, same OAuth flow as Claude Code.
Any client that speaks the Model Context Protocol works. It needs a streamable HTTP endpoint and OAuth 2.1 — nothing beyond the standard.
https://api.senseaition.com/audienca-api/mcp You are not signed in yet. Run /mcp and complete the OAuth flow. Until then the server answers every call with 401.
Your .mcp.json entry has a url but no type. Add "type": "http". streamable-http works as an alias.
Your token probably carries audienca:read only while the tool needs write access. Re-run the OAuth flow and grant the write scope.
MCP access is included in every plan, from the free trial through Enterprise. There is no separate activation.
Claude and Claude Code are trademarks of Anthropic. ChatGPT is a trademark of OpenAI. Cursor is a trademark of Anysphere. None of them belong to us, and none of these companies endorse or sponsor Audienca. We name them because our server works with their products — that is all the connection there is.