🏆 Audiense Demand MCP Server
@AudienseCo
MCP Server to interact with the Demand API
Overview
What is Audiense Demand MCP Server?
This MCP server enables Claude or any MCP-compatible client to interact with an Audiense Demand account. It provides tools to create and analyze demand reports, track entity performance, and gain insights across channels and countries. It is designed for users with an Audiense account authorized to use Audiense Demand.
How to use Audiense Demand MCP Server?
Follow the User Guide for business users (non-developers) to install necessary software and set up Claude Desktop. For technical users, the Developer Guide covers detailed installation, project architecture, and advanced configuration. Both guides are linked in the README.
Key features of Audiense Demand MCP Server
- Create new demand reports for specified entities
- Retrieve the list of demand reports owned by the user
- Fetch detailed information about a specific demand report
- Get channel‑wise and country‑wise report summaries
- Obtain YouTube and Google search volume summaries
- Check if entities exist and retrieve their details
Use cases of Audiense Demand MCP Server
- Automate the creation and retrieval of demand reports for competitive analysis
- Monitor brand performance across YouTube and Google search volumes
- Analyze entity trends by country and channel without manual API calls
- Integrate demand intelligence directly into AI‑assistant workflows
- Quickly verify entity data before generating reports
FAQ from Audiense Demand MCP Server
What do I need to use this server?
An Audiense account that is authorized to use Audiense Demand, plus a compatible MCP client (e.g., Claude Desktop).
Can I use this server with tools other than Claude?
Yes, it works with any MCP‑compatible client.
How do I install the server?
Refer to the User Guide (for business users) or the Developer Guide (for technical users) in the repository’s README for step‑by‑step instructions.
Where is my data processed?
All data is handled through the Audiense Demand API. No data is stored locally by the server beyond the current session.
What transport does the server use?
The README does not specify a transport; it is assumed to be stdio or HTTP as typical for MCP servers, but you should check the project’s documentation for details.