DigitalPilot

DigitalPilot is an attribution platform for B2B SMBs running paid campaigns. It identifies which companies visit your site from which ads, so you can see exactly which campaigns drive qualified leads.

Install

Install and configure the MCP from https://www.digitalpilot.app/support/getting-started-with-digitalpilot-mcp-server now. Follow the documentation's installation instructions, ask me for anything you can't complete yourself, and verify its tools load.

View documentation

README

Getting Started with the DigitalPilot MCP Server

New to MCP? Learn how to connect the DigitalPilot MCP server, verify workspace context, and safely move from reporting to controlled actions.

Who This Is For

New users connecting an AI agent to DigitalPilot data and actions.

What This MCP Server Does

The DigitalPilot MCP server lets your agent:

Read workspace identity and scope access.
Pull traffic, channel, UTM, lead, and domain activity reports.
Manage target-account lists.
Configure and test webhooks.
Run Google Ads reporting and optimization actions.

First-Run Checklist

Connect/authenticate the MCP server in your client.
Run get_workspace_info to confirm context (tagId, email, scopes, optional Google Ads IDs).
If needed, run list_webhooks and list_target_account_lists to inventory what already exists.
Start with read-only reporting tools before mutation tools.

Best Practice Workflow

Confirm context with get_workspace_info.
Pull overview/reporting (get_report_overview, get_report_channel, get_report_utm, list_leads).
Drill into specific domains (get_domain_activities, get_company_info).
Apply controlled changes (webhooks, target accounts, Google Ads updates).

Common Pitfalls

Running Google Ads tools before checking connected customerId context.
Mixing up grouped reports (get_report_channel) with row-level company listing (get_report_overview).
Creating duplicate webhooks without listing existing ones first.

Phone Call

Mon-Fri, 9am-5pm EST

Contact Form

We reply within 1 business day