Overview
What is mcp-adjust?
mcp-adjust is a simple MCP server that interfaces with the Adjust API, allowing users to query reports, metrics, and performance data from their Adjust account using any MCP client such as Cursor or Claude Desktop.
How to use mcp-adjust?
Obtain an Adjust API key from your Adjust account settings. Install via Smithery with npx -y @smithery/cli@latest run @bitscorp/mcp-adjust --config "{\"apiKey\":\"YOUR_ADJUST_API_KEY\"}" or clone the repository, run npm run build, and point your MCP client to the built script with the API key as an argument.
Key features of mcp-adjust
- Interfaces with the Adjust API for report and metric queries.
- Works with any MCP client (Cursor, Claude Desktop, etc.).
- On-demand lookup of performance data such as install numbers.
- Simple installation via Smithery or local clone.
- Supports natural language queries like “What’s the install numbers for the Feb 1 campaign?”
Use cases of mcp-adjust
- Querying install numbers for a specific campaign or date range.
- Checking revenue reports for the last 7 days.
- Monitoring performance metrics directly from a chat interface.
FAQ from mcp-adjust
What do I need to use mcp-adjust?
You need an Adjust API key from your Adjust account settings and an MCP client such as Cursor or Claude Desktop.
How do I install mcp-adjust?
You can install via Smithery using the provided npx command, or clone the repository, run npm run build, and configure your MCP client to run the built script with your API key.
What data can I query with mcp-adjust?
You can query reports, metrics, and performance data from Adjust, including install numbers and revenue for specific periods or campaigns.
Does mcp-adjust support all Adjust API endpoints?
The README states that coverage of the Adjust API is being added over time; currently it supports reports, metrics, and performance data. Additional endpoints may be added in the future.
How is the API key transmitted?
The API key is passed as a command-line argument or configuration when starting the server. The README does not specify additional transport or authentication details beyond the API key.
