What a marketing MCP connection should actually do
Understand marketing MCP tools, account permissions, source freshness and approval-based actions.
Connect a question to an authorized source
A marketing MCP server exposes defined tools to a compatible AI client. A useful tool can list available accounts or retrieve a campaign report. The connection does not replace account ownership, permissions or the platform API. Know which business and account a request is accessing.
Keep metric definitions visible
Spend, conversions and revenue may use different attribution windows, currencies and time zones. A trustworthy answer identifies the source, date range and definition. Website purchases, paid orders and delivered orders can be different numbers. Reconcile them before deciding that an advertisement is profitable.
Separate reading from changing
Reading a report is different from pausing a campaign or increasing a budget. Changes should have a clear proposal, an identified account, a reviewed diff and an approval record. A natural-language instruction should not silently remove existing controls.
Keep every client separate
An agency should authorize each customer independently. Customer tokens belong in a secure connector runtime, not in prompts, frontend code or shared documents. Tool results should return only the authorized business data. Test isolation with two restricted users, not only an administrator.
TechRewa scope
The TechRewa developer surface introduces project and capability access. External advertising connectors require their own account authorization and implementation. A visible integration card is not evidence of a connected Google Ads or Meta account. Start with a narrowly defined reporting use case and expand after reconciliation.