Voluum MCP server icon

Voluum

by Voluum

Analytics196 tools

Analyse and manage Voluum ad-tracking campaigns from your AI assistant. Read-only by default, write access opt-in. 196 tools, OAuth sign-in, works with any MCP client.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Voluum via MCP

https://mcp.voluum.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Voluum Tools & Capabilities (196)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Write mode is a real risk surface. Voluum's own action prompts pause campaigns and rewrite cost data. Start read-only; grant write access deliberately.
  • Voluum warns about confident wrong answers. Its documentation states plainly that assistants produce well-formatted answers the underlying data does not support, and supplies prompt rules to counter it. That warning comes from the vendor, not from us.
  • Analysis is easy to get wrong. Voluum specifically cautions against blending workspaces and against mixing VISIT and CONVERSION time modes within one comparison, saying late-funnel comparisons will otherwise show false drops.
  • Cross-system prompts need a second integration. Voluum's most valuable documented workflows assume the traffic source's API is also connected to the assistant.
  • We could not read tool schemas. OAuth-gated, so the 196 count is the directory's and parameter-level detail is not published here.

Frequently asked questions

Can the Voluum connector change your campaigns, or only read them?

Both, but read-only is the default. Voluum documents two access modes and describes write access as opt-in, so an assistant cannot pause a campaign or correct a cost until you grant it. Voluum states the MCP server itself enforces what the AI can and cannot do.

How do you sign in to the Voluum MCP server?

With OAuth 2.0 using your normal Voluum credentials. Voluum documents that you log in once and the assistant receives a scoped token, rather than pasting an API key. We confirmed the endpoint returns an authentication challenge when contacted anonymously on 2026-08-16.

Which AI assistants work with Voluum MCP?

Any MCP-enabled client. Voluum names Claude, ChatGPT, Perplexity, Cursor AI and custom bots, and publishes separate setup pages for several of them. Because it is a standard MCP server over streamable HTTP, other clients including Agentman connect the same way.

How do you stop an AI assistant inventing numbers from your campaign data?

Voluum publishes a safeguard for this. Its documentation warns that assistants produce confident answers even when the data does not support them, and supplies rules to prepend to any analysis prompt requiring every reported number to trace back to a query actually run.

Why does Voluum tell you to keep workspaces separate?

Because blending them misleads. Voluum's guidance states that KPIs and economics differ across workspaces, so combining them produces misleading aggregates, and advises telling the assistant which workspace to scope to. It gives similar advice about keeping conversion-time mode consistent within a comparison.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Analytics
Developer
Voluum
Tools
196
Domain
mcp.voluum.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.