Skip to content

Commit 6cab08a

Browse files
committed
Add advanced token authentication options to README and STREAMABLE_HTTP_SETUP
- Introduced sections for Direct Token Authentication for Claude, Cursor, and Other Clients in README.md, detailing how to authenticate using a Pipeboard API token in the URL. - Updated STREAMABLE_HTTP_SETUP.md to include instructions for using token-based authentication with the hosted Remote MCP, emphasizing its utility for clients that do not support interactive authentication flows.
1 parent 41d715c commit 6cab08a

2 files changed

Lines changed: 46 additions & 0 deletions

File tree

‎README.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,16 @@ The fastest and most reliable way to get started is to **[🚀 Get started with
4343

4444
That's it! You can now ask Claude to analyze your Meta ad campaigns, get performance insights, and manage your advertising.
4545

46+
#### Advanced: Direct Token Authentication (Claude)
47+
48+
For direct token-based authentication without the interactive flow, use this URL format when adding the integration:
49+
50+
```
51+
https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
52+
```
53+
54+
Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
55+
4656
### For Cursor Users
4757

4858
Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP, click on "Needs login" to finish the login process.
@@ -58,12 +68,38 @@ Add the following to your `~/.cursor/mcp.json`. Once you enable the remote MCP,
5868
}
5969
```
6070

71+
#### Advanced: Direct Token Authentication (Cursor)
72+
73+
If you prefer to authenticate without the interactive login flow, you can include your Pipeboard API token directly in the URL:
74+
75+
```json
76+
{
77+
"mcpServers": {
78+
"meta-ads-remote": {
79+
"url": "https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN"
80+
}
81+
}
82+
}
83+
```
84+
85+
Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
86+
6187
### For Other MCP Clients
6288

6389
Use the Remote MCP URL: `https://mcp.pipeboard.co/meta-ads-mcp`
6490

6591
**[📖 Get detailed setup instructions for your AI client here](https://pipeboard.co)**
6692

93+
#### Advanced: Direct Token Authentication (Other Clients)
94+
95+
For MCP clients that support token-based authentication, you can append your Pipeboard API token to the URL:
96+
97+
```
98+
https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
99+
```
100+
101+
This bypasses the interactive login flow and authenticates immediately. Get your token at [pipeboard.co/api-tokens](https://pipeboard.co/api-tokens).
102+
67103
## Local Installation (Technical Users Only)
68104

69105
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)**.

‎STREAMABLE_HTTP_SETUP.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,16 @@ curl -H "Authorization: Bearer your_pipeboard_token" \
8383
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
8484
```
8585

86+
#### Remote MCP: Token in URL
87+
88+
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:
89+
90+
```
91+
https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN
92+
```
93+
94+
This is particularly useful for MCP clients that don't support interactive authentication flows.
95+
8696
### Alternative Method: Direct Meta Token
8797

8898
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.

0 commit comments

Comments
 (0)