meta-ads-mcp 1.0.11__tar.gz → 1.0.17__tar.gz

meta_ads_mcp-1.0.17/.github/workflows/publish-mcp.yml

@@ -0,0 +1,32 @@
+name: Publish to MCP Registry (manual)
+
+on:
+  # This workflow is kept for manual runs only. The normal release flow
+  # is handled by the consolidated release workflow.
+  workflow_dispatch:
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Install MCP Publisher
+        run: |
+          curl -L "https://github.com/modelcontextprotocol/registry/releases/download/v1.1.0/mcp-publisher_1.1.0_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
+
+      - name: Login to MCP Registry (DNS auth)
+        run: |
+          echo "${{ secrets.MCP_PRIVATE_KEY }}" > temp_key.pem
+          PRIVATE_KEY_HEX=$(openssl pkey -in temp_key.pem -noout -text | grep -A3 "priv:" | tail -n +2 | tr -d ' :\n')
+          ./mcp-publisher login dns --domain pipeboard.co --private-key "$PRIVATE_KEY_HEX"
+          rm -f temp_key.pem
+
+      - name: Publish to MCP Registry
+        run: ./mcp-publisher publish
+

meta_ads_mcp-1.0.17/.github/workflows/publish.yml

@@ -0,0 +1,114 @@
+name: "Release: Test, PyPI, MCP"
+
+on:
+  release:
+    types: [published]
+  # Allow manual triggering for testing
+  workflow_dispatch:
+
+jobs:
+  test_and_build:
+    name: Test and Build (pre-release gate)
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    steps:
+    - name: Check out code
+      uses: actions/checkout@v4
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v5
+
+    - name: Install dependencies
+      run: |
+        uv sync --all-extras --dev
+
+    - name: Run tests
+      run: |
+        uv run pytest -q
+
+    - name: Build wheel and sdist
+      run: |
+        uv build
+
+    - name: Validate server.json against schema
+      run: |
+        uv run python - <<'PY'
+        import json, sys, urllib.request
+        from jsonschema import validate
+        from jsonschema.exceptions import ValidationError
+        server = json.load(open('server.json'))
+        schema_url = server.get('$schema')
+        with urllib.request.urlopen(schema_url) as r:
+            schema = json.load(r)
+        try:
+            validate(instance=server, schema=schema)
+        except ValidationError as e:
+            print('Schema validation failed:', e, file=sys.stderr)
+            sys.exit(1)
+        print('server.json is valid')
+        PY
+
+  publish_pypi:
+    name: Publish to PyPI
+    needs: test_and_build
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      id-token: write  # IMPORTANT: this permission is mandatory for trusted publishing
+      contents: read
+
+    steps:
+    - name: Check out code
+      uses: actions/checkout@v4
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.10"
+
+    - name: Install build dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install build
+
+    - name: Build package
+      run: python -m build
+
+    - name: Publish to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+      with:
+        verbose: true
+
+  publish_mcp:
+    name: Publish to MCP Registry
+    needs: publish_pypi
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+
+    steps:
+    - name: Check out code
+      uses: actions/checkout@v4
+
+    - name: Install MCP Publisher
+      run: |
+        curl -L "https://github.com/modelcontextprotocol/registry/releases/download/v1.1.0/mcp-publisher_1.1.0_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
+
+    - name: Login to MCP Registry (DNS auth)
+      run: |
+        # Extract private key using official MCP publisher method
+        echo "${{ secrets.MCP_PRIVATE_KEY }}" > temp_key.pem
+        PRIVATE_KEY_HEX=$(openssl pkey -in temp_key.pem -noout -text | grep -A3 "priv:" | tail -n +2 | tr -d ' :\n')
+        ./mcp-publisher login dns --domain pipeboard.co --private-key "$PRIVATE_KEY_HEX"
+        rm -f temp_key.pem
+
+    - name: Publish to MCP Registry
+      run: ./mcp-publisher publish

{meta_ads_mcp-1.0.11 → meta_ads_mcp-1.0.17}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: meta-ads-mcp
-Version: 1.0.11
-Summary: Model Context Protocol (MCP) server for interacting with Meta Ads API
+Version: 1.0.17
+Summary: Model Context Protocol (MCP) server for Meta Ads - Use Remote MCP at pipeboard.co for easiest setup
 Project-URL: Homepage, https://github.com/pipeboard-co/meta-ads-mcp
 Project-URL: Bug Tracker, https://github.com/pipeboard-co/meta-ads-mcp/issues
 Author-email: Yves Junqueira <yves.junqueira@gmail.com>
@@ -25,13 +25,15 @@ Description-Content-Type: text/markdown
 
 # Meta Ads MCP
 
-A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for interacting with Meta Ads API. This tool enables AI models to access, analyze, and manage Meta advertising campaigns through a standardized interface, allowing LLMs to retrieve performance data, visualize ad creatives, and provide strategic insights for Facebook, Instagram, and other Meta platforms.
+A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for interacting with Meta Ads. Analyze, manage and optimize Meta advertising campaigns through an AI interface. Use an LLM to retrieve performance data, visualize ad creatives, and provide strategic insights for your ads on Facebook, Instagram, and other Meta platforms.
 
 > **DISCLAIMER:** This is an unofficial third-party tool and is not associated with, endorsed by, or affiliated with Meta in any way. This project is maintained independently and uses Meta's public APIs according to their terms of service. Meta, Facebook, Instagram, and other Meta brand names are trademarks of their respective owners.
 
 [![Meta Ads MCP Server Demo](https://github.com/user-attachments/assets/3e605cee-d289-414b-814c-6299e7f3383e)](https://github.com/user-attachments/assets/3e605cee-d289-414b-814c-6299e7f3383e)
 
-<!-- mcp-name: io.github.pipeboard-co/meta-ads-mcp -->
+[![MCP Badge](https://lobehub.com/badge/mcp/nictuku-meta-ads-mcp)](https://lobehub.com/mcp/nictuku-meta-ads-mcp)
+
+mcp-name: co.pipeboard/meta-ads-mcp
 
 ## Community & Support
 
@@ -66,6 +68,16 @@ The fastest and most reliable way to get started is to **[🚀 Get started with
 
 That's it! You can now ask Claude to analyze your Meta ad campaigns, get performance insights, and manage your advertising.
 
+#### Advanced: Direct Token Authentication (Claude)
+
+For direct token-based authentication without the interactive flow, use this URL format when adding the integration:
+
+```
+https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
+```
+
+Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
+
 ### For Cursor Users
 
 Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP, click on "Needs login" to finish the login process.
@@ -81,31 +93,45 @@ Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP,
 }
 ```
 
+#### Advanced: Direct Token Authentication (Cursor)
+
+If you prefer to authenticate without the interactive login flow, you can include your Pipeboard API token directly in the URL:
+
+```json
+{
+  "mcpServers": {
+    "meta-ads-remote": {
+      "url": "https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN"
+    }
+  }
+}
+```
+
+Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
+
 ### For Other MCP Clients
 
 Use the Remote MCP URL: `https://mcp.pipeboard.co/meta-ads-mcp`
 
 **[📖 Get detailed setup instructions for your AI client here](https://pipeboard.co)**
 
-## Local Installation (Technical Users Only)
+#### Advanced: Direct Token Authentication (Other Clients)
 
-If you're a developer or need to customize the installation, you can run Meta Ads MCP locally. **Most marketers should use the Remote MCP above instead!** For complete technical setup instructions, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)**.
+For MCP clients that support token-based authentication, you can append your Pipeboard API token to the URL:
 
-Meta Ads MCP also supports **streamable HTTP transport**, allowing you to run it as a standalone HTTP API for web applications and custom integrations. See **[Streamable HTTP Setup Guide](STREAMABLE_HTTP_SETUP.md)** for complete instructions.
+```
+https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
+```
 
-### Quick Local Setup
+This bypasses the interactive login flow and authenticates immediately. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
 
-```bash
-# Install via uvx (recommended)
-uvx meta-ads-mcp
+## Local Installation (Advanced Technical Users Only)
 
-# Set your Pipeboard token
-export PIPEBOARD_API_TOKEN=your_pipeboard_token
+🚀 **We strongly recommend using [Remote MCP](https://pipeboard.co) instead** - it's faster, more reliable, and requires no technical setup.
 
-# Add to your MCP client configuration
-```
+For developers who need to self-host, the package is available via pip. Local installations require creating your own Meta Developer App and implementing the complete OAuth flow. See the source repository for technical details.
 
-For detailed step-by-step instructions, authentication setup, debugging, and troubleshooting, visit **[LOCAL_INSTALLATION.md](LOCAL_INSTALLATION.md)**.
+Meta Ads MCP also supports **streamable HTTP transport**, allowing you to run it as a standalone HTTP API for web applications and custom integrations. See **[Streamable HTTP Setup Guide](STREAMABLE_HTTP_SETUP.md)** for complete instructions.
 
 ## Features
 
@@ -128,9 +154,9 @@ For detailed step-by-step instructions, authentication setup, debugging, and tro
 
 **[✨ Get started with Remote MCP here](https://pipeboard.co)** - no technical setup required! Just connect your Facebook Ads account and start asking AI to analyze your campaigns.
 
-### Local Installation (Technical Users)
+### Local Installation (Advanced Technical Users)
 
-For local installation configuration, authentication options, and advanced technical setup, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)**.
+For advanced users who need to self-host, the package can be installed from source. Local installations require creating your own Meta Developer App. **We recommend using [Remote MCP](https://pipeboard.co) for a simpler experience.**
 
 ### Available MCP Tools
 
@@ -456,7 +482,7 @@ The only restriction is that you cannot offer this as a competing hosted service
 Meta Ads MCP follows security best practices with secure token management and automatic authentication handling. 
 
 - **Remote MCP**: All authentication is handled securely in the cloud - no local token storage required
-- **Local Installation**: Tokens are cached securely on your local machine - see [Local Installation Guide](LOCAL_INSTALLATION.md) for details
+- **Local Installation**: Tokens are cached securely on your local machine
 
 ## Testing
 
@@ -468,7 +494,7 @@ Test your Meta Ads MCP connection with any MCP client:
 2. **Check Account Details**: Use `mcp_meta_ads_get_account_info` with your account ID
 3. **List Campaigns**: Try `mcp_meta_ads_get_campaigns` to see your ad campaigns
 
-For detailed local installation testing, see [Local Installation Guide](LOCAL_INSTALLATION.md).
+For detailed local installation testing, see the source repository.
 
 ## Troubleshooting
 
@@ -478,10 +504,4 @@ The easiest way to avoid any setup issues is to **[🎯 use our Remote MCP inste
 
 ### Local Installation Issues
 
-For comprehensive troubleshooting, debugging, and local installation issues, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)** which includes:
-
-- Authentication troubleshooting
-- Installation issues and solutions
-- API error resolution
-- Debug logs and diagnostic commands
-- Performance optimization tips
+For local installation issues, refer to the source repository. **For the easiest experience, we recommend using [Remote MCP](https://pipeboard.co) instead.**

{meta_ads_mcp-1.0.11 → meta_ads_mcp-1.0.17}/README.md

@@ -1,12 +1,14 @@
 # Meta Ads MCP
 
-A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for interacting with Meta Ads API. This tool enables AI models to access, analyze, and manage Meta advertising campaigns through a standardized interface, allowing LLMs to retrieve performance data, visualize ad creatives, and provide strategic insights for Facebook, Instagram, and other Meta platforms.
+A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for interacting with Meta Ads. Analyze, manage and optimize Meta advertising campaigns through an AI interface. Use an LLM to retrieve performance data, visualize ad creatives, and provide strategic insights for your ads on Facebook, Instagram, and other Meta platforms.
 
 > **DISCLAIMER:** This is an unofficial third-party tool and is not associated with, endorsed by, or affiliated with Meta in any way. This project is maintained independently and uses Meta's public APIs according to their terms of service. Meta, Facebook, Instagram, and other Meta brand names are trademarks of their respective owners.
 
 [![Meta Ads MCP Server Demo](https://github.com/user-attachments/assets/3e605cee-d289-414b-814c-6299e7f3383e)](https://github.com/user-attachments/assets/3e605cee-d289-414b-814c-6299e7f3383e)
 
-<!-- mcp-name: io.github.pipeboard-co/meta-ads-mcp -->
+[![MCP Badge](https://lobehub.com/badge/mcp/nictuku-meta-ads-mcp)](https://lobehub.com/mcp/nictuku-meta-ads-mcp)
+
+mcp-name: co.pipeboard/meta-ads-mcp
 
 ## Community & Support
 
@@ -41,6 +43,16 @@ The fastest and most reliable way to get started is to **[🚀 Get started with
 
 That's it! You can now ask Claude to analyze your Meta ad campaigns, get performance insights, and manage your advertising.
 
+#### Advanced: Direct Token Authentication (Claude)
+
+For direct token-based authentication without the interactive flow, use this URL format when adding the integration:
+
+```
+https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
+```
+
+Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
+
 ### For Cursor Users
 
 Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP, click on "Needs login" to finish the login process.
@@ -56,31 +68,45 @@ Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP,
 }
 ```
 
+#### Advanced: Direct Token Authentication (Cursor)
+
+If you prefer to authenticate without the interactive login flow, you can include your Pipeboard API token directly in the URL:
+
+```json
+{
+  "mcpServers": {
+    "meta-ads-remote": {
+      "url": "https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN"
+    }
+  }
+}
+```
+
+Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
+
 ### For Other MCP Clients
 
 Use the Remote MCP URL: `https://mcp.pipeboard.co/meta-ads-mcp`
 
 **[📖 Get detailed setup instructions for your AI client here](https://pipeboard.co)**
 
-## Local Installation (Technical Users Only)
+#### Advanced: Direct Token Authentication (Other Clients)
 
-If you're a developer or need to customize the installation, you can run Meta Ads MCP locally. **Most marketers should use the Remote MCP above instead!** For complete technical setup instructions, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)**.
+For MCP clients that support token-based authentication, you can append your Pipeboard API token to the URL:
 
-Meta Ads MCP also supports **streamable HTTP transport**, allowing you to run it as a standalone HTTP API for web applications and custom integrations. See **[Streamable HTTP Setup Guide](STREAMABLE_HTTP_SETUP.md)** for complete instructions.
+```
+https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
+```
 
-### Quick Local Setup
+This bypasses the interactive login flow and authenticates immediately. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
 
-```bash
-# Install via uvx (recommended)
-uvx meta-ads-mcp
+## Local Installation (Advanced Technical Users Only)
 
-# Set your Pipeboard token
-export PIPEBOARD_API_TOKEN=your_pipeboard_token
+🚀 **We strongly recommend using [Remote MCP](https://pipeboard.co) instead** - it's faster, more reliable, and requires no technical setup.
 
-# Add to your MCP client configuration
-```
+For developers who need to self-host, the package is available via pip. Local installations require creating your own Meta Developer App and implementing the complete OAuth flow. See the source repository for technical details.
 
-For detailed step-by-step instructions, authentication setup, debugging, and troubleshooting, visit **[LOCAL_INSTALLATION.md](LOCAL_INSTALLATION.md)**.
+Meta Ads MCP also supports **streamable HTTP transport**, allowing you to run it as a standalone HTTP API for web applications and custom integrations. See **[Streamable HTTP Setup Guide](STREAMABLE_HTTP_SETUP.md)** for complete instructions.
 
 ## Features
 
@@ -103,9 +129,9 @@ For detailed step-by-step instructions, authentication setup, debugging, and tro
 
 **[✨ Get started with Remote MCP here](https://pipeboard.co)** - no technical setup required! Just connect your Facebook Ads account and start asking AI to analyze your campaigns.
 
-### Local Installation (Technical Users)
+### Local Installation (Advanced Technical Users)
 
-For local installation configuration, authentication options, and advanced technical setup, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)**.
+For advanced users who need to self-host, the package can be installed from source. Local installations require creating your own Meta Developer App. **We recommend using [Remote MCP](https://pipeboard.co) for a simpler experience.**
 
 ### Available MCP Tools
 
@@ -431,7 +457,7 @@ The only restriction is that you cannot offer this as a competing hosted service
 Meta Ads MCP follows security best practices with secure token management and automatic authentication handling. 
 
 - **Remote MCP**: All authentication is handled securely in the cloud - no local token storage required
-- **Local Installation**: Tokens are cached securely on your local machine - see [Local Installation Guide](LOCAL_INSTALLATION.md) for details
+- **Local Installation**: Tokens are cached securely on your local machine
 
 ## Testing
 
@@ -443,7 +469,7 @@ Test your Meta Ads MCP connection with any MCP client:
 2. **Check Account Details**: Use `mcp_meta_ads_get_account_info` with your account ID
 3. **List Campaigns**: Try `mcp_meta_ads_get_campaigns` to see your ad campaigns
 
-For detailed local installation testing, see [Local Installation Guide](LOCAL_INSTALLATION.md).
+For detailed local installation testing, see the source repository.
 
 ## Troubleshooting
 
@@ -453,10 +479,4 @@ The easiest way to avoid any setup issues is to **[🎯 use our Remote MCP inste
 
 ### Local Installation Issues
 
-For comprehensive troubleshooting, debugging, and local installation issues, see our **[Local Installation Guide](LOCAL_INSTALLATION.md)** which includes:
-
-- Authentication troubleshooting
-- Installation issues and solutions
-- API error resolution
-- Debug logs and diagnostic commands
-- Performance optimization tips
+For local installation issues, refer to the source repository. **For the easiest experience, we recommend using [Remote MCP](https://pipeboard.co) instead.**

{meta_ads_mcp-1.0.11 → meta_ads_mcp-1.0.17}/STREAMABLE_HTTP_SETUP.md

@@ -83,6 +83,16 @@ curl -H "Authorization: Bearer your_pipeboard_token" \
      -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
 ```
 
+#### Remote MCP: Token in URL
+
+When using the hosted Remote MCP at `https://mcp.pipeboard.co/meta-ads-mcp`, you can alternatively authenticate by including the token as a URL parameter:
+
+```
+https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
+```
+
+This is particularly useful for MCP clients that don't support interactive authentication flows.
+
 ### Alternative Method: Direct Meta Token
 
 If you have a Meta Developer App, you can use a direct access token via the `X-META-ACCESS-TOKEN` header. This is less common.

{meta_ads_mcp-1.0.11 → meta_ads_mcp-1.0.17}/meta_ads_mcp/__init__.py

@@ -6,7 +6,7 @@ This package provides a Meta Ads MCP integration
 
 from meta_ads_mcp.core.server import main
 
-__version__ = "1.0.11"
+__version__ = "1.0.17"
 
 __all__ = [
     'get_ad_accounts',