Connect Meltwater to Claude: IT Guide

This guide is for an organization’s  IT or  Claude Admin. It walks through enabling the Meltwater connector so your organization can query Meltwater in plain language from inside Claude, tracking brand coverage, comparing share of voice, and building briefings, without logging into the Meltwater platform for every question.

Enabling the connector makes it available to your organization. Each end user then signs in with their own Meltwater credentials before they can use it.

Before you start

How the connection works

The Meltwater connector is a remote MCP server hosted by Meltwater. 

Now available in Browse connectors. Meltwater is an approved Claude connector, so your admin adds it directly from Browse connectors in Claude, with no URL to paste.

If your organization prefers the manual route, you can still add Meltwater as a custom connector by pointing Claude at Meltwater's MCP URL; see the fallback note in Step 2.  

This means access to Meltwater data is always scoped to each user's own Meltwater permissions. Enabling the connector doesn’t grant anyone Meltwater access they don't already have. It only lets them reach the Meltwater data they are already entitled to, from inside Claude.

Step 1: Open connector settings

1. Sign in to Claude at claude.ai with your Owner or Primary Owner account.
2. Go to Organization settings → Connectors (the admin view). You'll see the connectors already enabled for your organization.

Step 2: Add the Meltwater connector for your organization

While Meltwater is pending directory approval, you add it as a custom connector using Meltwater's remote MCP server URL.

1. Meltwater is an approved Claude connector, so you add it from Browse connectors. This is a one-time action that takes about a minute. 
2. On the Connectors page, select Browse connectors.
3. Search for Meltwater and select it.
4. Add it to your organization.
5. Confirm the Meltwater connector is now listed under your organization’s enabled connectors.

Fallback: adding Meltwater by hand. If your organization needs the manual route, select Add custom connector (you may need to click Browse connectors first, then choose the custom / "connect your own" option at the bottom) and enter the URL https://api.meltwater.com/v2/mcp. Leave Client ID and Client Secret blank; Meltwater supports Dynamic Client Registration (DCR) over OAuth, so Claude registers itself automatically, with no credentials to obtain or paste. Both routes produce the same connector.

Step 3: Decide who can use it, and set your governance posture

Before announcing the connector, decide how tightly you want to control it. Claude Enterprise gives admins controls over connectors. The exact options in your console may include:

• Availability. Make the connector available to the whole organization, or scope it to specific groups or projects where Meltwater is relevant.
• Member-added connectors. Many organizations turn off the ability for individual members to add arbitrary connectors, and only allow admin-approved ones, like Meltwater. This keeps your connector surface area governed.
• Default on vs. opt-in. Decide whether the connector simply appears for users to switch on themselves, or whether you actively push it as enabled.

Step 4: Security and data considerations to brief your stakeholders

Useful points when your security or data governance team reviews this:

• Authentication is OAuth 2.0. Users never enter Meltwater credentials into Claude. They authenticate directly with Meltwater, and Claude receives a scoped access token. Tokens can be revoked from the Meltwater side at any time.
• Access is per-user and least-privilege. A user only sees the Meltwater data their own Meltwater account already permits.
• Revocation. Disabling the connector in Claude removes it for your organization.  

Step 5: Roll out to users

Once enabled and governed, point your users at the end-user connection guide. The user-side setup takes a couple of minutes and is a one-time action per user.