RevenueOS MCP — AI Assistant Access to Retail Media Revenue | Particular Audience
Connect your AI assistant to RevenueOS: retail media accounts, campaigns, pipeline, delivery performance and inventory forecasts, signed in as you under your existing permissions.
MCP server
Your retail media bookings, delivery and pipeline — one question away.
RevenueOS MCP lets retail media sales and AdOps teams ask their AI assistant about accounts, campaigns, pipeline, performance and inventory in RevenueOS. It signs in as you and only sees what your RevenueOS permissions already allow.
Status: Available to RevenueOS workspaces.
Read: Accounts — List the retail media advertiser accounts you work with. Campaigns — Search campaigns and insertion orders by advertiser, status or dates. Pipeline summary — Booked and proposed retail media value by stage. Campaign performance — Delivery against booking for a campaign. Inventory forecast — Forecast available inventory before you sell it. Records — Read the related account, contact, contract and activity records you can already see.
Write (limited): Campaign notes — Add a note to a campaign, recorded against your name.
Today: Open the revenue tool, Search the advertiser, Check each campaign, Pull the forecast, Write it up for the team. With MCP: Ask one question in your assistant, Get pipeline, delivery and inventory together.
Sales: “What's in the pipeline by stage this quarter?” The assistant gathers: Booked and proposed retail media value by stage. What it unlocks: A pipeline view ready for your forecast call, without collating it by hand.
AdOps: “How is this campaign delivering against its booking?” The assistant gathers: Delivery against the booked campaign. What it unlocks: Spot under-delivery early and notify the right people — the call on any make-good stays with the retailer.
Planner: “How much homepage inventory is forecast for March?” The assistant gathers: Forecast available inventory. What it unlocks: Sell what's really available before you promise it.
Account lead: “Add a note that the client approved the creative.” The assistant gathers: The campaign record you can already edit. What it unlocks: Keep the record current from the conversation, logged under your name.
What it unlocks: Forecast calls, prepared — Pipeline by stage, ready when you ask. Delivery at a glance — Check any campaign against its booking without digging. Sell available inventory — Forecasts in the same conversation as the deal. One view of the advertiser — Accounts, contacts, contracts and activity you can already see. Notes without switching tools — Add a campaign note straight from your assistant. Your permissions, nothing more — The assistant sees exactly what you can see in RevenueOS.
Setup: 1. Add the connector — Add RevenueOS MCP to your AI assistant. 2. Sign in and approve — Sign in with RevenueOS and approve the assistant's access. 3. Ask — Pipeline, delivery and inventory, in plain words.
Trust: Signs in as you; Existing RevenueOS permissions; Only write: campaign notes, under your name; Never activates campaigns or makes commitments.
Who it's for: Retail media sales — Pipeline, accounts and campaign status before every call. AdOps — Delivery against booking, so under-delivery is spotted and flagged early. Planners — Inventory forecasts before you sell. Leadership — Booked and proposed value by stage, on demand.
What's in the answer: Booked and proposed value by stage; Delivery against the booking for a campaign; Forecast available inventory; Campaigns and insertion orders by advertiser, status or dates; The related account, contact, contract and activity records you can already see.
What it doesn't do: Activating or pausing campaigns; Committing spend or signing contracts; Syncing with an external CRM; Pushing to finance or ERP systems; Changing bid floors or caps; Deciding make-goods: those stay with the retailer.
Works with AI assistants that support MCP connectors, such as Claude and ChatGPT, and with your own assistant or agent if it speaks MCP.
Getting started: Talk to us or your account team → Your RevenueOS workspace is enabled → Add the connector and sign in with RevenueOS → Ask your first question.
For IT and security: Sign-in — Each person signs in with their RevenueOS account and approves the assistant's access. Permissions — The assistant sees exactly what that person can see in RevenueOS. Writes — The only change it can make is adding a campaign note, recorded under the person's name. Removing access — Access follows the RevenueOS account. Remove or change the account and the assistant's access changes with it.
Pipeline: “What's proposed versus booked this quarter?” “Which deals are at the proposal stage for this advertiser?”
Campaigns: “Which campaigns go live next month?” “Show insertion orders for this advertiser this year.”
Delivery: “How is the Spring campaign delivering against its booking?” “Which campaigns are under-delivering?”
Inventory: “How much homepage carousel inventory is forecast for March?”
Records: “Who's the contact on this account?” “Add a note that the client approved the creative.”
How access works: Sign in with your RevenueOS account; you approve the assistant's access. Every call runs as you, under the same permissions you have in RevenueOS. The assistant never touches users and roles, billing plans, commissions, accounting integrations, month locks or revenue recognition. No automatic campaign activation and no contractual spend commitments are made through the assistant.
Ask things like: “Which campaigns for this advertiser go live next month?” “How is this campaign delivering against its booking?” “What's in the pipeline by stage this quarter?” “How much inventory is forecast for the homepage carousel in March?” “Add a note that the client approved the creative.”
Can the assistant book or activate a campaign? No. It reads, and can only add campaign notes. Activation and commitments stay with your team in RevenueOS.
Does it bypass permissions? No. It acts as the signed-in person and sees only what they can already see.
Which assistants work? Any assistant that supports MCP connectors with sign-in, such as Claude or ChatGPT.
Which AI assistants work with it? Works with AI assistants that support MCP connectors, such as Claude and ChatGPT, and with your own assistant or agent if it speaks MCP.
Can it activate a campaign or commit spend? No. It reads, and it can add campaign notes. Activation and commitments stay in your normal process.
Does it see insertion orders? Yes. Search campaigns and insertion orders by advertiser, status or dates.
Can it forecast inventory? Yes. Ask for forecast available inventory before you sell it.
What happens if a campaign is under-delivering? The assistant shows delivery against booking so you can notify the right people. Any make-good is the retailer's decision.
Does it sync with our CRM or finance system? No. It works with what's in RevenueOS.
Who can see what? Everyone keeps their existing RevenueOS permissions. The assistant never sees more than the person using it.
How do we turn it off? Remove the connector from your assistant, or ask us to switch it off for your workspace.
RevenueOS MCP
Retail media bookings, delivery and pipeline from your AI assistant.
Works with
- RevenueOS — Account planning, booking, delivery, billing and cash.