Connect Meltwater to ChatGPT: IT Guide

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

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

Meltwater appears in ChatGPT as a plugin, and the things it can do for you show up as actions. 

Before you start

How the connection works

The Meltwater plugin 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 (admin) enable the Meltwater plugin once for your workspace from the ChatGPT Plugins Marketplace. 

Plugins are disabled by default, so nothing is reachable until you enable it. 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 plugin 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 ChatGPT.

Step 1: Open plugin settings

1. Sign in to ChatGPT at chatgpt.com with your Workspace Owner or Admin account.
2. Go to Workspace settings → Plugins. You'll see the plugins available to your workspace and their enabled or disabled state.

Step 2: Enable the Meltwater plugin for your workspace

1. Find Meltwater in the plugin directory.
2. Select it and enable it for the workspace.
3. Confirm Meltwater now shows under Workspace settings → Plugins → Enabled.

Once enabled, users can browse and connect the Meltwater plugin. Each user still completes their own OAuth sign-in the first time they use it. Enabling it for the workspace doesn't sign anyone in on their behalf.

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

ChatGPT Enterprise gives admins granular control over plugins. Decide how tightly to scope Meltwater before you announce it:

• Role-based access. Plugins are off by default and only reachable by the roles you allow. You can assign the Meltwater plugin to one or more custom roles, so only the relevant teams (for example, Comms or Insights) can connect it.
• Action control. For the Meltwater plugin's actions, choose Allow all actions, Allow only read actions, or a custom set. If you want Meltwater used purely for read and reporting, not for creating or editing saved searches, set it to read-only. This applies workspace-wide and users can't override it.
• New actions. If you pick Custom, decide how actions added later are handled: enable all new actions, only enable new read actions, or disable new actions, so future Meltwater capabilities don't switch on silently.

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 ChatGPT. They authenticate directly with Meltwater, and ChatGPT 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, and only the actions your Action control settings allow.
• Revocation. Disabling the plugin in your workspace removes it for everyone. Revoking the OAuth grant in Meltwater cuts off an individual user.

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