mcp -triplewhale

This MCP server exposes Triplewhale capabilities to MCP clients using a Node.js-based server. It enables natural language queries to interact with Triplewhale data, such as retrieving meta spend, revenue, and ad performance through plain-text prompts. The server is designed to run locally after installation and can be started with Node, pointing to the built entry point (dist/index.js). When connected to an MCP client, you can issue commands that the server translates into Triplewhale API calls and returns structured results. The included tooling emphasizes Claude Desktop integration and local development workflow, but the server is usable with any MCP client that adheres to the MCP standard. Tools supported by this server include the MOBY interface for data retrieval and command execution, enabling you to ask questions like “what was my meta spend in the last 7 days?” and receive actionable answers.

Prerequisites:

• Node.js >= 18.x
• npm (comes with Node.js)
• Access to the Triplewhale API and an API key

Installation steps:

1. Install the MCP server package globally or set up locally:

   • npm install -g @triplewhale/mcp-server-triplewhale
   • or install locally in your project: npm install @triplewhale/mcp-server-triplewhale

2. Build or prepare the server for local development (if required by the package):

   • npm run build

3. Obtain your Triplewhale API key from the Triplewhale console and store it in an environment variable (see environment notes).

4. Start the server using Node.js and point to the built entry (as per README examples):

   • node dist/index.js

5. If you are using Claude Desktop or another MCP client, configure the client to connect to this server per your MCP client’s instructions and provide the TRIPLEWHALE_API_KEY when initializing.

Optional for development workflow (Claude Desktop setup):

• Run: npx -y @triplewhale/mcp-server-triplewhale init $TRIPLEWHALE_API_KEY
• Restart Claude Desktop after starting the server.

Tips and notes:

• Ensure your TRIPLEWHALE_API_KEY is valid and has the necessary permissions for the operations you plan to perform.
• After making changes to server code, restart the MCP client (e.g., Claude Desktop) to ensure the new capabilities are loaded.
• The server currently lists MOBY as a supported tool; confirm that MOBY or any additional tools you rely on are enabled in your environment.
• If you encounter connection issues, verify network access, API key validity, and that the dist/index.js entry point exists after build.
• For development, keep an eye on the environment variable naming and ensure it is loaded by your runtime environment before starting the server.