Adrapid

@adrapid show me all banners with status 'ready' so I can see what's currently live in production

Found 12 banners with status 'ready'. Here's a summary: 5 are display ads (728×90 leaderboards), 4 are social media banners (1200×628 Facebook), and 3 are mobile banners (320×50). The most recent is 'Q1-promo-hero' created 3 days ago. All are tagged with campaign ID 'spring-launch-2024'. This illustrative example shows how the MCP returns banner metadata including dimensions, format, and campaign associations.

This example demonstrates the List Banners tool with status filtering. Requires an API key with read access to your Adrapid account. The actual response structure depends on how many banners exist in your workspace and what metadata fields you've configured. Useful for auditing creative assets before a campaign launch.

@adrapid what's my current account info and which API version am I using?

Your Adrapid account is registered to team@example.com with plan tier 'Professional'. You're currently using API version 2.1.0, which is the latest stable release. Your account has 847 banners created this month, with 2,153 remaining in your monthly quota. This illustrative example shows the kind of account-level metadata the MCP surfaces when queried.

This example uses the Get user and API info tool to retrieve authenticated account details. Helpful for debugging quota issues or confirming which API features are available to your plan tier. Requires a valid API key; the MCP won't expose credentials but will show usage limits and versioning.

@adrapid check the API capabilities and tell me if there's a way to bulk-generate banner variations from a template

The Adrapid API (version 2.1.0) supports banner creation, listing, and status management. Based on the API root information, the service focuses on managing existing banners rather than templated generation. For bulk workflows, you'd need to call the creation endpoint multiple times with different parameters. This illustrative example shows how the MCP helps you understand API scope before building an integration.

This example demonstrates the Get API info tool, which reveals the MCP's available capabilities. Useful when planning automation workflows or assessing whether Adrapid fits your creative production pipeline. The MCP surfaces API metadata but doesn't extend beyond what the vendor's API exposes—no built-in templating if the API lacks it.

When Adrapid fits a small paid-ads team's banner workflow

A 3-person growth team running display campaigns across Google and Meta needs to track which banner variants are live, paused, or awaiting approval. Adrapid's List Banners tool lets them pull status snapshots directly into Switchy without logging into the vendor dashboard. The filter-by-status parameter means they can script a daily standup check: "show me all banners marked 'ready' but not yet deployed." This works cleanly if your team creates fewer than 50 banners per week and you already use Adrapid as your creative production tool. If you're generating hundreds of variants or using multiple creative platforms, the 3-tool scope here is too narrow—you'll spend more time context-switching than you save. For small teams with a single creative vendor, this MCP turns banner audits into a 30-second Switchy query instead of a 10-minute dashboard crawl.

Why solo consultants should skip this MCP for now

A freelance ad-ops consultant managing 8 client accounts wants to pull banner delivery stats into weekly reports. Adrapid's MCP doesn't help here: the three available tools retrieve API metadata and list banner records, but they don't expose performance metrics like impressions, CTR, or spend. The Get User and API Info tool confirms your auth is working, and List Banners shows creation timestamps, but neither surfaces the data clients actually pay for. If you're billing hourly and need to prove campaign ROI, you'll still export CSVs from Adrapid's web UI or hit their REST API directly. This MCP is a discovery layer, not a reporting layer. Wait for Adrapid to expose analytics tools through the server, or stick with your current export workflow until they do.

When this MCP saves 20 minutes in API integration setup

A 6-person agency dev team is integrating Adrapid into a client's martech stack and needs to verify API access before writing production code. The Get API Info and Get User and API Info tools let them confirm the API version, check authentication, and retrieve the root schema without reading Adrapid's docs or making test cURL requests. In Switchy, a junior dev can ask "what version of Adrapid are we authenticated against?" and get an answer in 5 seconds instead of hunting through Postman collections. This is a pure setup-time win: once the integration is live, these tools have no ongoing value. If your team onboards a new ad platform every quarter, the MCP pays for itself in reduced Slack questions. If you're a one-client shop, the 20-minute savings isn't worth adding another MCP to your workspace.