Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Campaign Pack is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
90/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Turn a product photo and a brief into a full ad campaign: scripts, stills, client-ready PDF.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http campaign-pack-mcp https://tools.campaignpack.ai/mcp
# 2 — ask your agent for something these tools do
# start_campaign, check_campaign, get_pack and 10 more
Campaign Pack costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CAAll 1 server
campaignpack1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http campaign-pack-mcp https://tools.campaignpack.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Start a marketing campaign pack on Campaign Pack's own GPUs. Produces a campaign plan, ideas, ad and social scripts, a creator brief, and a client-ready PDF — plus product stills on the image sizes. Returns immediately with a job id; the run itself takes minutes, so poll check_campaign rather than waiting. Write the brief yourself from what the user told you: the richer and more specific it is, th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | What the product is, who it is for, what matters about it. A few sentences to a few paragraphs. State only facts the user gave you — invented metrics or customers end up in the finished pack. |
| brand | string | yes | The brand name, spelled exactly as the customer spells it. Every mention in the pack is rewritten to match this. |
| size | string | no | Pack size. Available here: 'text' (about a minute), 'lite' (about ten minutes). |
| photo | string | no | Workspace path from upload_product_photo. Required for the image sizes: the stills are edited from the real photo rather than generated from nothing. |
Progress of a running campaign: status, the tools it has just called, queue position, and whether it is waiting for a human approval. Poll about every 20 seconds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | Job id returned by start_campaign. |
Collect a finished campaign: the folder, its files, the written overview, and the path to the PDF.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | Job id returned by start_campaign. |
Campaigns on this account, newest first, including ones shared with it. Start here when you do not already have an id — the ids from start_campaign only exist in the conversation that made them, so this is how you find a campaign from last week.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many to return, newest first. Default 20. |
List files and folders in the account's workspace — campaign folders, scripts, product stills, PDFs, uploads. Directories end in '/'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | Folder to list, relative to the workspace. Omit or '.' for the top level. |
| session_id | string | no | Look inside a campaign shared with this account rather than its own files. Omit for your own workspace. |
Contents of a text file in the workspace — a script, the plan, the creator brief, a transcript. Large files are truncated. For a PDF, image or video call get_download_url instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | File path relative to the workspace, as shown by list_workspace_files. |
| session_id | string | no | Read from a campaign shared with this account rather than its own files. Omit for your own workspace. |
A link the person can open to get one file — the campaign PDF, a product still, a video. Works for any file in the workspace, including ones too big or too binary to read as text. The link expires within the hour.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | File path relative to the workspace, as shown by list_workspace_files. |
| session_id | string | no | Link a file from a campaign shared with this account rather than its own files. Omit for your own workspace. |
Put a product photo into the user's workspace so a campaign can edit stills from the real thing. Base64 of the image bytes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filename | string | yes | Name to save it under, with the extension — 'bottle.jpg'. Reusing a name that is already there replaces that photo. |
| data_base64 | string | yes | The image file's bytes, base64-encoded. The raw image, not a data: URL and not a path on your own machine. |
Give a teammate access to a campaign by email address — including while it is still running. They see the same live run from their own AI client or the website, can abort it, answer its approval prompts, and take the next turn. They must already have a Campaign Pack account; sharing does not create one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Campaign to act on — the session id from start_campaign or check_campaign. |
| string | yes | Email address of the person to let in. They must already have a Campaign Pack account under this address; sharing does not create one or send an invitation. |
Who owns a campaign and who it is shared with.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Campaign to act on — the session id from start_campaign or check_campaign. |
Revoke a collaborator's access. Takes effect on their next request.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Campaign to act on — the session id from start_campaign or check_campaign. |
| string | yes | Email address of the collaborator to remove. The owner cannot be removed this way. |
Answer a paused run that wants to send the user's data somewhere outside Campaign Pack. Ask the person; never decide for them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | Job id returned by start_campaign. |
| decision | string | yes | What the person said: 'allow' to let the run go ahead, 'refuse' to deny it. This must be their answer, not yours. |
Stop a running campaign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | Job id returned by start_campaign. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Campaign Pack or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 90 / 100
Release 0.1.1 · scanned 8 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score90
Findings0 threat · 2 capability
Capabilityhigh
Coveragemanifest
Verificationnot in this report
Surface digestb0430461bf1b2b475dd74327722e2490c5a8ea5f1ad4d7319b208e7966fd1cf6
Score vectorthreat 100 → client 90
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| start_campaign | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| check_campaign | no tags | |
| get_pack | no tags | |
| list_campaigns | no tags | |
| list_workspace_files | sensitive-source | sensitive-source: keyword "list_files" |
| read_workspace_file | no tags | |
| get_download_url | untrusted-inputstate-write | untrusted-input: keyword "download"; state-write: declares readOnlyHint: false |
| upload_product_photo | state-write | state-write: declares readOnlyHint: false |
| share_campaign | state-write | state-write: declares readOnlyHint: false |
| list_campaign_access | no tags | |
| unshare_campaign | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| answer_approval | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| abort_campaign | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
get_download_url → list_workspace_files → answer_approval
A cross-tool exfiltration chain exists: get_download_url → list_workspace_files → answer_approval.
Supply chain and provenance
Integrityfirst-seen
Surface digestb0430461bf1b2b47
Scanned2026-11-08
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Campaign Pack can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.