Adzviser MCP

Live

API KEY

ADVERTISING ANALYTICS

Marketing

Every ad account, cross-channel campaign, and performance metric your team tracks lives in Adzviser. Adzviser MCP gives your agent authenticated access to advertising analytics scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Adzviser MCP account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Adzviser MCP
agent · Acme Q3
Run
Compare our Google vs Meta spend and ROAS for this month vs last month.
S
adzviser_performance_compare
88ms
Ad analytics agent
This month: Google $18.4K spend, ROAS 3.2x; Meta $12.1K, ROAS 2.8x. vs last month: Google up 12% spend, ROAS flat; Meta down 8% spend, ROAS improved 0.4x. Google driving better return.
Sources: Google Ads, Meta Ads, this month vs last month
adzvvisermcpmcp
2 platforms
18:29
Message Claude...

Tools your ad analytics agent reaches for on Adzviser MCP, scoped per user.

CALL ANY TOOL
List ad accounts, pull cross-channel metrics, compare periods, and generate consolidated reports.
adzviser_accounts_list
List ad accounts
List all ad accounts connected to the Adzviser workspace.
Parameters
Name
Type
Required
Description
platform
string
Optional
Filter by platform: google, meta, tiktok, linkedin
adzviser_campaigns_list
List campaigns
adzviser_metrics_get
Get campaign metrics
adzviser_performance_compare
Compare periods
adzviser_report_get
Get cross-channel report
Build your Agent
Drop the toolkit in, point it at the user, and your ad analytics agent can use Adzviser MCP from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["adzvvisermcp"], toolNames: ["adzviser_accounts_list", "adzviser_campaigns_list", "adzviser_metrics_get"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["adzvvisermcp"], toolNames: ["adzviser_accounts_list", "adzviser_campaigns_list", "adzviser_metrics_get"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["adzvvisermcp"], toolNames: ["adzviser_accounts_list", "adzviser_campaigns_list", "adzviser_metrics_get"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/adzvvisermcp",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Adzviser MCP.
Accounts & campaigns
Copy the prompt
Copied
List all connected ad accounts.
Copy the prompt
Copied
Show active campaigns across all platforms.
Copy the prompt
Copied
Which campaigns are paused right now?
Copy the prompt
Copied
Get metrics for [campaign name] last 30 days.
Performance & compare
Copy the prompt
Copied
Compare Google vs Meta spend this month.
Copy the prompt
Copied
Which campaigns have ROAS above 3x?
Copy the prompt
Copied
Compare [campaign] this month vs last month.
Copy the prompt
Copied
Cross-channel spend breakdown today.
Reporting
Copy the prompt
Copied
Consolidated report for all platforms this week.
Copy the prompt
Copied
Top 5 campaigns by conversion volume.
Copy the prompt
Copied
Which ad sets have CPA above target?
Copy the prompt
Copied
Platform performance trend last 90 days.
SEE HOW AUTH WORKS
Users authorize Adzviser MCP once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Adzviser MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Adzviser MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Adzviser MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Adzviser MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other ad analytics agents and MCP connectors. Working code, live demos, fork what fits.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Adzviser MCP today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Adzviser MCP as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Adzviser MCP api key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Adzviser MCP?
Yes. Pass a tool name filter to listScopedTools so the ad analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Adzviser MCP.
What happens when a user revokes Adzviser MCP access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent access ad accounts from other platforms the user hasn't connected?
Only platforms the authorizing user has connected to their Adzviser workspace. Disconnected or unauthorized ad accounts return no data. Access mirrors the user's native Adzviser connections.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""adzvvisermcp"": {
""url"": ""https://mcp.scalekit.com/adzvvisermcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.adzvvisermcp]
url = ""https://mcp.scalekit.com/adzvvisermcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""adzvvisermcp"": {
""url"": ""https://mcp.scalekit.com/adzvvisermcp"",
""type"": ""http""
}
}
}