SERVER

Studio Signal

Rank #37,737

io.github.vfxprojoe/studio-signal

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

6 versions

by vfxprojoe (1 servers)View repository ↗Claim this server

First listed

Apr 22, 2026

Last publish date

Aug 3, 2026

OVERVIEW

Studio Signal is a Model Context Protocol (MCP) server published by vfxprojoe. It ranks #37,737 of 137,138 servers tracked on MCP Toplist. Studio Signal is listed on Official MCP, with 6 tracked versions. It was first listed on Apr 22, 2026 and most recently updated on Aug 3, 2026.

STANDING

#37,737of 137,138 tracked serversTop 50%

Ranks ahead of 99,401 of 137,138 servers on MCP Toplist.

CONNECT

Use Studio Signal

No setupRuns out of the box

No credentials or required configuration declared — add it to your MCP client and go.

Remote · HTTP

claude mcp add --transport http studio-signal https://studiosignal.app/api/mcp

npm package

claude mcp add studio-signal -e "STUDIO_SIGNAL_API_KEY=<your STUDIO_SIGNAL_API_KEY>" -- npx -y @studiosignal/mcp-server

Replace each placeholder with your own value before saving.

Remote · HTTP

[mcp_servers.studio-signal]
url = "https://studiosignal.app/api/mcp"

Add to ~/.codex/config.toml.

npm package

[mcp_servers.studio-signal]
command = "npx"
args = ["-y", "@studiosignal/mcp-server"]

[mcp_servers.studio-signal.env]
STUDIO_SIGNAL_API_KEY = "<your STUDIO_SIGNAL_API_KEY>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

Remote · HTTP

https://studiosignal.app/api/mcp

Settings → Connectors → “Add custom connector”, then paste this URL.

npm package

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

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

Remote · HTTP

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

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).

npm package

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

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

Remote · HTTP

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

Save as .vscode/mcp.json in your workspace.

npm package

{
  "servers": {
    "studio-signal": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@studiosignal/mcp-server"
      ],
      "env": {
        "STUDIO_SIGNAL_API_KEY": "<your STUDIO_SIGNAL_API_KEY>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

Remote · HTTP

{
  "mcpServers": {
    "studio-signal": {
      "serverUrl": "https://studiosignal.app/api/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

npm package

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

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

Remote · HTTP

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

npm package

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

Replace each placeholder with your own value before saving.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.vfxprojoe%2Fstudio-signal.svg)](https://mcptoplist.com/server/io.github.vfxprojoe%2Fstudio-signal)

HTML

<a href="https://mcptoplist.com/server/io.github.vfxprojoe%2Fstudio-signal"><img src="https://mcptoplist.com/badge/io.github.vfxprojoe%2Fstudio-signal.svg" alt="MCP Toplist: Top 50% of 137,138" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

REGISTRIES

Listed on 1 registry

Official MCP

ORGANIZATION

vfxprojoe

Organization

vfxprojoe

Servers in org

Versions across org

VERSIONS

Available versions (6)

Version	Published
1.4.6	Aug 3, 2026
1.4.5	Jul 7, 2026
1.4.2	Jun 23, 2026
1.4.1	Jun 23, 2026
1.0.7	May 16, 2026
1.0.5	Apr 22, 2026

FAQ

Frequently asked questions

Who maintains Studio Signal?: Studio Signal is maintained by vfxprojoe, which publishes 1 MCP server (6 total versions) tracked on MCP Toplist.
Is Studio Signal listed on the Official MCP Registry?: Yes — Studio Signal is listed on the Official MCP Registry.
How many versions does Studio Signal have?: MCP Toplist tracks 6 versions of Studio Signal, most recently published on Aug 3, 2026.
Where can I find the source code for Studio Signal?: The source code for Studio Signal is hosted at github.com/vfxprojoe/studiosignal.

Used in projects

Do you run this server?

Add to a project

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers