Productivity · Remote MCP server
Sheetrender MCP
Render PDFs from templates and spreadsheet data via SheetRender, locally or at mcp.sheetrender.com.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sheetrender/sheetrender-mcp- Version
- 0.5.3
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- sheetrender (GitHub)
- Repository
- github.com/sheetrender/sheetrender-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.sheetrender.com/mcp | Authorization (required, secret) |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @sheetrender/mcp | 0.5.3 | stdio |
How to connect Sheetrender MCP
Sheetrender MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.sheetrender.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @sheetrender/mcp version 0.5.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @sheetrender/mcp@0.5.3. It reads these environment variables: SHEETRENDER_API_KEY (required, secret) and SHEETRENDER_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"sheetrender-mcp": {
"command": "npx",
"args": [
"-y",
"@sheetrender/mcp@0.5.3"
],
"env": {
"SHEETRENDER_API_KEY": "<secret>",
"SHEETRENDER_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| ServiceAgent CRMSearch CRM contacts, deals, tasks, appointments, calls and workflows with workspace-scoped OAuth. | Remote · HTTP |
| SessionplanCreate and edit visual agendas for workshops, trainings, meetings, and events. | Remote · HTTP |
| SetlineLive festival data for AI agents: lineups, set times, dates, locations and ticket links worldwide. | Remote · HTTP |
| ShakaCompany email for Rwanda. Read and send mail from a Shaka mailbox over OAuth or an API key. | Remote · HTTP |
| SheetspecContract testing and quality gates for spreadsheets created by AI agents. | Local · stdio |
| ShelfmarkLocal, privacy-first document catalogue for AI agents: metadata-only discovery, no cloud, no RAG. | Local · stdio |
| Shiftyasan Shift SchedulingGenerate optimized work shift schedules from staffing demand, availability and fairness rules. | Remote & Local · HTTP, stdio |
| ShikamaruProvably correct day-count, calendar, business-day, and schedule math, verified against QuantLib. | Local · stdio |