Developer · Remote MCP server
Adside
AI agents that manage paid ads on Meta, LinkedIn, and Google Ads from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.adside/adside- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-16
- Updated
- 2026-07-16
- Publisher
- ai.adside
- Namespace
- Namespace verified by the MCP Registry via the domain adside.ai · how
- Listed under
- LinkedIn MCP servers
- Website
- www.adside.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.adside.ai/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Adside
Adside is a remote MCP server: there is nothing to install. Its endpoint is https://api.adside.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ADITUS Developer Portal MCPRead-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend. | Remote · HTTPLive check: ✓ handshake |
| Adobe MCPDrive Adobe CC (AE, Photoshop, Illustrator, Premiere, Character Animator) from any MCP client. | Local · stdio |
| AdoMcpDatabase MCP server for schema discovery, comments, and SQL queries. | Local · stdio |
| adrkit decision memoryDeterministic, offline, read-only ADR decision memory for coding agents. No model or network calls. | Local · stdio |
| AdsTurbo Creative MCPLocal-only MCP server and CLI for AI video ad briefs, UGC scripts, storyboards, and prompts. | Local · stdio |
| Advanced GitLab MCP server58 CQRS tools exposing 230 GitLab operations across 26 entity types. | Local · stdio |
| Advanced Zebrunner MCP ServerAdvanced analytics, reporting, and safe mutations for Zebrunner. 64 tools, 14 resources, 17 prompts. | Local · stdio, HTTP |
| AegisCharter-bound defensive security copilot: secrets, obfuscation, deps, Dockerfile, IaC scans. | Local · stdio |