Glitch Grow Linkedin Ad Mcp

com.glitchexecutor.growPublished by grow.glitchexecutor.comv0.1.1Updated Oct 24, 2026

MCP server for the LinkedIn Marketing API — campaigns, analytics, creatives.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work with the LinkedIn Marketing API for campaigns, analytics, and creatives.

What you can do
This MCP server exposes the LinkedIn Marketing API to an assistant, covering campaigns, analytics, and creatives. It runs as a local process over stdio and is intended for desktop use. No tools are listed in the registry entry, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to read or manage LinkedIn advertising data such as campaigns, performance analytics, or creative assets. It is aimed at desktop setups rather than browser-based use.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package glitch-grow-linkedin-ad-mcp over stdio. Desktop only; not web executable. No authentication, environment variables, or headers are declared, though the LinkedIn Marketing API normally requires credentials.
Before you install
The registry declares no authentication, environment variables, or headers, yet the LinkedIn Marketing API generally needs account credentials and permissions. Campaign and creative operations can change or spend advertising budget. Verify what credentials it actually requests and what it writes before installing.

Installation

In SourceWeft

  1. Open Glitch Grow Linkedin Ad Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.