<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=9151474&amp;fmt=gif">
Skip to content

Glossary · Data and operations

What is MCP, and what does it mean for MMM?

MCP, the Model Context Protocol, is an open standard that lets an AI assistant such as Claude, ChatGPT or Microsoft Copilot use an external system's tools and data. Odins exposes its platform as an MCP server, so customers run scenarios, forecasts and reports from the assistant they already use.

Reviewed November 2026

By the Odins team · Updated November 2026 · About 3 minutes

Definition

An AI assistant on its own knows nothing about your marketing data and cannot run a model. MCP is the protocol that connects it to systems that do. The system publishes a set of tools (run a forecast, list the channels, create a scenario, query the spend) and the assistant calls them in a conversation, in natural language, with the computation done on the system's side. Any assistant that speaks MCP can connect to any MCP server.

How Odins uses it

Odins is an MCP server. A customer connects their own Claude, ChatGPT or Copilot to it and asks the questions they would otherwise click through: how much do we need to spend next month to reach this target with 80% certainty; what would Odins have done differently last year, and how would it have turned out; which weeks should we lean into before Christmas. Every answer is computed by the Odins platform, the same scenarios and Monte Carlo runs the platform itself would produce, and returned with an explanation of what the numbers mean. The assistant does not estimate anything; it asks Odins. A scenario created in the chat sits in the platform with a link, so anything the assistant says can be checked.

The model's setup is exposed through the same door: how the channels are defined, how the priors were set, what the control variables are. A CFO gets a direct answer; an analyst can dig as deep as they want.

Why it matters

Since the launch, the large majority of platform use across Odins customers goes through the MCP, from the customer's own assistant rather than an Odins chatbot, and more people inside each customer use it than ever used the interface. Nobody has to learn a new tool. It is also the API: an agent connected to the MCP can forecast, create scenarios, write and pull data, so a data team that wants numbers on its own dashboard points its agent at the MCP, and the interpretation of each value is encoded in the server, so the agent knows what the results mean.

Before a model is built, the same connection lets a team talk to its history and media plans, and ask about the raw data at ad level.

  • Scenario planning: Forecasting what a budget would return before committing it, and comparing several futures side by side.
  • Structured marketing data: Every source, one dataset, your hierarchy, your warehouse. The foundation the model sits on, and a product on its own.
  • Forecast verification: Forecast first, compare with actuals afterwards. The only honest way to know whether a model is right.

Go one level deeper: Odins MCP. Marketing mix modelling from ChatGPT or Claude. Or go back to all terms in the glossary.

FAQ

Frequently asked questions.

Does the assistant hallucinate the numbers?

No. The numbers come from the Odins platform, which runs the scenarios and simulations and returns the actual results with an explanation. The assistant relays and explains; it does not estimate.

Which assistants work with Odins?

Claude, ChatGPT and Microsoft Copilot, and any other client that speaks MCP. The setup guides for each client are on the Odins MCP page.

Is there a separate API?

The MCP is the API. It can read and write: forecast, create scenarios, pull data. An agent connected to it can feed your own dashboards, with the meaning of each value encoded in the server.

Talk to our team

See it on your own numbers.

A 30-minute walkthrough of how this plays out for channels like yours, on a model built on your data.

Book a demo