Skip to main content

Add a custom ChatGPT MCP server

Add the public Meltwater server from ChatGPT Plugins when you want a custom connection for your workspace. Every client connects to the same Meltwater MCP server, so the URL and sign-in are the same as the ChatGPT Apps listing.

Connection details​

SettingValue
Server URLhttps://api.meltwater.com/v2/mcp
TransportStreamable HTTP
AuthenticationOAuth sign-in at app.meltwater.com, or a Meltwater API token in the apikey header

Before you start​

  • A Meltwater account with access to Meltwater MCP.
  • The server URL, exactly https://api.meltwater.com/v2/mcp, with no trailing slash.
  • ChatGPT on the web. Custom MCP connections are available on Business and Enterprise/Edu workspaces. Pro accounts can connect a custom server for read and fetch tools. Use the web app for this setup.
  • Permission to create the connection. On Business, only admins and owners can create and publish it. On Enterprise/Edu, admins and owners can create and test it, and they can grant Create plugins with MCPs to selected members. Only admins and owners can publish it for the workspace.

Connect​

1. Add a custom MCP server​

OpenAI's current Plugins flow adds the server from Plugins. Acknowledge the risk warning for the server when ChatGPT shows it. Workspace policies still apply.

  1. Open Plugins.
  2. Select +, then Add custom MCP server.
  3. Enter a name, such as Meltwater, and an optional description.
  4. Under Connection, paste the public HTTPS endpoint below. Leave Tunnel unset. Meltwater is already a public server.
  5. For authentication, choose OAuth. Leave the client ID and client secret empty. Meltwater publishes dynamic client registration, and its authorization server advertises the refresh_token grant, so ChatGPT can renew access after the first sign-in.
  6. Read the risk warning and select I understand and want to continue.
  7. Select Create as a plugin. Complete the Meltwater sign-in if ChatGPT opens it, then review the tools it discovers.
MCP server URL
https://api.meltwater.com/v2/mcp

On a Business or Enterprise/Edu workspace, test the connection in a new chat before you publish it. Type @ and select the app. Only an admin or owner can publish it, from Workspace settings, then Apps, then Drafts. After it is published, members see it under Apps with the label custom.

If the workspace still uses the older Apps page, an admin opens Workspace settings, then Apps, then Create. Someone allowed to create apps can open Settings, then Apps, then Create. Paste the same URL, choose OAuth, select Scan Tools, finish the Meltwater sign-in, then select Create. That draft is labeled Dev until an admin publishes it.

2. Authenticate​

Use either a browser sign-in or a Meltwater API token.

  • Browser sign-in (OAuth) - if the client opens a browser, sign in with your Meltwater account. The server publishes OAuth metadata for https://app.meltwater.com, including dynamic client registration, so you don't need to register a client. Leave the client ID and client secret empty if the form marks them as optional.
  • API token - for a custom agent, or a client that only offers a header field, send your Meltwater API token in a header named apikey. This is the method used in Building agents with Meltwater MCP. See API Credentials to create a token.

Treat your API token like a password. Keep it in an environment variable or a secrets manager - never in the URL, in client-side code, or in source control.

A request with no credential returns 401 with the body no bearer token. A rejected apikey value returns {"message":"Unauthorized"}.

3. Confirm the tool list​

Open a new conversation and ask the assistant to list the Meltwater tools it can call.

An empty list means either the account can't see any tools, or the client is still using a failed connection. After you fix authentication, start a new chat so the client runs initialize again.

Check the connection​

Once the server shows as connected, paste this prompt into a new conversation. It only uses tools the client has actually listed.

First session
I just connected Meltwater. Use the Meltwater MCP tools if they are available.

1. Confirm the connection by listing the tools you can call. If none are listed, say so and stop.
2. Ask me which brand, company, or topic to brief if I have not named one.
3. Use the available tools to pull recent coverage and the main narratives. Cite the source and date for each material fact the tools return.
4. Return a short briefing: what is being said, what changed, what is unresolved, and one recommended next action.
5. Before calling a tool, check its schema. Ask only for missing inputs, in a single message, then name the tools you will call.
See which tools you can access

Use the Tools Explorer to browse the tools available to your account - each tool's name, description and parameters - without connecting a client.

If it does not connect​

The URL is rejected

Use HTTPS and the exact URL https://api.meltwater.com/v2/mcp. A trailing slash, an http:// scheme, or any other Meltwater URL won't reach the server.

The client only offers SSE

Choose Streamable HTTP, which uses POST. An unauthenticated GET, POST or DELETE to the server URL returns 401 with the body no bearer token.

Tools stay empty after sign-in

Start a new chat so the client runs initialize and tools/list again. Check that the Meltwater account you signed in with has access to Meltwater MCP.

Still stuck?

Take a look at the FAQs, or contact our Support team.