What is rocketblue MCP?
rocketblue exposes an MCP (Model Context Protocol) server so AI assistants — such as Cursor, Claude Desktop, or other MCP-compatible clients — can read and manage your organization’s rocketblue data using natural language. MCP wraps the same organization API you use for HTTP integrations. Your API key, rate limits, and permissions are identical whether you call REST endpoints directly or invoke MCP tools.Connect a client
Set up Cursor, Claude Desktop, or another MCP client.
Use cases
Practical AI visibility automation workflows.
Tools reference
Full list of MCP tools and what each one does.
Best practices
How agents should work with prompts, quotas, and scheduling.
Prerequisites
- API access enabled — MCP is available when API access is enabled for your organization. In the rocketblue app, go to Settings → API and turn on the API.
- API key — Copy your key from Settings → API. MCP uses the same key as REST calls.
- MCP endpoint — Find your MCP URL under Settings → MCP. The default is:
MCP is currently in closed beta. If you do not see the API or MCP tabs in Settings, contact your rocketblue account team to request access.
What you can do with MCP
See MCP use cases for end-to-end automation recipes (weekly digests, competitor watches, content pipelines, and more).
How MCP relates to the REST API
Each MCP tool maps to one or more REST endpoints underhttps://app.rocketblue.ai/api. For example, list_brands calls GET /v1/brands, and get_run_stats calls GET /v1/runs/{runId}/stats.
Agents should call get_organization_context once per session and get_brand_context before working with a specific brand. See Best practices for the recommended workflow.
Transport and protocol
- Transport: HTTP (streamable HTTP MCP)
- Authentication:
x-spotlight-api-keyheader (same as the REST API) - Scope: One API key = one organization; all tools are scoped to that organization

