Chorus MCP Server

by chorushq Your server? Claim it

answering

Chorus is answering right now. Last checked 10 min ago.

Run ad campaigns on Meta, Google Ads and LinkedIn from your assistant. Spend waits for your OK.

Uptime history 5 days of history

5 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

405 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Chorus every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add chorus --transport http https://mcp.chorushq.net/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.chorushq.net/mcp

~/.codex/config.toml

[mcp_servers.chorus]
url = "https://mcp.chorushq.net/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "chorus": {
      "url": "https://mcp.chorushq.net/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "chorus": {
      "type": "http",
      "url": "https://mcp.chorushq.net/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.chorushq.net/mcp	streamable-http	sign-in	397 ms	10 min ago

Alternatives to Chorus

same job, measured the same way

Growomat

by growomat

Build, edit and sync Google, Microsoft, Reddit and Meta ad campaigns from your assistant.

answering

Adrex AI

by gauravapiscean

Open-source MCP server for Google Ads & Meta Ads — manage campaigns from any AI assistant.

64 installs/wk local only

Adako: ad ops for AI assistants

by adako

Google, Meta, LinkedIn and ChatGPT Ads for AI assistants. Every change needs your approval.

answering

LoomaScale Ads

by loomascale

Run Google Ads and Meta Ads from ChatGPT or Claude: audit wasted spend, create and manage campaigns.

answering

Adwarp

by adwarp-dev

Open-source ad agent for LinkedIn Ads and Google Ads. Drafts campaigns, audiences and reports.

609 installs/wk answering

uplads

by uplads

Ads MCP for Meta, Google Ads, TikTok, Snapchat and LinkedIn: stage launches and manage campaigns.

answering

Opus Growth

by opus-growth

Run Google, Meta, TikTok, LinkedIn and Microsoft Ads, GA4, Search Console and WordPress from your AI

answering

MCP Ads

by mcp-ads

Run Google Ads, Meta Ads, GA4 and Search Console from chat: read, audit and launch campaigns.

answering

Chorus — questions

Answers built from our own checks of this server.

Why is there no tool list for Chorus?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Chorus working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 405 ms. The bar chart above shows every period we have measured.

How do I connect Chorus?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Chorus?

No API key is involved. Chorus answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Chorus?

It answers our handshake in 405 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.