Getting Started with the DigitalPilot MCP Server

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.
• Manage lead-capture forms.
• Configure and test webhooks.
• Run Google Ads reporting and optimization actions.

First-Run Checklist

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

Best Practice Workflow

1. Confirm context with get_workspace_info.
2. Pull overview/reporting (get_report_overview, get_report_channel, get_report_utm, list_leads).
3. Drill into specific domains (get_domain_activities, get_company_info).
4. Apply controlled changes (forms, 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/forms without listing existing ones first.