📡 Studio Signal MCP Server

Give your AI agent real-time media & entertainment intelligence. Ask Claude, ChatGPT, Cursor, or any MCP-compatible assistant to research any M&E company — earnings, streaming wars, box office, M&A, production trends, executive moves, and more. Every response is grounded in real, verified sources from across the industry.

Studio Signal is the M&E intelligence platform used by media executives and analysts. This MCP server connects that intelligence directly to your AI workflow. Research any company, any topic — powered by live ground truth, not a static dataset.

⚡ Quick Install (npx)

No cloning required — run directly from npm:

{
  "mcpServers": {
    "studio-signal": {
      "command": "npx",
      "args": ["-y", "@studiosignal/mcp-server"],
      "env": {
        "STUDIO_SIGNAL_API_KEY": "ss_live_your_key_here"
      }
    }
  }
}

Get your API key free at developer.studiosignal.app → Profile → API Key.

🛠 Tools (5)

Research & Intelligence

| Tool | What it does | |-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ask_kai | Ask Kai Rivers (AI research analyst) any M&E question — competitive analysis, earnings breakdowns, deal impact, market trends. Returns sourced, citation-backed research. | | get_daily_brief | Today's executive intelligence brief — top stories ranked by impact, market movers, and strategic implications. Updated every morning. | | get_deep_dive | In-depth analysis expanding on the day's most significant story. Full market context and strategic recommendations. | | get_stocks | Live M&E sector stock data — prices, changes, market caps, and analyst ratings for 30+ media & entertainment companies. Filter by symbol or get all. |

Note: For PDF reports, Excel models, infographics, and slide decks, simply ask Claude to convert Kai's research output — it handles these natively.

Account

| Tool | What it does | |-------------|-----------------------------------------------------------------------------------------------| | get_usage | Check your API usage stats for the current billing period — queries used, tier, and estimated cost. |

💡 Example Prompts

Once connected, just ask naturally:

Research

• "Use Studio Signal to analyze Netflix's Q1 2026 earnings"
• "Ask Kai about the impact of AI on Hollywood production pipelines"
• "What's the competitive landscape between Disney+ and Max?"
• "Analyze the Warner Bros Discovery restructuring"

Daily Intelligence

• "Get today's M&E daily brief from Studio Signal"
• "What does the Studio Signal deep dive say today?"

Market Data

• "Get M&E stock data from Studio Signal"
• "What are the stock prices for NFLX, DIS, and CMCSA today?"

Exports & Deliverables

• "Turn that Netflix analysis into a PDF" (Claude handles this natively)
• "Create a slide deck from that earnings breakdown" (Claude handles this natively)

Usage

• "Check my Studio Signal API usage"

🔧 Setup by Client

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "studio-signal": {
      "command": "npx",
      "args": ["-y", "@studiosignal/mcp-server"],
      "env": {
        "STUDIO_SIGNAL_API_KEY": "ss_live_your_key_here"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "studio-signal": {
      "command": "npx",
      "args": ["-y", "@studiosignal/mcp-server"],
      "env": {
        "STUDIO_SIGNAL_API_KEY": "ss_live_your_key_here"
      }
    }
  }
}

Windsurf / Other MCP Clients

Same pattern — point command to npx with args ["-y", "@studiosignal/mcp-server"] and provide your API key in env.

⚠️ If your config file already has content, merge the studio-signal entry into the existing mcpServers object. Don't create a duplicate JSON root.

🧪 Testing & Debugging

Use the MCP Inspector to verify your setup:

npx @modelcontextprotocol/inspector npx -y @studiosignal/mcp-server

🔑 Environment Variables

| Variable | Required | Description | |-------------------------|----------|------------------------------------------------------------------------------------| | STUDIO_SIGNAL_API_KEY | Yes | Your API key from developer.studiosignal.app | | STUDIO_SIGNAL_URL | No | API base URL (defaults to https://studiosignal.app) |

📊 API Pricing

The MCP server uses API key authentication with metered billing — completely separate from in-app subscriptions. All tools consume API calls equally.

Free Trial (No credit card required)

• 50 API calls across all tools — research, briefs, stocks, everything
• 7-day trial window
• Full access to all 6 tools during trial

Pay-as-you-go (After trial)

Activate metered billing to continue using the API with no hard caps:

| Volume | Rate per call | |------------------|---------------| | First 1,000 | $0.15 | | 1,001 – 10,000 | $0.10 | | 10,001+ | $0.07 |

• Track usage anytime with the get_usage tool
• Manage billing at developer.studiosignal.app

Data Coverage

• Any M&E company — from the major studios (Netflix, Disney, WBD, Comcast, Paramount) to independents, streamers, agencies, VFX houses, ad-tech, gaming, and live entertainment
• Ground truth sources — every research response is backed by real, verified sources pulled live from across the industry
• Deep research on earnings, M&A, streaming metrics, box office, production pipelines, executive moves, regulatory shifts, and more
• Daily intelligence briefings updated every morning before market open

🔗 Links

• Platform: studiosignal.app
• Developer Portal: developer.studiosignal.app
• REST API: Endpoints for research, content generation, and market data
• npm: @studiosignal/mcp-server

🔒 Privacy Policy

Studio Signal respects your privacy:

• Data collected: Query text is sent to Studio Signal's API for processing. No personal data beyond your API key and query content is transmitted.
• Data usage: Queries are processed by Google's Gemini AI to generate research reports. Query logs are retained for usage analytics and product improvement.
• Data storage: API keys and usage logs are stored in encrypted PostgreSQL databases hosted on Neon (AWS US-East). No query data is sold or shared with third parties for advertising.
• Data sharing: Query content is sent to Google Cloud's Gemini API for AI processing. Google does not retain prompt data beyond the API request duration.
• Data retention: Usage logs are retained for up to 12 months. Users may request deletion by contacting [email protected].
• Full policy: studiosignal.app/legal

📄 License

MIT — © Harkins Capital, LLC