Getting Started

1. Get an API key

API keys are provisioned through the web app’s workspace settings. Each key is prefixed with sk_live_* and grants access to the channels (Meta, LinkedIn, Google) connected in that workspace.

2. Make your first call

All MCP tools are called via POST /{source}/mcp using JSON-RPC 2.0:

curl -X POST http://localhost:3100/meta/mcp \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "1",
    "method": "tools/call",
    "params": {
      "name": "list_meta_campaigns",
      "arguments": {
        "status": "ACTIVE",
        "limit": 5
      }
    }
  }'

3. Discover available tools

List all tools available for a source:

curl -X POST http://localhost:3100/meta/mcp \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": "1",
    "method": "tools/list"
  }'

4. Understanding the response

MCP tool responses follow this structure:

{
  "jsonrpc": "2.0",
  "id": "1",
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"campaigns\": [...], \"pagination\": {...}}"
      }
    ]
  }
}

The result.content[0].text field contains a JSON-stringified payload with the actual data.

Available sources

Source	Endpoint	Protocol
Meta	`POST /meta/mcp`	MCP (JSON-RPC 2.0)
LinkedIn	`POST /linkedin/mcp`	MCP (JSON-RPC 2.0)
Google Ads	`POST /google-ads/mcp`	MCP (JSON-RPC 2.0)
Google Sheets	`GET/POST /google/sheets/*`	REST
Google Drive	`GET/POST /google/drive/*`	REST