Brand24

What the Brand24 connector does

The Brand24 MCP server connects your social listening projects to Claude, ChatGPT and any MCP-compatible agent. It exposes four tools that read account events, project statistics, mention sources and discussion topics — so you ask what people said about your brand this week instead of opening a dashboard. Sign-in is OAuth, and nothing in this connector posts.

Brand24 tools (4)

• brand24_account_events
• brand24_project_stats
• brand24_project_sources
• brand24_topics_overview

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

• The plan gate is two tiers above what the connector's own doc implies. The help article says only that MCP access is available to Brand24 subscribers. The pricing page feature matrix marks MCP absent on Individual ($249/mo) and Team ($349/mo) and present on Pro ($499/mo), Business ($699/mo) and Enterprise (from $1,499/mo). A reader trusting the help article alone could subscribe twice and still not have the connector.
• Two of the four tools sit behind the same gate independently. Brand24 documents AI Events as available on Pro and higher, and AI Topic Analysis as available to Pro, Business and Enterprise customers. On Business, AI Insights and AI Topics are further scoped to a set number of projects (2 on Pro, 5 on Business).
• History is shallow by design. Brand24 states it does not collect data older than 30 days except in special cases, and describes its model as a wide fishing net rather than an excavator. Your assistant cannot answer a question about last year unless the project was already running then.
• Archived mentions expire. One month on Individual; 12 months on Team, Pro, Business and Enterprise. Longer retention requires contacting Brand24's customer success team.
• Keyword and volume quotas bound what exists to read. Pro allows 12 keywords and 40,000 mentions a month; Business allows 25 keywords and 100,000; Individual and Team allow 3 and 7 keywords. Mentions beyond the monthly quota are not collected, so they cannot be read.
• Engagement figures are frozen at collection time. Brand24 states it provides the stats visible at the moment a mention was collected — so a post's like and share counts as reported by the connector are not current.
• We could not read tool schemas. The endpoint is OAuth-gated, so there are no parameter definitions, no output shapes and no readOnlyHint / destructiveHint annotations on this page. Every per-tool description above is inferred from the name plus Brand24's feature documentation, and could be wrong about what a tool actually returns.
• No scope names write access, so none can be audited afterwards. projects:read is the only scope advertised. That supports the read-only reading, but it also means no consent screen could offer a narrower grant and no issued token can be inspected for one later.
• Dynamic client registration is advertised but not implemented. The authorization-server metadata publishes a registration_endpoint, and that endpoint returns HTTP 501 (checked 2026-09-08). A client relying on automatic registration will fail; use the connector flow.
• Not a substitute for the dashboard. Blocking a spam source, deleting a mention, editing keywords and exporting reports all remain dashboard actions. The connector reads.

Frequently asked questions

Sources

• Brand24 MCP help article (fetched 2026-09-09; 606 words, also served as clean Markdown at the same URL with a .md suffix, and indexed in the host's llms.txt) · retrieved 2026-09-09
• Brand24 pricing page (fetched 2026-09-09; the plan feature matrix, including the MCP row and per-plan keyword and mention quotas). Note the vendor's /pricing/ path returns HTTP 301 to this URL; the destination is cited. · retrieved 2026-09-09
• Brand24 AI Events (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 AI Topic Analysis (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 Summary tab overview (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 Sources tab overview (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 Sources filter (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 on historical data (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 on mention archive retention (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 on project versus keyword scoping (fetched 2026-09-09) · retrieved 2026-09-09
• Brand24 on post engagement statistics (fetched 2026-09-09) · retrieved 2026-09-09
• Live authentication probe against https://mcp.brand24.com/v1/mcp — anonymous initialize returned HTTP 401 with a WWW-Authenticate: Bearer challenge naming the resource metadata document; an invalid bearer changed the error body; an invented path on the same host returned a 301 to the marketing site rather than a 401 (2026-09-08) · retrieved 2026-09-08
• RFC 9728 protected-resource descriptor — and the authorization-server metadata at https://oauth.brand24.com/resources/res_99790078397645058 (retrieved 2026-09-08; both publish scopes_supported: ["projects:read"]) · retrieved 2026-09-08
• help.brand24.com/robots.txt — permits the documentation path; no Content-Signal line is present (fetched 2026-09-09) · retrieved 2026-09-09
• Anthropic Connectors Directory entry — , via the committed 2026-09-08 snapshot (tool names, categories, endpoint, tier) · retrieved 2026-09-08