
Adlane App
io.github.adlane-app由 GitHub 帳號 adlane-app 發布v1.2.1更新於 Nov 2, 2026
Read-only MCP connector for Adlane workspaces, Google and Meta ad accounts and campaign reports.
概覽
唯讀的 Adlane 連接器,讓助理檢視 Google 與 Meta 廣告工作區、帳戶和廣告活動報表。
- 可以做什麼
- 讀取已登入帳戶的個人資料,並列出其擁有的廣告工作區
- 尋找已擁有、已連結的 Google 與 Meta 廣告帳戶
- 依所選帳戶與報表時間範圍讀取廣告活動成效
- 在解讀結果前檢視廣告活動的設定與狀態
- 適用情境
- 適合讓助理比較不同期間的廣告成效、說明變化原因,並提出待審核的後續建議,而不會更動線上廣告帳戶。
- 執行需求
- 支援 Streamable HTTP 與 OAuth 的遠端 MCP 用戶端,或用於本機 stdio 橋接的 Node.js 22 以上版本;需要既有的 Adlane 帳戶,並在瀏覽器中登入授權 profile:read 與 ads:read 權限。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Adlane App,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.adlane-app%2Fmcp-server/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"adlane-app": {
"type": "http",
"url": "https://mcp.adlane.app/mcp"
}
}
}README
Adlane MCP
A clearer next move in Google and Meta advertising.
Adlane is an AI workspace for paid marketing. Bring your business website, goal and target market, connect Google or Meta ad accounts, and explore the evidence behind campaign decisions in one conversation. The product brings campaign analysis, market research and proposals together so teams can review the exact action before changing a live account.
Website · MCP repository · Agent skill · npm package
What this connector does
This package connects a local stdio MCP client to the hosted Adlane MCP server. Hosted tools run on Cloudflare; the local package bridges the connection and opens browser-based OAuth. You do not need to deploy a Worker or paste a product password into your assistant.
The MCP is read-only: it cannot create campaigns, approve proposals, change ads or budgets, or spend money. Campaign creation and approved live changes belong to the Adlane application. Preserve each platform’s attribution context; conversion value is not profit and overlapping conversions are not unique customers.
Example workflow
- Choose the owned workspace and ad account; note the reporting currency and timezone.
- Compare equal-length date ranges and inspect campaign details where a change needs explanation.
- Return observed changes and proposed next steps for review in Adlane, without modifying the account.
Things to ask your assistant
Compare the last two complete weeks for my selected ad account. Show spend and conversion changes with the reporting currency.
Which campaigns need a closer look? Read their current status before suggesting next steps.
Prepare a short review of Google and Meta performance without treating cross-platform conversions as unique sales.
Connect a remote MCP client
- Open the client’s custom MCP or connector settings.
- Enter
https://mcp.adlane.app/mcpas the remote server URL. - Complete Adlane sign-in in your browser and review the permissions on the consent screen.
- Return to the client and load the available tools.
Use a client that supports Streamable HTTP MCP and OAuth. Custom-connector availability depends on the client and your account. A public repository or npm release does not mean the integration has been approved for a client’s marketplace.
Claude Desktop and other stdio clients
Requires Node.js 22 or newer and an existing Adlane account. Add this entry to your client’s MCP configuration:
You can also run npx -y adlane-mcp from a terminal to start the bridge. It speaks MCP over stdio; it is not an interactive chat interface. For desktop clients that support MCPB extensions, download the .mcpb file from Adlane releases.
Permissions and account access
Requested scopes: profile:read ads:read. Older profile-only connections need to reconnect and explicitly approve the additional permissions before content tools are available.
Only approve a connection you intended to start. If sign-in opens a new tab, finish it, return to the consent screen and refresh. Manage or revoke connected apps.
The package uses pinned mcp-remote for OAuth, PKCE and local token storage. Tokens on your computer are credentials. The connector uses the fixed endpoint above and rejects command-line endpoint overrides. Product passwords and underlying provider credentials are not requested by this package.
Troubleshooting
- No tools or insufficient permissions: reconnect through browser consent and check the selected account.
- An empty list: confirm that the account owns the expected items. Empty results are different from a failed request.
- A link asks you to sign in: open it with the owning product account; a private product link is not a public share link.
- The browser blocks authorization: inspect the browser’s displayed error and restart an expired request from the client. Never send cookies or tokens in an issue.
Add the companion skill
The Adlane agent skill explains how to select the right records, interpret results and respect the workflow’s limits:
Learn more about Adlane
Development and support
Report a connector issue with your client, Node.js version and a redacted error. Keep package.json, manifest.json, server/config.json, server.json and the lockfile version aligned for releases. GitHub Actions publishes versioned npm packages and MCPB assets. See LICENSE for the MIT license.
來源:README.md,提交 da3ebeb
工具
0版本歷史
1- v1.2.1最新Sep 22, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分