ZITS Digital · Zee Medical Billing
Ask Claude or Grok about your ads and search data.
ZMCP Connector is a remote MCP server you host yourself. Connect Search Console, GA4, Meta, and Google Ads once, then question the accounts from Claude or a Grok bot.
A question you can ask
“Which queries sent clicks to the billing site last month, and which Meta campaigns spent more than they converted?”
The connector answers from the accounts your organization connected. Tokens stay encrypted on your server. Google tools are read-only. Meta changes require a preview and a one-time confirmation.
How a team uses it
1. Create the organization
Email and password, or Google. The first matching bootstrap email becomes the platform owner.
2. Connect accounts
Search Console, GA4, and Meta each use their own OAuth grant. Meta also accepts a system user token.
3. Add the connector
Paste the MCP URL into Claude or a Grok bot. Sign in with OAuth, or use an API key.
4. Ask with the data
Tool calls are counted, isolated per organization, and written to the audit log.
Sources
- Google Search Console. Sites, search analytics, URL inspection, sitemaps.
- GA4. Account summaries, reports, realtime, metadata.
- Meta ads. Accounts, campaigns, ad sets, ads, insights, audiences, Page and Instagram insights.
- Google Ads. Read-only GAQL. Hidden until a developer token is configured on the server.
What stays put
- Provider tokens are encrypted with AES-256-GCM. API keys and OAuth tokens are stored as hashes.
- Passwords use argon2id. Sessions are httpOnly cookies with CSRF checks on forms.
- Every tool call is audited with the tool name, organization, duration, and status. Secret values are not written to the log.
- Write tools exist only for Meta, default off, and never delete a campaign or ad set.