Skip to main content

MCP Server

The Media Intelligence MCP server lets AI assistants and other Model Context Protocol (MCP) clients search media coverage directly in a conversation, without writing any code against the REST API. It exposes the same Media Intelligence API functionality used by direct API integrations, so an assistant can detect trends, monitor reputation, and surface sentiment across news, broadcast, and social coverage as part of a conversation.

Server URL​

https://apigateway.agilitypr.com/api/mcp

The server implements the Streamable HTTP transport from the MCP spec (single POST /api/mcp endpoint, no separate SSE endpoint). Configure your client with this URL as an HTTP MCP server.

Authentication​

The MCP server accepts two forms of authentication:

  • OAuth — the client redirects you to your Agility account login (single sign-on) and authorizes access on your behalf. This flow is only supported for Claude.ai and Claude Code; see Claude Integration for the full walkthrough with screenshots.
  • API key — for MCP clients that don't support an OAuth connection flow, authenticate with an API key the same way you would against the REST API: provision one following Quick Start, then supply it via the apiKey header when configuring the client's connection to this server.

Either way, the server only ever acts within the permissions of the Agility account (OAuth) or API key used to connect — an MCP client can't see or search more than that account is provisioned for.

note

Access to social media coverage (e.g. X/Twitter, Reddit, YouTube) depends on your account's provisioning, regardless of which auth method you use. If social mentions aren't returned as expected, check with your Agility representative.

Available tools​

Today the server exposes a single tool:

ToolDescription
Agility Media Mention Search (ad_hoc_search)Mirrors the ad-hoc search endpoint. Searches news, broadcast, blog, press release, and social coverage for a brand, person, or topic, with boolean query logic, media type, date range, and sentiment filters.

The tool's search field uses the same Expert Search syntax as the REST API — an assistant using this tool builds boolean queries following those same rules.

Connecting your client​

  • Claude.ai or Claude Code — follow Claude Integration for step-by-step setup.
  • Other MCP clients — point the client at the server URL above and authenticate with an API key via the apiKey header (see Authentication). Consult your client's documentation for how it takes an MCP server URL and request headers; the connection and tool-calling behavior from there follows the standard MCP client/server flow.

Learn more​