@cesteral/dbm-mcp

@cesteral/dbm-mcp

DBM MCP Server - Generic cross-platform reporting and metrics server.

Purpose

Read-only reporting server that provides delivery metrics, performance calculations, time-series data, and pacing status. Platform-agnostic design supports DV360, Google Ads, Meta, The Trade Desk, and Amazon DSP.

Features

• Per-session Google auth via GoogleAuthAdapter with X-DV360-* request headers
• Streamable HTTP + stdio transports via Hono + @hono/mcp
• OpenTelemetry instrumentation for traces and metrics
• Rate limiting via shared RateLimiter class
• Structured logging via Pino
• Read-only reporting -- no write operations, no entity mutation

MCP Tools

1. dbm_get_campaign_delivery

Fetch delivery metrics (impressions, clicks, spend, conversions) for a campaign within a date range.

Parameters:

• campaignId (string): Campaign ID
• advertiserId (string): DV360 Advertiser ID
• startDate (string): Start date (YYYY-MM-DD)
• endDate (string): End date (YYYY-MM-DD)

2. dbm_get_performance_metrics

Calculate performance KPIs (CPM, CTR, CPA, ROAS) from delivery data.

Parameters:

• campaignId (string): Campaign ID
• startDate (string): Start date (YYYY-MM-DD)
• endDate (string): End date (YYYY-MM-DD)

3. dbm_get_historical_metrics

Fetch time-series historical metrics for trend analysis.

Parameters:

• campaignId (string): Campaign ID
• startDate (string): Start date (YYYY-MM-DD)
• endDate (string): End date (YYYY-MM-DD)
• granularity (string, optional): "daily" or "hourly" (default: "daily")

4. dbm_get_pacing_status

Get real-time pacing status for a campaign (actual vs expected delivery).

Parameters:

• campaignId (string): Campaign ID

5. dbm_run_custom_query

Compose and execute a custom Bid Manager report with specified metrics, dimensions, and filters.

Parameters:

• reportType (string): Report type
• timeRange (object): Time range for the report
• metrics (string[]): Metrics to include
• dimensions (string[]): Dimensions for grouping
• filters (object[], optional): Filter conditions
• advertiserId (string): DV360 Advertiser ID
• mode, columns, offset, maxRows (optional): Bounded report-view params — mode is "summary" (default — headers + counts + 10-row preview) or "rows" (paginated rows page); columns projects to selected columns; offset paginates; maxRows caps page size (default 10/50; hard cap 200).

6. dbm_run_custom_query_async

Submit a custom Bid Manager report without waiting for completion (non-blocking). Uses MCP Tasks to return a task handle immediately; clients poll via tasks/getTask and retrieve results via tasks/getTaskResult.

Parameters: Same as dbm_run_custom_query (including the bounded report-view params).

Authentication Modes

Mode	Header	Description
google-headers (default)	X-DV360-*	Google OAuth2 credentials via request headers
jwt	Authorization: Bearer <JWT>	JWT token authentication for hosted deployments
none	—	No authentication (development only)

Set via MCP_AUTH_MODE environment variable.

Context Efficiency Notes

• Tools with outputSchema provide full typed payloads in structuredContent; text output is intentionally summary-focused.
• Use scoped resources when possible to reduce context size:
  • metric-types://category/{slug}
  • filter-types://category/{slug}
• Full catalogs remain available at metric-types://all and filter-types://all.

Architecture

Key Components

• BidManagerService - Core service for Bid Manager API v2: query creation, execution, polling, and CSV report parsing
• BidManagerClient - googleapis-based client for the Bid Manager API v2
• auth-bridge.ts - Adapts shared GoogleAuthAdapter to the googleapis OAuth2Client shape
• SessionServiceStore - Per-session service instances keyed by session ID
• report-parser.ts - CSV-to-JSON parser for Bid Manager report results

Transport

• Streamable HTTP: MCP protocol via Streamable HTTP transport at /mcp
• Health check: /health endpoint

Key Gotchas

• Reports are async: create query → run query → poll status → fetch results
• Report results are CSV-formatted; the server parses them into structured JSON
• advertiserId is required for all reporting tools
• Rate limits apply per Google Cloud project, not per advertiser
• Read-only server — no entity mutation; use dv360-mcp for write operations

Data Sources

• Bid Manager API v2: DV360 reporting queries

Current Status

Phase: Production-Ready

The reporting and query tools are fully implemented using Bid Manager API v2 for DV360 reporting. Entity retrieval is handled by the separate @cesteral/dv360-mcp server.

Development

# Install dependencies
pnpm install

# Run in development mode
pnpm run dev:http

# Build
pnpm run build

# Start production server
pnpm run start

# Type check
pnpm run typecheck

# Lint
pnpm run lint

Environment Variables

See root .env.example for all required variables:

• DBM_MCP_PORT: Server port (default: 3001)
• DBM_MCP_HOST: Server host (default: 0.0.0.0)
• GCP_PROJECT_ID: Google Cloud project ID
• BIGQUERY_DATASET_ID: BigQuery dataset name

Testing with MCP Inspector

# Start the server
pnpm run dev:http

# In another terminal, use MCP Inspector
npx @modelcontextprotocol/inspector http://localhost:3001/mcp

API Endpoints

• GET /health - Health check
• POST /mcp - MCP protocol via Streamable HTTP transport

Contributing

See root CLAUDE.md for development guidelines, build system details, and monorepo conventions. See the root README for full architecture context.

Get Started

Self-host: Follow the deployment guide to run this server on your own infrastructure.

Cesteral Intelligence: Request access -- governed execution with credential brokering, approvals, audit, and multi-tenant access.

Book a workflow demo: See it in action with your own ad accounts.

Compare options: OSS connectors vs Cesteral Intelligence

License

Apache License 2.0 — see LICENSE for details. This package is part of Cesteral's open-source connector layer; managed hosting and higher-level governance features live outside this repository.