Getting started with the Waild MCP beta

For beta testers · Part of the docs

Waild MCP is an MCP server: your AI agent connects to it and gains search-data tools. In the private beta the agent does the work — it creates and edits your marketing plans in conversation — while your dashboard handles sign-in, connections, and auditing what the agent saved. Here is the whole flow.

1. Sign in and apply

Open your dashboard and continue with your Google account, then choose how external API usage is funded:

• Bring your own API keys — your providers bill you for their API usage.
• Included API usage — a one-time complimentary credit the owner grants in an amount they choose. It does not renew, though the owner can add more later.

Accept the beta terms and apply. No payment details are required, and both plans need owner approval before service access turns on — you can use the dashboard while you wait. Either way, normal Waild MCP functions and workspace storage are unlimited under fair use; rate, concurrency and request-size limits protect reliability. External API usage is always separate and metered.

2. Connect your agent and data

Once approved, open Connections. Copy the public server URL shown there into your agent's remote-MCP or connector settings, then authorize with the same Google account you signed in with — that Google consent is what identifies and authorizes you, not the URL. Never use or share tokenized owner URLs or credentials. Then ask the agent which Waild MCP tools it can see; the beta exposes a focused set that grows in reviewed steps. If a connection check is offered before approval, it reaches only a read-only reference tool — it cannot see your data or paid services.

Each data service is optional:

• DataForSEO — Google search research. Included accounts simply enable it; searches draw on your credit. BYOK accounts enter the API login and API password from DataForSEO's API Access page — not your DataForSEO website sign-in password — and their provider charges them directly.
• Google data — the Google account whose Search Console (and Analytics, when enabled) data your agent may read. This is separate from your Waild MCP sign-in, and one Google data account serves both services. Google's testing program may require your account to be registered as a beta tester and can ask for fresh consent after seven days; if Google blocks the connection, contact the beta owner.
• Umami Cloud — paste your Cloud API key, which is stored encrypted, then choose which of its websites your agent may read.

Enter credentials only in these dashboard forms — never in chat, plans or saved evidence.

3. Work through your agent

Start with your website and what you want to achieve. Your agent can discover the relevant analytics sites and properties through the available tools, reuse an existing plan and ask for missing context. A listed tool does not mean its service is connected or that paid usage is authorized. You do not need to assign a website to a plan in the dashboard.

Creating and editing happen in conversation, not in dashboard forms. For example: “Create a marketing plan for example.com to grow organic trial sign-ups; I have about 2 hours a week.” The site, goal and hours are examples — state your own, and always name the website you mean: the dashboard does not assign sites to plans, so if it is ambiguous your agent should ask rather than guess.

Fast search answers immediately. When your agent offers slower, thorough research, it submits a search and collects the results later — usually minutes, sometimes 45 minutes or more — for more complete destination links. Research needs DataForSEO enabled, current approval and available funding; submitting uses your funding once, collecting is not another purchase, and Waild MCP never automatically retries a paid call whose outcome is uncertain.

Reports live in the conversation unless you ask your agent to save evidence to a plan. For large saves, keep evidence summaries compact and split action items into smaller batches if the server reports an input limit. That refusal happens before anything is saved.

{
  "name": "gsc_report",
  "arguments": {
    "site_url": "sc-domain:example.com",
    "start_date": "2026-10-01",
    "end_date": "2026-10-28",
    "dimensions": [],
    "filters": [
      {
        "dimension": "page",
        "operator": "equals",
        "expression": "https://example.com/your-page/"
      }
    ]
  }
}

{
  "name": "gsc_report",
  "arguments": {
    "site_url": "sc-domain:example.com",
    "start_date": "2026-10-01",
    "end_date": "2026-10-28",
    "compare_to": {
      "start_date": "2026-09-03",
      "end_date": "2026-09-30"
    },
    "filters": [
      {
        "dimension": "page",
        "operator": "equals",
        "expression": "https://example.com/your-page/"
      }
    ]
  }
}

4. Audit what it saved

Saved data lists your websites, marketing plans and the evidence behind each item — the audit trail for what your agent recorded. Usage shows included credit, temporary holds and paid-provider activity, including BYOK requests. Some outcomes or costs may remain unconfirmed; internal functions and free analytics reads are not listed. This view stays readable even when service access is off.

The other docs describe the broader product, including recorded owner-side capabilities that are not in this beta. Something blocked or unclear? Contact the beta owner.