The Adspìrer MCP server is part of the Ads MCP ecosystem. It exposes a Model Context Protocol (MCP) server endpoint that allows clients to query and manage advertising-related contexts, assets, and integrations through the MCP framework. This server supports basic lifecycle and context operations that enable tooling and chat-based assistants to fetch ads-related context, validate assets, and coordinate with OAuth-enabled flows when integrated with Ads MCP tooling. To begin, run the server and connect a client that supports MCP to the server endpoint to retrieve or mutate context data as defined by the Ads MCP schema and your integration needs. Note that this repository is historical and the actively maintained version is now Ads MCP; many usage patterns and endpoints are documented there, but you can use this as a reference for legacy compatibility or local experimentation.

Prerequisites:

• Node.js (LTS version) and npm installed on your system
• A compatible MCP client or tooling to interact with the MCP server

Step 1: Install dependencies (if any)

• If this repository ships with a package.json, run:

  npm install

Step 2: Start the MCP server

• Run the server using Node.js (as configured in mcp_config):

  npm run start

  or, if there is no start script, use:

  node server.js

Step 3: Verify the server is running

• Open a browser or HTTP client and hit the configured endpoint (default port 3000 if not overridden):

  http://localhost:3000/

Step 4: Connect a client

• Use an MCP client or your own integration to connect to the MCP server endpoint and perform basic MCP operations (get, upsert, delete contexts) according to the MCP protocol and Ads MCP tooling documentation.

Notes and tips:

• This repository is historical; the actively maintained Ads MCP project should be used for production deployments. The modern Ads MCP provides broader features such as Google Ads, TikTok Ads integration, OAuth 2.1, real-time progress streaming, asset management, and AI integrations.
• If you run into port conflicts, override the PORT environment variable in your environment or in a .env file if supported by your startup script.
• Ensure your network permissions allow inbound connections to the MCP server port and that any required OAuth redirection URIs are configured in your provider.
• When upgrading to Ads MCP, review the new tooling and API surface as there are feature differences and improved security patterns.
• If you need to restore legacy behavior, keep a local copy of this server and align its MCP contexts to match the current registry or migration path.