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 still needs access granted from within Meltwater by a Meltwater account admin, and then signs in with their own Meltwater credentials before they can use it.
Before you start
| Requirement | Detail |
| Claude plan | A Claude Enterprise or Team plan. Connectors are managed at the organization level, so this doesn't apply to individual Pro accounts. |
| Claude role | You'll need Owner or Primary Owner access to your Claude organization to enable the connector for everyone. |
| Meltwater role | A Meltwater account admin will need to grant individual users access to the Claude connector inside Meltwater. |
| Meltwater plan | An active Meltwater subscription. Each end user signs in with their own Meltwater credentials via OAuth. |
| Meltwater sign-in | Users sign in through Meltwater's OAuth flow, with SSO if your organization uses it, or with their Meltwater email and password if not. Both are supported. |
How the connection works
The Meltwater connector is a remote MCP server hosted by Meltwater. There's nothing to install: no software on user machines, no servers to run, no files to edit.
You add the connector once for your organization, using Meltwater's remote MCP server URL. Each user then authorizes it individually by signing in to their own Meltwater account via OAuth.
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're already entitled to, from inside Claude.
Interim setup, while the connector is pending directory approval. The Meltwater connector is currently being reviewed for the official Claude connector directory. Until it's listed, you add it as a custom connector by pointing Claude at Meltwater's MCP URL (Step 2 below). This is a one-time action and takes about a minute. Once Meltwater is live in the directory, new organizations will be able to add it directly from Browse connectors instead, but the custom-connector route will keep working, so there's nothing you'll need to migrate.
Step 1: Open connector settings
- Sign in to Claude at claude.ai with your Owner or Primary Owner account.
- 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.
- On the Connectors page, select Add custom connector (you may need to click Browse connectors first, then choose the custom, or "connect your own," option at the bottom).
- Give it a name your users will recognize, for example, Meltwater.
- In the URL (remote MCP server) field, enter: https://api.meltwater.com/v2/mcp
- Leave Client ID and Client Secret blank. Meltwater's server supports Dynamic Client Registration over OAuth, so Claude registers itself automatically. There are no credentials to obtain or paste.
- Save. Confirm the Meltwater connector is now listed under your organization's enabled connectors.
Once added, the Meltwater connector becomes available to the members you've chosen to give it to. Each user still completes their own sign-in the first time they use it. Adding it org-wide doesn't sign anyone in on their behalf.
Once Meltwater is in the directory, you'll instead be able to click Browse connectors → Meltwater → Add to your team and skip the URL step. Both routes produce the same connector, so you won't need to re-add it.
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. Revoking the OAuth grant in Meltwater cuts off an individual user.
Step 5: Roll out to users
Once enabled and governed, make sure your Meltwater account admins have granted the relevant users access to the connector. Then 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.