AI agents are becoming full members of marketing, sales, and support teams. With the KWatch.io MCP server, your agents get first-class access to social listening: they can create keyword alerts, track conversations, and manage your whole monitoring setup on Reddit, LinkedIn, Hacker News, X, Youtube, and Facebook, using plain language instructions.
The Model Context Protocol is an open standard that connects AI assistants and agents to external tools and data sources. It is often described as the USB-C of AI: instead of writing a custom integration for every assistant, a platform exposes one MCP server, and every MCP-compatible client can use it out of the box.
KWatch.io hosts a remote MCP server, so there is nothing to install and nothing to deploy. Claude, Claude Code, Cursor, VS Code, and any other MCP-compatible client can connect to it in one minute with a KWatch API key.
Once connected, your agent can use the same capabilities as our REST API, with the same permissions and team roles:
The mentions found by KWatch.io are then delivered through your existing notification channels: email, Slack, and API webhooks. Learn more about our API webhooks.
Our MCP server uses the standard Streamable HTTP transport and is authenticated with your KWatch API key:
https://api.kwatch.io/mcp
For example, here is how you connect Claude Code to KWatch.io:
claude mcp add --transport http kwatch https://api.kwatch.io/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
Here is how it works:
The detailed setup for Claude, Cursor, VS Code, and other clients, along with the full list of available tools, is in our documentation. Check the MCP server documentation.
Any client that supports the Model Context Protocol over Streamable HTTP: Claude, Claude Code, Cursor, VS Code, and the agents you build yourself with frameworks like the OpenAI Agents SDK or the Claude Agent SDK. Clients that only support local MCP servers can connect through the standard mcp-remote bridge.
Agents authenticate with a KWatch API key sent as a bearer token, the same keys as our REST API. You can create and revoke API keys at any time from your dashboard, in the API section.
Yes. The MCP server enforces exactly the same rules as our API and dashboard: team roles and permissions, plan limits, and input validation. All traffic is encrypted with TLS, and revoking the API key instantly cuts the agent's access.
The MCP server is used to set up and manage your monitoring. The mentions themselves are delivered in real time through your notification channels: email, Slack, and API webhooks. Pointing an API webhook at your own system is the best way to feed mentions to an automated pipeline.
The MCP server is available on every plan that includes API access, like the Business and Enterprise plans.
No. The MCP server is fully hosted by KWatch.io at https://api.kwatch.io/mcp. You only need an API key and an MCP-compatible client.