Connect Gemini CLI to Meltwater MCP

Add the public Meltwater server to the Gemini command line. 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.
• Gemini CLI installed and signed in to Google.

Connect

1. Edit the Gemini CLI settings

Gemini CLI reads mcpServers from ~/.gemini/settings.json, or from .gemini/settings.json when you pass --scope project. You can also run gemini mcp add --transport http meltwater followed by the public URL.

2. Add the HTTP server

On the current Gemini CLI settings page, httpUrl is the Streamable HTTP endpoint. The url field is the SSE endpoint, so do not use url for this server. The default auth provider is dynamic discovery, which matches Meltwater's published OAuth metadata. For a Meltwater API token, pass --header "apikey: ..." and take the token from the environment. Do not commit that header value.

~/.gemini/settings.json

{
  "mcpServers": {
    "meltwater": {
      "httpUrl": "https://api.meltwater.com/v2/mcp"
    }
  }
}

3. Restart the CLI and sign in

Quit the running Gemini CLI session and start it again. If it prompts for Meltwater, complete that sign-in, then ask it to list Meltwater tools.

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.