Inside Ads is an MCP server with 3 tools an agent can call, among them create_campaign_draft, estimate_campaign, get_draft_status. It answers at https://app.inside.ad/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Telegram ad exchange: estimate reach and cost with no account, then create and run campaigns.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_campaign_draft | Build a ready-to-launch ad campaign for a product WITHOUT the user having an account yet. Parses the landing page, generates ad creatives, and returns a single checkout link. Give that link to the user: they sign in there, the campaign move Inputs: url, description, budget, geo, lang |
estimate_campaign | Estimate reach, clicks and cost of advertising a product to Telegram audiences — no account or authorization required. Call this FIRST, before asking the user to connect an account: it tells you whether inside.ad has relevant inventory for Inputs: url, description, keywords, budget, geo, lang |
get_draft_status | Check what happened to a campaign draft you created with create_campaign_draft: whether the user opened the link, signed in and paid. Poll this instead of asking the user to report back. Inputs: draftId |
Every block below points at https://app.inside.ad/api/mcp. Pick your client and copy.
claude mcp add --transport http inside-ads https://app.inside.ad/api/mcp
{
"mcpServers": {
"inside-ads": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.inside.ad/api/mcp"]
}
}
}{
"mcpServers": {
"inside-ads": {
"url": "https://app.inside.ad/api/mcp"
}
}
}{
"servers": {
"inside-ads": {
"type": "http",
"url": "https://app.inside.ad/api/mcp"
}
}
}{
"context_servers": {
"inside-ads": {
"url": "https://app.inside.ad/api/mcp"
}
}
}{
"mcpServers": {
"inside-ads": {
"serverUrl": "https://app.inside.ad/api/mcp"
}
}
}{
"mcpServers": {
"inside-ads": {
"url": "https://app.inside.ad/api/mcp"
}
}
}name: Inside Ads
version: 0.0.1
schema: v1
mcpServers:
- name: Inside Ads
type: streamable-http
url: https://app.inside.ad/api/mcp{
"mcpServers": {
"inside-ads": {
"httpUrl": "https://app.inside.ad/api/mcp"
}
}
}{
"mcpServers": {
"inside-ads": {
"type": "http",
"url": "https://app.inside.ad/api/mcp"
}
}
}{
"mcpServers": {
"inside-ads": {
"url": "https://app.inside.ad/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapp.inside.ad%2Fapi%2Fmcp&type=streamable_http&id=inside-ads&name=Inside%20Ads
It answered our last check on 17 October 2026 in 98 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by inside.ad and served from app.inside.ad, the vendor's own domain: https://app.inside.ad/api/mcp.
3, as returned by the server's own tools/list on 7 September 2026: create_campaign_draft, estimate_campaign, get_draft_status.
It answered our last check on 17 October 2026 in 98 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.inside.ad/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ad.inside. Endpoint host: app.inside.ad. ARD identifier: urn:air:ad.inside:mcp:inside-ads.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.