LinkedIn Ads MCP Server

The materials explicitly state that no keys or environment variables are required; there is no stated need for API keys, OAuth tokens, or local sensitive credentials. Based on the available information, there is no clear red flag of credential collection or misuse.

The description claims it can create and manage LinkedIn ad campaigns and upload audiences, which normally implies interaction with external services; however, the materials also state no remote endpoint and provide no README, so the actual domains contacted and whether user input is sent out cannot be verified. The lack of detail warrants caution around real network behavior.

The objective checks mark this tool as executes-code, meaning local code/process execution is within its normal capability scope. The materials do not show requests for excessive system privileges beyond its stated function, nor obvious malicious execution behavior, so this is rated caution rather than high risk.

Per the description, it may handle ad drafts, targeting, creatives, and audience uploads, which could involve marketing content and audience data; however, the materials do not specify what local files it reads or writes, whether it persists data, or whether it accesses resources such as contacts/CSVs. There is no explicit evidence of overbroad access, but the data scope is insufficiently documented.

Positive factors include an auditable open-source repository and an MIT license; however, the source is a third-party registry, community adoption is only 0 stars, maintenance status is unknown, and the README is missing, which weakens verifiability and maturity. There is no direct high-risk red flag, but supply-chain trust remains limited.