meta-ads-mcp 0.2.5__tar.gz → 0.2.8__tar.gz

{meta_ads_mcp-0.2.5 → meta_ads_mcp-0.2.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meta-ads-mcp
-Version: 0.2.5
+Version: 0.2.8
 Summary: Model Calling Protocol (MCP) plugin for interacting with Meta Ads API
 Project-URL: Homepage, https://github.com/nictuku/meta-ads-mcp
 Project-URL: Bug Tracker, https://github.com/nictuku/meta-ads-mcp/issues
@@ -15,6 +15,7 @@ Requires-Dist: httpx>=0.26.0
 Requires-Dist: mcp[cli]>=1.6.0
 Requires-Dist: pathlib>=1.0.1
 Requires-Dist: pillow>=10.0.0
+Requires-Dist: python-dateutil>=2.8.2
 Requires-Dist: python-dotenv>=1.1.0
 Requires-Dist: requests>=2.32.3
 Description-Content-Type: text/markdown
@@ -49,6 +50,11 @@ Screenhot: using an LLM to understand your ad performance.
 When using uv no specific installation is needed. We can use uvx to directly run meta-ads-mcp:
 
 ```bash
+# RECOMMENDED: Use with Pipeboard authentication
+export PIPEBOARD_API_TOKEN=your_pipeboard_token  # Get your token at https://pipeboard.co
+uvx meta-ads-mcp
+
+# Alternative: Use with direct Meta authentication
 uvx meta-ads-mcp --app-id YOUR_META_ADS_APP_ID
 ```
 
@@ -76,15 +82,50 @@ pip install meta-ads-mcp
 After installation, you can run it as:
 
 ```bash
+# RECOMMENDED: Use with Pipeboard authentication
+export PIPEBOARD_API_TOKEN=your_pipeboard_token  # Get your token at https://pipeboard.co
 python -m meta_ads_mcp
+
+# Alternative: Use with direct Meta authentication
+python -m meta_ads_mcp --app-id YOUR_META_ADS_APP_ID
 ```
 
 ## Configuration
 
+### Quick Start with Pipeboard Authentication (Recommended)
+
+The easiest way to configure Meta Ads MCP is using Pipeboard authentication:
+
+1. Sign up at [Pipeboard.co](https://pipeboard.co) and generate an API token - **Get your free token at [https://pipeboard.co](https://pipeboard.co)**
+2. Set the environment variable:
+   ```bash
+   export PIPEBOARD_API_TOKEN=your_pipeboard_token   # Token obtainable via https://pipeboard.co
+   ```
+3. Run meta-ads-mcp without needing to set up a Meta Developer App:
+   ```bash
+   uvx meta-ads-mcp
+   ```
+
+This method provides longer-lived tokens (60 days), simplified setup, and automatic token renewal.
+
 ### Usage with Claude in Cursor
 
 Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor:
 
+```json
+"mcpServers": {
+  "meta-ads": {
+    "command": "uvx",
+    "args": ["meta-ads-mcp"],
+    "env": {
+      "PIPEBOARD_API_TOKEN": "your_pipeboard_token"  // Token obtainable via https://pipeboard.co
+    }
+  }
+}
+```
+
+Or if you prefer direct Meta authentication (using your own Facebook app):
+
 ```json
 "mcpServers": {
   "meta-ads": {
@@ -187,7 +228,28 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `ad_id`: Meta Ads ad ID
     - Returns: The ad image ready for direct visual analysis
 
-12. `mcp_meta_ads_get_insights`
+12. `mcp_meta_ads_update_ad`
+    - Update an ad with new settings
+    - Inputs:
+      - `ad_id`: Meta Ads ad ID
+      - `status`: Update ad status (ACTIVE, PAUSED, etc.)
+      - `bid_amount`: Bid amount in account currency (in cents for USD)
+      - `access_token` (optional): Meta API access token (will use cached token if not provided)
+    - Returns: Confirmation with updated ad details and a confirmation link
+
+13. `mcp_meta_ads_update_adset`
+    - Update an ad set with new settings including frequency caps
+    - Inputs:
+      - `adset_id`: Meta Ads ad set ID
+      - `frequency_control_specs`: List of frequency control specifications
+      - `bid_strategy`: Bid strategy (e.g., 'LOWEST_COST_WITH_BID_CAP')
+      - `bid_amount`: Bid amount in account currency (in cents for USD)
+      - `status`: Update ad set status (ACTIVE, PAUSED, etc.)
+      - `targeting`: Targeting specifications including targeting_automation
+      - `access_token` (optional): Meta API access token (will use cached token if not provided)
+    - Returns: Confirmation with updated ad set details and a confirmation link
+
+14. `mcp_meta_ads_get_insights`
     - Get performance insights for a campaign, ad set, ad or account
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -197,7 +259,7 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `level`: Level of aggregation (ad, adset, campaign, account)
     - Returns: Performance metrics for the specified object
 
-13. `mcp_meta_ads_debug_image_download`
+15. `mcp_meta_ads_debug_image_download`
     - Debug image download issues and report detailed diagnostics
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -205,8 +267,9 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `ad_id`: Meta Ads ad ID (optional, used if url is not provided)
     - Returns: Diagnostic information about image download attempts
 
-14. `mcp_meta_ads_get_login_link`
+16. `mcp_meta_ads_get_login_link`
     - Get a clickable login link for Meta Ads authentication
+    - NOTE: This method should only be used if you're using your own Facebook app. If using Pipeboard authentication (recommended), set the PIPEBOARD_API_TOKEN environment variable instead (token obtainable via https://pipeboard.co).
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
     - Returns: A clickable resource link for Meta authentication
@@ -223,13 +286,47 @@ Before using the MCP server, you'll need to set up a Meta Developer App:
 
 ## Authentication
 
-The Meta Ads MCP uses the OAuth 2.0 flow designed for desktop apps. When authenticating, it will:
+The Meta Ads MCP supports two authentication methods:
+
+### 1. Pipeboard Authentication (Recommended ⭐)
+
+This method uses [Pipeboard.co](https://pipeboard.co) to manage Meta API authentication, providing longer-lived tokens and a simplified flow:
+
+1. **Get your Pipeboard token**: Sign up at [https://pipeboard.co](https://pipeboard.co) to generate your free API token
+2. Set the `PIPEBOARD_API_TOKEN` environment variable with your token: 
+   ```bash
+   export PIPEBOARD_API_TOKEN=your_pipeboard_token
+   ```
+3. Run the Meta Ads MCP normally - it will automatically detect and use Pipeboard authentication:
+   ```bash
+   uvx meta-ads-mcp
+   ```
+4. The first time you run a command, you'll be provided with a login URL to authorize with Meta
+
+**Benefits of Pipeboard authentication:**
+- ✅ Longer-lived tokens (60 days)
+- ✅ No need to configure a Meta Developer App
+- ✅ Simpler setup with just an API token
+- ✅ Automatic token renewal
+
+To test the Pipeboard authentication flow:
+```bash
+python test_pipeboard_auth.py --api-token YOUR_PIPEBOARD_TOKEN
+```
+
+### 2. Direct Meta OAuth (Legacy)
+
+The traditional OAuth 2.0 flow designed for desktop apps. This method should only be used if you are using your own Facebook app instead of Pipeboard.
+
+When authenticating, it will:
 
 1. Start a local callback server on your machine
 2. Open a browser window to authenticate with Meta
 3. Ask you to authorize the app
 4. Redirect back to the local server to extract and store the token securely
 
+This method requires you to [create a Meta Developer App](#create-a-meta-developer-app) first.
+
 ## Troubleshooting and Logging
 
 The Meta Ads MCP includes a comprehensive logging system to help troubleshoot issues:
@@ -244,21 +341,29 @@ Log files are stored in a platform-specific location:
 
 ### Common Issues
 
-#### App ID Issues
+#### Authentication Issues
+
+If you're having authentication problems:
 
-If you encounter errors like `(#200) Provide valid app ID`, check the following:
+1. **Recommended: Use Pipeboard Authentication**
+   - Set `export PIPEBOARD_API_TOKEN=your_token` and retry
+   - This provides longer-lived tokens and better reliability
+   - Verify your token in the Pipeboard dashboard
 
-1. Ensure you've set up a Meta Developer App correctly
-2. Verify that you're passing the correct App ID using one of these methods:
-   - Set the `META_APP_ID` environment variable: `export META_APP_ID=your_app_id`
-   - Pass it as a command-line argument: `meta-ads-mcp --app-id your_app_id`
+2. For App ID issues (when using direct authentication):
+   If you encounter errors like `(#200) Provide valid app ID`, check the following:
+   - Ensure you've set up a Meta Developer App correctly
+   - Verify that you're passing the correct App ID using one of these methods:
+     - Set the `META_APP_ID` environment variable: `export META_APP_ID=your_app_id`
+     - Pass it as a command-line argument: `meta-ads-mcp --app-id your_app_id`
 
-#### Authentication Errors
+#### API Errors
+
+If you receive errors from the Meta API:
 
-Authentication errors can be tracked in the log file. Check for:
-- Token expiration issues
-- App permission problems
-- Connection errors
+1. Verify your app has the Marketing API product added
+2. Ensure the user has appropriate permissions on the ad accounts
+3. Check if there are rate limits or other restrictions on your app
 
 ### Debugging Command
 
@@ -289,14 +394,15 @@ uvx meta-ads-mcp --app-id=your_app_id
 The Meta Ads MCP follows security best practices:
 
 1. Tokens are cached in a platform-specific secure location:
-   - Windows: `%APPDATA%\meta-ads-mcp\token_cache.json`
-   - macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json`
-   - Linux: `~/.config/meta-ads-mcp/token_cache.json`
+   - Windows: `%APPDATA%\meta-ads-mcp\token_cache.json` or `%APPDATA%\meta-ads-mcp\pipeboard_token_cache.json`
+   - macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json` or `~/Library/Application Support/meta-ads-mcp/pipeboard_token_cache.json`
+   - Linux: `~/.config/meta-ads-mcp/token_cache.json` or `~/.config/meta-ads-mcp/pipeboard_token_cache.json`
 
 2. You do not need to provide your access token for each command; it will be automatically retrieved from the cache.
 
 3. You can set the following environment variables instead of passing them as arguments:
-   - `META_APP_ID`: Your Meta App ID (Client ID)
+   - `META_APP_ID`: Your Meta App ID (Client ID) - for direct OAuth method
+   - `PIPEBOARD_API_TOKEN`: Your Pipeboard API token - for Pipeboard authentication method
 
 ## Testing
 
@@ -318,11 +424,12 @@ python test_meta_ads_auth.py --app-id YOUR_APP_ID --force-login
 
 When using the Meta Ads MCP with an LLM interface (like Claude):
 
-1. Test authentication by calling the `mcp_meta_ads_get_login_link` tool
-2. Verify account access by calling `mcp_meta_ads_get_ad_accounts`
-3. Check specific account details with `mcp_meta_ads_get_account_info`
+1. If using direct Meta authentication (your own Facebook app), test authentication by calling the `mcp_meta_ads_get_login_link` tool
+2. If using Pipeboard authentication (recommended), ensure the PIPEBOARD_API_TOKEN environment variable is set (token obtainable via https://pipeboard.co)
+3. Verify account access by calling `mcp_meta_ads_get_ad_accounts`
+4. Check specific account details with `mcp_meta_ads_get_account_info`
 
-These functions will automatically handle authentication if needed and provide a clickable login link.
+These functions will automatically handle authentication if needed and provide a clickable login link if required.
 
 ## Troubleshooting
 
@@ -331,20 +438,20 @@ These functions will automatically handle authentication if needed and provide a
 If you encounter authentication issues:
 
 1. When using the LLM interface:
-   - Use the `mcp_meta_ads_get_login_link` tool to generate a fresh authentication link
+   - If using direct Meta authentication (your own Facebook app), use the `mcp_meta_ads_get_login_link` tool to generate a fresh authentication link
+   - If using Pipeboard authentication (recommended), ensure the PIPEBOARD_API_TOKEN environment variable is set (token obtainable via https://pipeboard.co)
    - Ensure you click the link and complete the authorization flow in your browser
    - Check that the callback server is running properly (the tool will report this)
 
-2. When using the command line:
+2. When using Pipeboard authentication:
+   - Verify your `PIPEBOARD_API_TOKEN` is set correctly (token obtainable via https://pipeboard.co)
+   - Check if you need to complete the authorization process by visiting the provided login URL
+   - Try forcing a new login: `python test_pipeboard_auth.py --force-login`
+
+3. When using direct Meta OAuth:
    - Run with `--force-login` to get a fresh token: `uvx meta-ads-mcp --login --app-id YOUR_APP_ID --force-login`
    - Make sure the terminal has permissions to open a browser window
 
-3. General authentication troubleshooting:
-   - Check that your app is properly configured in the Meta Developers portal
-   - Ensure your app has the necessary permissions (ads_management, ads_read, business_management)
-   - Verify the app's redirect URI includes `http://localhost:8888/callback`
-   - Try clearing the token cache (located in platform-specific directories listed in the Token Caching section)
-
 ### API Errors
 
 If you receive errors from the Meta API:

{meta_ads_mcp-0.2.5 → meta_ads_mcp-0.2.8}/README.md

@@ -28,6 +28,11 @@ Screenhot: using an LLM to understand your ad performance.
 When using uv no specific installation is needed. We can use uvx to directly run meta-ads-mcp:
 
 ```bash
+# RECOMMENDED: Use with Pipeboard authentication
+export PIPEBOARD_API_TOKEN=your_pipeboard_token  # Get your token at https://pipeboard.co
+uvx meta-ads-mcp
+
+# Alternative: Use with direct Meta authentication
 uvx meta-ads-mcp --app-id YOUR_META_ADS_APP_ID
 ```
 
@@ -55,15 +60,50 @@ pip install meta-ads-mcp
 After installation, you can run it as:
 
 ```bash
+# RECOMMENDED: Use with Pipeboard authentication
+export PIPEBOARD_API_TOKEN=your_pipeboard_token  # Get your token at https://pipeboard.co
 python -m meta_ads_mcp
+
+# Alternative: Use with direct Meta authentication
+python -m meta_ads_mcp --app-id YOUR_META_ADS_APP_ID
 ```
 
 ## Configuration
 
+### Quick Start with Pipeboard Authentication (Recommended)
+
+The easiest way to configure Meta Ads MCP is using Pipeboard authentication:
+
+1. Sign up at [Pipeboard.co](https://pipeboard.co) and generate an API token - **Get your free token at [https://pipeboard.co](https://pipeboard.co)**
+2. Set the environment variable:
+   ```bash
+   export PIPEBOARD_API_TOKEN=your_pipeboard_token   # Token obtainable via https://pipeboard.co
+   ```
+3. Run meta-ads-mcp without needing to set up a Meta Developer App:
+   ```bash
+   uvx meta-ads-mcp
+   ```
+
+This method provides longer-lived tokens (60 days), simplified setup, and automatic token renewal.
+
 ### Usage with Claude in Cursor
 
 Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor:
 
+```json
+"mcpServers": {
+  "meta-ads": {
+    "command": "uvx",
+    "args": ["meta-ads-mcp"],
+    "env": {
+      "PIPEBOARD_API_TOKEN": "your_pipeboard_token"  // Token obtainable via https://pipeboard.co
+    }
+  }
+}
+```
+
+Or if you prefer direct Meta authentication (using your own Facebook app):
+
 ```json
 "mcpServers": {
   "meta-ads": {
@@ -166,7 +206,28 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `ad_id`: Meta Ads ad ID
     - Returns: The ad image ready for direct visual analysis
 
-12. `mcp_meta_ads_get_insights`
+12. `mcp_meta_ads_update_ad`
+    - Update an ad with new settings
+    - Inputs:
+      - `ad_id`: Meta Ads ad ID
+      - `status`: Update ad status (ACTIVE, PAUSED, etc.)
+      - `bid_amount`: Bid amount in account currency (in cents for USD)
+      - `access_token` (optional): Meta API access token (will use cached token if not provided)
+    - Returns: Confirmation with updated ad details and a confirmation link
+
+13. `mcp_meta_ads_update_adset`
+    - Update an ad set with new settings including frequency caps
+    - Inputs:
+      - `adset_id`: Meta Ads ad set ID
+      - `frequency_control_specs`: List of frequency control specifications
+      - `bid_strategy`: Bid strategy (e.g., 'LOWEST_COST_WITH_BID_CAP')
+      - `bid_amount`: Bid amount in account currency (in cents for USD)
+      - `status`: Update ad set status (ACTIVE, PAUSED, etc.)
+      - `targeting`: Targeting specifications including targeting_automation
+      - `access_token` (optional): Meta API access token (will use cached token if not provided)
+    - Returns: Confirmation with updated ad set details and a confirmation link
+
+14. `mcp_meta_ads_get_insights`
     - Get performance insights for a campaign, ad set, ad or account
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -176,7 +237,7 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `level`: Level of aggregation (ad, adset, campaign, account)
     - Returns: Performance metrics for the specified object
 
-13. `mcp_meta_ads_debug_image_download`
+15. `mcp_meta_ads_debug_image_download`
     - Debug image download issues and report detailed diagnostics
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
@@ -184,8 +245,9 @@ Add this to your `claude_desktop_config.json` to integrate with Claude in Cursor
       - `ad_id`: Meta Ads ad ID (optional, used if url is not provided)
     - Returns: Diagnostic information about image download attempts
 
-14. `mcp_meta_ads_get_login_link`
+16. `mcp_meta_ads_get_login_link`
     - Get a clickable login link for Meta Ads authentication
+    - NOTE: This method should only be used if you're using your own Facebook app. If using Pipeboard authentication (recommended), set the PIPEBOARD_API_TOKEN environment variable instead (token obtainable via https://pipeboard.co).
     - Inputs:
       - `access_token` (optional): Meta API access token (will use cached token if not provided)
     - Returns: A clickable resource link for Meta authentication
@@ -202,13 +264,47 @@ Before using the MCP server, you'll need to set up a Meta Developer App:
 
 ## Authentication
 
-The Meta Ads MCP uses the OAuth 2.0 flow designed for desktop apps. When authenticating, it will:
+The Meta Ads MCP supports two authentication methods:
+
+### 1. Pipeboard Authentication (Recommended ⭐)
+
+This method uses [Pipeboard.co](https://pipeboard.co) to manage Meta API authentication, providing longer-lived tokens and a simplified flow:
+
+1. **Get your Pipeboard token**: Sign up at [https://pipeboard.co](https://pipeboard.co) to generate your free API token
+2. Set the `PIPEBOARD_API_TOKEN` environment variable with your token: 
+   ```bash
+   export PIPEBOARD_API_TOKEN=your_pipeboard_token
+   ```
+3. Run the Meta Ads MCP normally - it will automatically detect and use Pipeboard authentication:
+   ```bash
+   uvx meta-ads-mcp
+   ```
+4. The first time you run a command, you'll be provided with a login URL to authorize with Meta
+
+**Benefits of Pipeboard authentication:**
+- ✅ Longer-lived tokens (60 days)
+- ✅ No need to configure a Meta Developer App
+- ✅ Simpler setup with just an API token
+- ✅ Automatic token renewal
+
+To test the Pipeboard authentication flow:
+```bash
+python test_pipeboard_auth.py --api-token YOUR_PIPEBOARD_TOKEN
+```
+
+### 2. Direct Meta OAuth (Legacy)
+
+The traditional OAuth 2.0 flow designed for desktop apps. This method should only be used if you are using your own Facebook app instead of Pipeboard.
+
+When authenticating, it will:
 
 1. Start a local callback server on your machine
 2. Open a browser window to authenticate with Meta
 3. Ask you to authorize the app
 4. Redirect back to the local server to extract and store the token securely
 
+This method requires you to [create a Meta Developer App](#create-a-meta-developer-app) first.
+
 ## Troubleshooting and Logging
 
 The Meta Ads MCP includes a comprehensive logging system to help troubleshoot issues:
@@ -223,21 +319,29 @@ Log files are stored in a platform-specific location:
 
 ### Common Issues
 
-#### App ID Issues
+#### Authentication Issues
+
+If you're having authentication problems:
 
-If you encounter errors like `(#200) Provide valid app ID`, check the following:
+1. **Recommended: Use Pipeboard Authentication**
+   - Set `export PIPEBOARD_API_TOKEN=your_token` and retry
+   - This provides longer-lived tokens and better reliability
+   - Verify your token in the Pipeboard dashboard
 
-1. Ensure you've set up a Meta Developer App correctly
-2. Verify that you're passing the correct App ID using one of these methods:
-   - Set the `META_APP_ID` environment variable: `export META_APP_ID=your_app_id`
-   - Pass it as a command-line argument: `meta-ads-mcp --app-id your_app_id`
+2. For App ID issues (when using direct authentication):
+   If you encounter errors like `(#200) Provide valid app ID`, check the following:
+   - Ensure you've set up a Meta Developer App correctly
+   - Verify that you're passing the correct App ID using one of these methods:
+     - Set the `META_APP_ID` environment variable: `export META_APP_ID=your_app_id`
+     - Pass it as a command-line argument: `meta-ads-mcp --app-id your_app_id`
 
-#### Authentication Errors
+#### API Errors
+
+If you receive errors from the Meta API:
 
-Authentication errors can be tracked in the log file. Check for:
-- Token expiration issues
-- App permission problems
-- Connection errors
+1. Verify your app has the Marketing API product added
+2. Ensure the user has appropriate permissions on the ad accounts
+3. Check if there are rate limits or other restrictions on your app
 
 ### Debugging Command
 
@@ -268,14 +372,15 @@ uvx meta-ads-mcp --app-id=your_app_id
 The Meta Ads MCP follows security best practices:
 
 1. Tokens are cached in a platform-specific secure location:
-   - Windows: `%APPDATA%\meta-ads-mcp\token_cache.json`
-   - macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json`
-   - Linux: `~/.config/meta-ads-mcp/token_cache.json`
+   - Windows: `%APPDATA%\meta-ads-mcp\token_cache.json` or `%APPDATA%\meta-ads-mcp\pipeboard_token_cache.json`
+   - macOS: `~/Library/Application Support/meta-ads-mcp/token_cache.json` or `~/Library/Application Support/meta-ads-mcp/pipeboard_token_cache.json`
+   - Linux: `~/.config/meta-ads-mcp/token_cache.json` or `~/.config/meta-ads-mcp/pipeboard_token_cache.json`
 
 2. You do not need to provide your access token for each command; it will be automatically retrieved from the cache.
 
 3. You can set the following environment variables instead of passing them as arguments:
-   - `META_APP_ID`: Your Meta App ID (Client ID)
+   - `META_APP_ID`: Your Meta App ID (Client ID) - for direct OAuth method
+   - `PIPEBOARD_API_TOKEN`: Your Pipeboard API token - for Pipeboard authentication method
 
 ## Testing
 
@@ -297,11 +402,12 @@ python test_meta_ads_auth.py --app-id YOUR_APP_ID --force-login
 
 When using the Meta Ads MCP with an LLM interface (like Claude):
 
-1. Test authentication by calling the `mcp_meta_ads_get_login_link` tool
-2. Verify account access by calling `mcp_meta_ads_get_ad_accounts`
-3. Check specific account details with `mcp_meta_ads_get_account_info`
+1. If using direct Meta authentication (your own Facebook app), test authentication by calling the `mcp_meta_ads_get_login_link` tool
+2. If using Pipeboard authentication (recommended), ensure the PIPEBOARD_API_TOKEN environment variable is set (token obtainable via https://pipeboard.co)
+3. Verify account access by calling `mcp_meta_ads_get_ad_accounts`
+4. Check specific account details with `mcp_meta_ads_get_account_info`
 
-These functions will automatically handle authentication if needed and provide a clickable login link.
+These functions will automatically handle authentication if needed and provide a clickable login link if required.
 
 ## Troubleshooting
 
@@ -310,20 +416,20 @@ These functions will automatically handle authentication if needed and provide a
 If you encounter authentication issues:
 
 1. When using the LLM interface:
-   - Use the `mcp_meta_ads_get_login_link` tool to generate a fresh authentication link
+   - If using direct Meta authentication (your own Facebook app), use the `mcp_meta_ads_get_login_link` tool to generate a fresh authentication link
+   - If using Pipeboard authentication (recommended), ensure the PIPEBOARD_API_TOKEN environment variable is set (token obtainable via https://pipeboard.co)
    - Ensure you click the link and complete the authorization flow in your browser
    - Check that the callback server is running properly (the tool will report this)
 
-2. When using the command line:
+2. When using Pipeboard authentication:
+   - Verify your `PIPEBOARD_API_TOKEN` is set correctly (token obtainable via https://pipeboard.co)
+   - Check if you need to complete the authorization process by visiting the provided login URL
+   - Try forcing a new login: `python test_pipeboard_auth.py --force-login`
+
+3. When using direct Meta OAuth:
    - Run with `--force-login` to get a fresh token: `uvx meta-ads-mcp --login --app-id YOUR_APP_ID --force-login`
    - Make sure the terminal has permissions to open a browser window
 
-3. General authentication troubleshooting:
-   - Check that your app is properly configured in the Meta Developers portal
-   - Ensure your app has the necessary permissions (ads_management, ads_read, business_management)
-   - Verify the app's redirect URI includes `http://localhost:8888/callback`
-   - Try clearing the token cache (located in platform-specific directories listed in the Token Caching section)
-
 ### API Errors
 
 If you receive errors from the Meta API: