ZenABM

com.zenabmPublished by zenabm.comOfficial publisherv1.0.0Updated Nov 5, 2026

LinkedIn ads, ABM and CRM data for AI agents: reports, audits, and campaign management.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server from ZenABM giving AI assistants LinkedIn ads, ABM and CRM data for reports, audits and campaign management.

What you can do
  • Pull LinkedIn ads, ABM and CRM data into assistant-driven reports.
  • Run audits over advertising and account-based marketing data.
  • Manage campaigns through the connected ZenABM account.
  • No individual tools are listed in the manifest, so exact capabilities are only described at this level.
When to use it
Useful when you want an assistant to work with LinkedIn advertising and account-based marketing data, or to produce reports and audits and manage campaigns without leaving the chat.
Requirements
A remote server reached at the ZenABM endpoint over streamable HTTP; OAuth authentication is required, so a ZenABM account with the relevant LinkedIn ads and CRM data connected is needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your ZenABM account and the LinkedIn ads and CRM data behind it. Campaign management implies the assistant can change live advertising settings and spend, so review actions before confirming. Data is handled by a third-party service.

Installation

In SourceWeft

  1. Open ZenABM in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.zenabm%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "zenabm": {
      "type": "http",
      "url": "https://app.zenabm.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.