Skip to main content

Connect Gemini to Meltwater MCP

Use Meltwater from the Gemini app through the Enterprise or Spark connection. Every client connects to the same Meltwater MCP server, so the URL and sign-in are the same wherever you use it.

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.
  • The Gemini Enterprise or Gemini Spark connection from the matching guide (Gemini Enterprise or Gemini Spark).

Connect​

1. Pick the product that matches the account​

The consumer Gemini app does not read an mcp.json file. Google's help page adds a custom MCP app from gemini.google.com for a personal Google Account, then lets you call it in web and mobile chat. A work or school account uses the Gemini Enterprise guide. Those are different consoles.

2. Confirm in the surface that owns the connection​

On a personal account, start a chat on gemini.google.com or in the mobile app, type @, and select the custom app. On a work account, ask inside the Gemini Enterprise app that has the data store.

MCP server URL
https://api.meltwater.com/v2/mcp

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.