
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 分