Provides access to Uber's External Ads API for comprehensive advertising campaign management, including creating, retrieving, updating, and deleting campaigns with support for budget management, scheduling, and campaign objectives.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Uber External Ads API MCP Server show me the active campaigns for ad account d924b89c-09f9-477b-a3ae-5526aa533835"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP (Model Context Protocol) server that provides access to Uber's External Ads API for campaign management.
Get Campaigns: Retrieve campaigns for an ad account with optional filtering
Get Campaign: Get details for a specific campaign
Create Campaign: Create new advertising campaigns
Update Campaign: Modify existing campaigns
Delete Campaign: Remove campaigns
Related MCP server: Google Ads MCP Server
npm install
npm run buildnpm run devnpm startRetrieve campaigns for an ad account.
Parameters:
auth_token (required): Bearer token for authentication
ad_account_id (required): The ad account UUID
filters (optional): Object with filtering options
status: Filter by campaign status (ACTIVE, PAUSED, DELETED)
limit: Number of campaigns to return (1-100, default: 20)
offset: Number of campaigns to skip (default: 0)
Get details for a specific campaign.
Parameters:
auth_token (required): Bearer token for authentication
ad_account_id (required): The ad account UUID
campaign_id (required): The campaign UUID
Create a new campaign.
Parameters:
auth_token (required): Bearer token for authentication
ad_account_id (required): The ad account UUID
campaign_data (required): Campaign configuration object
name (required): Campaign name
budget_amount (required): Budget amount in USD
status: Campaign status (ACTIVE, PAUSED) - default: ACTIVE
budget_type: Budget type (DAILY, LIFETIME) - default: DAILY
start_time: Campaign start time (ISO 8601)
end_time: Campaign end time (ISO 8601)
objective: Campaign objective (AWARENESS, CONSIDERATION, CONVERSION) - default: CONVERSION
Update an existing campaign.
Parameters:
auth_token (required): Bearer token for authentication
ad_account_id (required): The ad account UUID
campaign_id (required): The campaign UUID
campaign_data (required): Updates to apply
name: Campaign name
status: Campaign status (ACTIVE, PAUSED)
budget_amount: Budget amount in USD
end_time: Campaign end time (ISO 8601)
Delete a campaign.
Parameters:
auth_token (required): Bearer token for authentication
ad_account_id (required): The ad account UUID
campaign_id (required): The campaign UUID
Using the provided curl request as an example:
// Get campaigns
await callTool('get_campaigns', {
auth_token: 'IA.AQAAAATlHYAkrhJsBvg2h_K7dmXYDF_9LQAe8gEiCkd7Wyd79AB36AmskjmnMMPtDOwrWBgnGuHNb0Esrh2dScncw8weNgx5kjMNtxP88XJSdDzjfdOmcWe3Zvc0rHx-p5ldHqmXvDvUnjndiPqXigz_yg332ek6b_dmR-1KRus',
ad_account_id: 'd924b89c-09f9-477b-a3ae-5526aa533835',
filters: {
status: 'ACTIVE',
limit: 10
}
});The server uses the Uber External Ads API base URL: https://api.uber.com/v1/ads
All requests require a valid Bearer token for authentication.
The server provides detailed error messages for:
Authentication failures
Invalid parameters
API errors
Network issues
Errors are returned with isError: true and descriptive messages.
All authentication tokens are validated
Input parameters are validated using Zod schemas
API responses are properly formatted and sanitized
Create a new campaign
Inputs: ad_account_id (required), campaign_data (required), auth_token.
Delete a campaign
Inputs: ad_account_id (required), campaign_id (required), auth_token.
Get details for a specific campaign
Inputs: ad_account_id (required), campaign_id (required), auth_token.
Get campaigns for an ad account
Inputs: ad_account_id (required), auth_token, filters.
Update an existing campaign
Inputs: ad_account_id (required), campaign_data (required), campaign_id (required), auth_token.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose: create, delete, get (single), get (multiple), and update campaigns. There is no overlap or ambiguity in functionality, making it easy for an agent to select the correct tool for any campaign-related operation.
All tool names follow a consistent verb_noun pattern (e.g., create_campaign, delete_campaign, get_campaign, get_campaigns, update_campaign). The naming is uniform and predictable, using snake_case throughout without any deviations or mixed conventions.
With 5 tools, this server is well-scoped for managing campaigns in an ads API context. Each tool serves a specific and necessary function (CRUD operations plus listing), and there are no extraneous or missing tools for this focused domain.
The tool set provides complete CRUD coverage for campaigns: create, read (both single and multiple), update, and delete. There are no obvious gaps, as all essential lifecycle operations are covered, ensuring agents can handle campaign management without dead ends.
Build, edit and sync Google, Microsoft, Reddit and Meta ad campaigns from your assistant.
Open-source ad agent for LinkedIn Ads and Google Ads. Drafts campaigns, audiences and reports.
Manage Apple Ads campaigns and reporting in chat.
Conversational access to advertising performance data, creative analysis, and campaign insights
