Studio Signal

io.github.vfxprojoePublished by GitHub account vfxprojoev1.4.6Updated Oct 24, 2026

AI-powered media & entertainment intelligence — research, briefs, and market data.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Studio Signal gives an assistant AI-powered media and entertainment intelligence for research, briefs, and market data.

What you can do
Studio Signal is a media and entertainment intelligence service exposed to an assistant through MCP. According to its description, it supports research, briefs, and market data in that domain. The manifest lists no individual tools, so the exact operations are not documented here. It can be reached as a remote endpoint or run locally as an npm package over stdio.
When to use it
Consider it when you want an assistant to help with media and entertainment research, draft briefs, or pull market data in that sector. It is less relevant if your work falls outside media and entertainment.
Requirements
Either the remote endpoint or the local npm package @studiosignal/mcp-server (stdio), which needs Node.js. Authentication is required via OAuth, and the local setup also uses the STUDIO_SIGNAL_API_KEY environment variable, which the provider says can be obtained free at its developer site. Network access is needed for the remote endpoint.
Before you install
An API key (STUDIO_SIGNAL_API_KEY) and OAuth sign-in are required, so treat the key as a secret and check what the OAuth grant authorizes. The manifest does not list tools, so what the server can read or change is not documented; review that before use. Requests go to a third-party service.

Installation

In SourceWeft

  1. Open Studio Signal in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vfxprojoe%2Fstudio-signal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "studio-signal": {
      "type": "http",
      "url": "https://studiosignal.app/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.4.6LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.