meta-ads-mcp 0.4.4__tar.gz → 0.4.5__tar.gz

{meta_ads_mcp-0.4.4 → meta_ads_mcp-0.4.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meta-ads-mcp
-Version: 0.4.4
+Version: 0.4.5
 Summary: Model Context Protocol (MCP) plugin for interacting with Meta Ads API
 Project-URL: Homepage, https://github.com/pipeboard-co/meta-ads-mcp
 Project-URL: Bug Tracker, https://github.com/pipeboard-co/meta-ads-mcp/issues
@@ -49,7 +49,7 @@ A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for in
 
 ## Getting started with Remote MCP (Recommended)
 
-The fastest and most reliable way to get started is to **[🚀 Get started with our Meta Ads Remote MCP](https://pipeboard.co)**. No technical setup required - just connect and start analyzing your ad campaigns with AI!
+The fastest and most reliable way to get started is to **[🚀 Get started with our Meta Ads Remote MCP](https://pipeboard.co)**. Our cloud service uses streamable HTTP transport for reliable, scalable access to Meta Ads data. No technical setup required - just connect and start analyzing your ad campaigns with AI!
 
 ### For Claude Pro/Max Users
 
@@ -88,6 +88,8 @@ Use the Remote MCP URL: `https://mcp.pipeboard.co/meta-ads-mcp`
 
 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)**.
 
+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.
+
 ### Quick Local Setup
 
 ```bash

{meta_ads_mcp-0.4.4 → meta_ads_mcp-0.4.5}/README.md

@@ -24,7 +24,7 @@ A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for in
 
 ## Getting started with Remote MCP (Recommended)
 
-The fastest and most reliable way to get started is to **[🚀 Get started with our Meta Ads Remote MCP](https://pipeboard.co)**. No technical setup required - just connect and start analyzing your ad campaigns with AI!
+The fastest and most reliable way to get started is to **[🚀 Get started with our Meta Ads Remote MCP](https://pipeboard.co)**. Our cloud service uses streamable HTTP transport for reliable, scalable access to Meta Ads data. No technical setup required - just connect and start analyzing your ad campaigns with AI!
 
 ### For Claude Pro/Max Users
 
@@ -63,6 +63,8 @@ Use the Remote MCP URL: `https://mcp.pipeboard.co/meta-ads-mcp`
 
 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)**.
 
+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.
+
 ### Quick Local Setup
 
 ```bash

{meta_ads_mcp-0.4.4 → meta_ads_mcp-0.4.5}/STREAMABLE_HTTP_SETUP.md

@@ -26,10 +26,10 @@ export PIPEBOARD_API_TOKEN=your_pipeboard_token
 
 ### 3. Make HTTP Requests
 
-The server accepts JSON-RPC 2.0 requests at the `/mcp/` endpoint. Use the `Authorization` header to provide your token.
+The server accepts JSON-RPC 2.0 requests at the `/mcp` endpoint. Use the `Authorization` header to provide your token.
 
 ```bash
-curl -X POST http://localhost:8080/mcp/ \
+curl -X POST http://localhost:8080/mcp \
   -H "Content-Type: application/json" \
   -H "Accept: application/json, text/event-stream" \
   -H "Authorization: Bearer your_pipeboard_token" \
@@ -77,7 +77,7 @@ python -m meta_ads_mcp --transport streamable-http --port 9000
 
 ```bash
 curl -H "Authorization: Bearer your_pipeboard_token" \
-     -X POST http://localhost:8080/mcp/ \
+     -X POST http://localhost:8080/mcp \
      -H "Content-Type: application/json" \
      -H "Accept: application/json, text/event-stream" \
      -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
@@ -89,7 +89,7 @@ If you have a Meta Developer App, you can use a direct access token via the `X-M
 
 ```bash
 curl -H "X-META-ACCESS-TOKEN: your_meta_access_token" \
-     -X POST http://localhost:8080/mcp/ \
+     -X POST http://localhost:8080/mcp \
      -H "Content-Type: application/json" \
      -H "Accept: application/json, text/event-stream" \
      -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
@@ -100,7 +100,7 @@ curl -H "X-META-ACCESS-TOKEN: your_meta_access_token" \
 ### Server URL Structure
 
 **Base URL**: `http://localhost:8080`  
-**MCP Endpoint**: `/mcp/`
+**MCP Endpoint**: `/mcp`
 
 ### MCP Protocol Methods
 
@@ -129,7 +129,7 @@ All responses follow JSON-RPC 2.0 format:
 ### 1. Initialize Session
 
 ```bash
-curl -X POST http://localhost:8080/mcp/ \
+curl -X POST http://localhost:8080/mcp \
   -H "Content-Type: application/json" \
   -H "Accept: application/json, text/event-stream" \
   -H "Authorization: Bearer your_token" \
@@ -148,7 +148,7 @@ curl -X POST http://localhost:8080/mcp/ \
 ### 2. List Available Tools
 
 ```bash
-curl -X POST http://localhost:8080/mcp/ \
+curl -X POST http://localhost:8080/mcp \
   -H "Content-Type: application/json" \
   -H "Accept: application/json, text/event-stream" \
   -H "Authorization: Bearer your_token" \
@@ -162,7 +162,7 @@ curl -X POST http://localhost:8080/mcp/ \
 ### 3. Get Ad Accounts
 
 ```bash
-curl -X POST http://localhost:8080/mcp/ \
+curl -X POST http://localhost:8080/mcp \
   -H "Content-Type: application/json" \
   -H "Accept: application/json, text/event-stream" \
   -H "Authorization: Bearer your_token" \
@@ -180,7 +180,7 @@ curl -X POST http://localhost:8080/mcp/ \
 ### 4. Get Campaign Performance
 
 ```bash
-curl -X POST http://localhost:8080/mcp/ \
+curl -X POST http://localhost:8080/mcp \
   -H "Content-Type: application/json" \
   -H "Accept: application/json, text/event-stream" \
   -H "Authorization: Bearer your_token" \
@@ -210,7 +210,7 @@ import json
 class MetaAdsMCPClient:
     def __init__(self, base_url="http://localhost:8080", token=None):
         self.base_url = base_url
-        self.endpoint = f"{base_url}/mcp/"
+        self.endpoint = f"{base_url}/mcp"
         self.headers = {
             "Content-Type": "application/json",
             "Accept": "application/json, text/event-stream"
@@ -245,7 +245,7 @@ const axios = require('axios');
 class MetaAdsMCPClient {
     constructor(baseUrl = 'http://localhost:8080', token = null) {
         this.baseUrl = baseUrl;
-        this.endpoint = `${baseUrl}/mcp/`;
+        this.endpoint = `${baseUrl}/mcp`;
         this.headers = {
             'Content-Type': 'application/json',
             'Accept': 'application/json, text/event-stream'
@@ -325,7 +325,7 @@ export META_ACCESS_TOKEN=your_access_token
 
 1. **Connection Refused**: Ensure the server is running and accessible on the specified port.
 2. **Authentication Failed**: Verify your Bearer token is valid and included in the `Authorization` header.
-3. **404 Not Found**: Make sure you're using the correct endpoint (`/mcp/`).
+3. **404 Not Found**: Make sure you're using the correct endpoint (`/mcp`).
 4. **JSON-RPC Errors**: Check that your request follows the JSON-RPC 2.0 format.
 
 ### Debug Mode
@@ -337,7 +337,7 @@ Enable verbose logging by setting the log level in your environment if the appli
 Test if the server is running by sending a `tools/list` request:
 
 ```bash
-curl -X POST http://localhost:8080/mcp/ \
+curl -X POST http://localhost:8080/mcp \
   -H "Content-Type: application/json" \
   -H "Accept: application/json, text/event-stream" \
   -H "Authorization: Bearer your_token" \

{meta_ads_mcp-0.4.4 → meta_ads_mcp-0.4.5}/meta_ads_mcp/__init__.py

@@ -7,7 +7,7 @@ with the Claude LLM.
 
 from meta_ads_mcp.core.server import main
 
-__version__ = "0.4.4"
+__version__ = "0.4.5"
 
 __all__ = [
     'get_ad_accounts',

{meta_ads_mcp-0.4.4 → meta_ads_mcp-0.4.5}/meta_ads_mcp/core/auth.py

@@ -23,7 +23,9 @@ from .callback_server import (
 from .pipeboard_auth import pipeboard_auth_manager
 
 # Auth constants
-AUTH_SCOPE = "ads_management,ads_read,business_management,public_profile"
+# Scope includes pages_show_list and pages_read_engagement to fix issue #16
+# where get_account_pages failed for regular users due to missing page permissions
+AUTH_SCOPE = "ads_management,ads_read,business_management,public_profile,pages_show_list,pages_read_engagement"
 AUTH_REDIRECT_URI = "http://localhost:8888/callback"
 AUTH_RESPONSE_TYPE = "token"
 

{meta_ads_mcp-0.4.4 → meta_ads_mcp-0.4.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "meta-ads-mcp"
-version = "0.4.4"
+version = "0.4.5"
 description = "Model Context Protocol (MCP) plugin for interacting with Meta Ads API"
 readme = "README.md"
 requires-python = ">=3.10"