ads

This MCP server named Ads provides a centralized, strategy-aware interface for planning, creating, analyzing, and optimizing advertising campaigns across Google Ads, Meta Ads, TikTok Ads, and LinkedIn Ads. With over 100 tools and capabilities across platforms, you can perform keyword research with CPC data, generate and validate multi-platform campaigns, manage assets and ad extensions, and receive actionable optimization recommendations. The server persists strategic decisions to a STRATEGY.md file to guide future campaigns and offers structured prompts for campaign planning, cross-platform keyword research, and performance analysis. To use it, connect your MCP-enabled AI assistant to the MCP URL, grant OAuth access, and start issuing prompts such as creating a Google Performance Max campaign, researching high-intent keywords, or evaluating cross-platform performance. The system supports sustaining multi-account management and leverages built-in safety metadata for tool usage.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Access to the MCP server URL and required OAuth credentials

Install steps:

1. Clone or download the repository to your development environment
2. Navigate to the project root
3. Install dependencies
   • npm install
4. Configure environment variables (see mcp_config.env in sample or set them in your environment):
   • MCP_REGISTRY_ID
   • MCP_TRANSPORT
   • OAUTH_CLIENT_ID
   • OAUTH_CLIENT_SECRET
   • OAUTH_REDIRECT_URI
   • OAUTH_AUTHORIZATION_URL
   • OAUTH_TOKEN_URL
   • DATABASE_URL
   • LOG_LEVEL
5. Start the MCP server
   • npm run start (or node server.js if a simple entry point is used)
6. Verify the server is up by visiting the MCP health endpoint or the configured health URL provided in the README

Notes:

• Ensure proper OAuth configuration for the environment where the server runs
• If running behind a reverse proxy, configure TLS termination and pass-through correctly

Environment variables and configuration can often differ between local development and production. Common issues include OAuth redirect URI mismatches, incorrect database connection strings, or firewall rules blocking the transport. For troubleshooting, check logs at the configured LOG_LEVEL, verify that the MCP transport is set to Streamable HTTP, and ensure the registry ID matches the one advertised by your MCP server. If you rely on a cloud-hosted registry, ensure network egress is allowed to the OAuth endpoints and that PKCE challenge handling is correctly implemented. The server is designed to manage multiple ad accounts across platforms and can be extended with plugins per platform as described in the repository documentation.