mcpbeat

Studio MCP Server

net.reogrid/studio
answering

Studio is answering right now. Last checked 11 min ago. It exposes 4 tools.

Turn analyzed data into a real Excel-like spreadsheet at a shareable URL: cells, formulas, tables.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
1154 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add studio --transport http https://api-studio.reogrid.net/studio/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "studio": {
      "url": "https://api-studio.reogrid.net/studio/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.studio]
url = "https://api-studio.reogrid.net/studio/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "studio": {
      "url": "https://api-studio.reogrid.net/studio/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "studio": {
      "url": "https://api-studio.reogrid.net/studio/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

feature
get_feature_spec
Returns the full schema fragment for one advanced feature listed in get_schema().features.
publish
publish_sheet
Publishes a ReoGridJsonDocument and returns a public URL. Anonymous; rate-limited per IP. No expiry in Phase 1. The doc must conform to the schema returned by get_schema().
schema
get_schema
Returns the base ReoGridJsonDocument schema (envelope + cells, styles, borders, merges) and an index of advanced features. Call get_feature_spec(feature) for any feature in the index before populating it.
sheet
get_sheet
Fetches a previously published sheet by its short ID.

Endpoints

URLTransportStateLatencyChecked
https://api-studio.reogrid.net/studio/mcp streamable-http answering 1165 ms 11 min ago

Studio — questions

Answers built from our own checks of this server.

What can Studio do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_feature_spec, get_schema, get_sheet, publish_sheet. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Studio working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1154 ms. The bar chart above shows every period we have measured.
How do I connect Studio?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Studio need an API key?
No. Studio completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Studio?
It answers our handshake in 1154 ms on average, which is faster than 3% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.