
🏆 Audiense Demand MCP Server
MCP Server to interact with the Demand API
What is Audiense Demand MCP Server?
Audiense Demand MCP Server is a server designed to interact with the Audiense Demand API, allowing users to create and analyze demand reports, track entity performance, and gain insights across various channels and countries.
How to use Audiense Demand MCP Server?
To use the server, you need an authorized Audiense account. Follow the provided user or developer guides to set up the server and start creating demand reports.
Key features of Audiense Demand MCP Server?
- Create and manage demand reports for specified entities.
- Retrieve lists and detailed information about demand reports.
- Analyze report summaries by channels and countries.
- Access YouTube and Google search volume summaries for entities.
Use cases of Audiense Demand MCP Server?
- Businesses can generate demand reports to understand market trends.
- Marketers can track entity performance across different platforms.
- Analysts can gain insights into consumer behavior through detailed reports.
FAQ from Audiense Demand MCP Server?
- What is required to use the server?
An authorized Audiense account is necessary to access the Audiense Demand API.
- Is there a guide for non-developers?
Yes, there is a user guide tailored for business users and non-developers.
- Can developers contribute to the project?
Yes, there is a developer guide that includes contributing guidelines.
🏆 Audiense Demand MCP Server
This server, based on the Model Context Protocol (MCP), allows Claude or any other MCP-compatible client to interact with your Audiense Demand account. It provides tools to create and analyze demand reports, track entity performance, and gain insights across different channels and countries.
This MCP server is designed to work with the Audiense Demand API and requires an Audiense account authorized to use Audiense Demand.
We provide two different guides based on your background and needs:
🌟 For Business Users and Non-Developers
If you're primarily interested in using the Audiense Demand tools with Claude or another "MCP compatible" tool and don't need to understand the technical details, follow our User Guide. This guide will help you:
- Install the necessary software quickly
- Set up Claude Desktop
- Start creating and analyzing demand reports
- Troubleshoot common issues
🛠️ For Developers and Technical Users
If you're a developer, want to contribute, or need to understand the technical implementation, follow our Developer Guide. This guide covers:
- Detailed installation steps
- Project architecture
- Development setup
- Advanced configuration
- API documentation
- Contributing guidelines
🛠️ Available Tools
create-demand-report
📌 Description: Creates a new demand report for specified entities.
-
Parameters:
title
(string): Title of the demand reportentitiesReferences
(array of strings): Array of entity names for the reportuserEmail
(string): Email of the user creating the report
-
Response:
- Report creation details in JSON format
get-demand-reports
📌 Description: Retrieves the list of demand reports owned by the authenticated user.
-
Parameters:
paginationStart
(number, optional): Pagination start indexpaginationEnd
(number, optional): Pagination end index
-
Response:
- List of reports in JSON format
get-demand-report-info
📌 Description: Fetches detailed information about a specific demand report.
-
Parameters:
reportId
(string): The ID of the report to get information for
-
Response:
- Full report details in JSON format
get-demand-report-summary-by-channels
📌 Description: Gets a summary of the report broken down by channels.
-
Parameters:
reportId
(string): The ID of the report to get the summary forcountry
(string, default: "Weighted-Total"): The country to filter byoffset
(number, default: 0): Pagination offsetentityNames
(array of strings, optional): Optional array of entity names to filter by
-
Response:
- Channel-wise summary data in JSON format
get-demand-report-summary-by-countries
📌 Description: Gets a summary of the report broken down by countries.
-
Parameters:
reportId
(string): The ID of the report to get the summary forplatform
(string, default: "all_platforms"): Platform name to analyzecountries
(array of strings): Array of country codes to analyzeoffset
(number, optional): Pagination offsetentityNames
(array of strings, optional): Optional array of entity names to filter by
-
Response:
- Country-wise summary data in JSON format
get-youtube-search-volume-summary
📌 Description: Gets YouTube search volume summary for entities in a report.
-
Parameters:
reportId
(string): The ID of the report to get the summary forcountry
(string, default: "Global"): Country code to analyzeentityNames
(array of strings, optional): Optional array of entity names to filter by
-
Response:
- YouTube search volume data in JSON format
get-google-search-volume-summary
📌 Description: Gets Google search volume summary for entities in a report.
-
Parameters:
reportId
(string): The ID of the report to get the summary forcountry
(string, default: "Global"): Country code to analyzeentityNames
(array of strings, optional): Optional array of entity names to filter by
-
Response:
- Google search volume data in JSON format
check-entities
📌 Description: Checks if entities exist and gets their details.
-
Parameters:
entities
(array of strings): Array of entity names to check
-
Response:
- Entity status information in JSON format
📄 License
This project is licensed under the Apache 2.0 License. See the LICENSE file for more details.