Connect Gemini Enterprise to Meltwater MCP

Connect the public Meltwater server for a Google work account. Every client connects to the same Meltwater MCP server, so the URL and sign-in are the same wherever you use it.

Connection details

Setting	Value
Server URL	https://api.meltwater.com/v2/mcp
Transport	Streamable HTTP
Authentication	OAuth 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.
• A Gemini Enterprise admin or a work account allowed to add data stores.
• A Meltwater OAuth client id and secret for a client whose redirect URI is https://vertexaisearch.cloud.google.com/oauth-redirect. Register that client in the next section, then store the secret in a secret manager. This page does not publish either value.

Connect

1. Create a custom MCP server data store

In the Google Cloud console for Gemini Enterprise, add a data source and search for Custom MCP Server. Google's setup page says the URL must be HTTPS and the transport is Streamable HTTP.

2. Register an OAuth client, then fill the published fields

Google's setup page requires an HTTPS Streamable HTTP URL, an authorization URL with no query string, a token URL, scopes, and an OAuth client id and secret. Gemini Enterprise does not call Meltwater's registration endpoint for you.

Register a confidential client at https://app.meltwater.com/oauth/register (also published as registration_endpoint on https://app.meltwater.com/.well-known/oauth-authorization-server). Include Google's redirect URI, https://vertexaisearch.cloud.google.com/oauth-redirect. The response returns client_id and client_secret. Copy both into Google's form and store the secret privately. Register again if you lose the secret. Meltwater accepts client_secret_post and client_secret_basic. Use client_secret_basic in a new registration if Google sends the secret with HTTP Basic authentication and the token request is rejected. Turn on PKCE in Google's form: Meltwater advertises the S256 code challenge method.

Terminal

curl -sS https://app.meltwater.com/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Gemini Enterprise",
    "redirect_uris": ["https://vertexaisearch.cloud.google.com/oauth-redirect"],
    "grant_types": ["authorization_code", "refresh_token"],
    "response_types": ["code"],
    "token_endpoint_auth_method": "client_secret_post",
    "scope": "tools:read tools:call"
  }'

Use the URLs and scopes below for the rest of the form. Paste the client_id and client_secret from the registration response. Do not type a placeholder.

Gemini Enterprise fields

MCP server URL: https://api.meltwater.com/v2/mcp
Authorization URL: https://app.meltwater.com/oauth/authorize
Token URL: https://app.meltwater.com/oauth/token
Scopes: tools:read tools:call

3. Attach the data store to an app

Google's docs say to add the data store to the Gemini Enterprise app people open. A normal gemini.google.com chat is a different product and does not read this data store.

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.