MCP Server#
The Brandwave MCP server connects Brandwave to AI assistants like Claude, ChatGPT, Copilot, and anything else that allows you to configure a custom MCP server. Once connected, your assistant can help find activities, manage campaigns, track performance, and answer questions about your marketing record in natural language.
Connecting your AI assistant#
- Open Claude, go to Settings, then select Connectors.
- Select Add custom connector and name it Brandwave.
- Enter
https://mcp.gobrandwave.com/mcpas the remote MCP server URL. - Select Connect and complete the Brandwave sign-in in the browser window that opens.
- If the final localhost callback page cannot connect, copy its complete address and paste it back into Claude when prompted.
Remote MCP endpoint#
Point an MCP-compatible client at the Brandwave endpoint:
https://mcp.gobrandwave.com/mcp
It speaks streamable HTTP, secured with OAuth 2.1 and PKCE. Newer clients are identified by their metadata document; older ones can still register dynamically.
Permissions#
Access is granted with two scopes. The normal management connection requests read and write access together, and Brandwave shows both before you approve it. A client that explicitly requests read-only access remains read-only.
brandwave.read- Explore and analyze the record.
brandwave.write- Create, update, and delete records. A write request also includes read access.
Sign in securely#
When you first connect, your client opens a browser window so you can sign in to Brandwave. After that, the client remembers the connection and keeps it refreshed.
Choosing a workspace
Decision-ready marketing workflows#
Brandwave includes focused tools that answer common operating questions without forcing your assistant to assemble a conclusion from many low-level reads. Use get_campaign_portfolio for broad campaign health, compare_campaigns for period-aware comparisons, get_marketing_brief for stakeholder reporting, and get_marketing_recommendations for evidence-backed next actions.
Campaign planning fields are first-class records, including the summary, objective, audience, key message, desired outcomes, channels, owner, and tags. Readiness and closeout tools combine that context with ISO currency, measurement provenance, limitations, and customer-facing campaign links.
Native tools#
Brandwave gives your client native tools for checking the current Brandwave context and fetching a complete record by its canonical URL or stable identifier. The rest of the catalog consists of focused tools with exact input and output schemas.
Get Brandwave context#
Return the authenticated user's profile, accessible workspaces, active workspace, and only the current assistant connection. Use this before answering identity, profile, workspace, or current-connection questions.
Tool name: get_brandwave_context
Protocol hints: readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false.
Fetch Brandwave record#
Fetch the complete Brandwave record identified by a search result and return its canonical Brandwave URL with a useful structured record.
Tool name: fetch
Protocol hints: readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false.
Browse the tool pages for example prompts and exact operation details.