mcpbeat Sign in

screenRIG MCP Server

by screenrig Your server? Claim it
answering

screenRIG is answering right now. Last checked 2 min ago.

Manage screenRIG screens, playlists, media, schedules, webhooks, and reports through MCP.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
486 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check screenRIG every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add screenrig --transport http https://api.screenrig.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.screenrig.ai/mcp
~/.codex/config.toml
[mcp_servers.screenrig]
url = "https://api.screenrig.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "screenrig": {
      "url": "https://api.screenrig.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "screenrig": {
      "type": "http",
      "url": "https://api.screenrig.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.screenrig.ai/mcp streamable-http sign-in 422 ms 2 min ago

Alternatives to screenRIG

same job, measured the same way
Paddle
by paddle

Query and manage Paddle Billing: pricing, subscriptions, payments, revenue reports and webhooks.

answering
Timesheet
by timesheetio

timesheet.io MCP server - manage timers, projects, tasks and reports

36 installs/wk answering
Google AdSense
by sirmacke

Read AdSense Management API v2 accounts, inventory, payments, policy, and reports through MCP.

19 installs/wk local only
Bitbucket
by mcparmory

Manage repositories, branches, webhooks, and pull requests in Bitbucket workspaces

291 installs/wk local only
Techpool
by techpool

Field service management: missions, schedule, field work reports, clients and timesheets.

answering
Beadhive
by beadhive

Manage cross-repository beads work, hive status, and Beadhive workflows through bh-mcp.

7 120 installs/wk local only
Mailchimp MCP Server
by cyanheads

Mailchimp via MCP: draft, test, and send campaigns; manage audiences and subscribers; pull reports.

115 installs/wk local only
Spacefast
by spacefast

Build, publish, and manage websites, dashboards, reports, and web tools with Spacefast.

answering

screenRIG — questions

Answers built from our own checks of this server.

Why is there no tool list for screenRIG?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is screenRIG working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 486 ms. The bar chart above shows every period we have measured.
How do I connect screenRIG?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to screenRIG?
No API key is involved. screenRIG answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is screenRIG?
It answers our handshake in 486 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.