Skip to main content

Connect Microsoft Copilot to Meltwater MCP

Add Meltwater as an MCP tool inside a Copilot Studio agent. 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.
  • Access to Copilot Studio for the environment where the agent runs.

Connect​

1. Open the MCP wizard​

Microsoft documents two places. In the current agent experience, open the agent, select the Build tab, then Tools, then Add, then Model Context Protocol. In the earlier wizard, open Tools, Add a tool, New tool, then Model Context Protocol. Both ask for a name, a description, and a server URL.

2. Choose OAuth or an API key​

Authentication choices include None, API key, and OAuth 2.0. None does not work: this server returns 401 with no bearer token. For a browser sign-in, choose OAuth 2.0 and Dynamic discovery. Meltwater publishes protected-resource metadata and a registration endpoint. For a Meltwater API token, choose API key, set the header name to apikey, and have the maker supply the token. Do not invent a client id, and do not put the token in the agent URL.

Server URL
https://api.meltwater.com/v2/mcp

3. Publish and test​

Save the tool, publish the agent if your environment requires it, and start a test chat. Ask the agent to list Meltwater tools before you ask it to research a brand.

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.