Prerender MCP server
6 operations0 webhooks
Prerender service API for recaching pages, searching the cache, submitting sitemaps and tuning the render queue.
Try Prerender with your agent
Connect Prerender, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Prerender on my account, then run one read-only example and show me the result.
Prerender tools and triggers
Tools are what your agent can do in Prerender through Corsair's MCP server. Triggers are the Prerender events a routine can start from.
Cache
- ClearDestructive
Delete cached URLs matching a pattern. The clear runs as a job, and only one runs at a time
cache.clear
- Clear StatusRead-only
Read whether a cache clear job is still running: inProgress is true while one runs
cache.clearStatus
- RecacheDestructive
Render and cache one URL, or up to 1000 in one call, so crawlers see current content. Each URL spends one render from the plan, billed past the included amount
cache.recache
- SearchRead-only
Search the cache by substring or exact URL, or list all of it, 200 results per page, optionally filtered by device
cache.search
- SitemapDestructive
Render and cache every URL in a sitemap that is not cached yet, spending one render per new URL. URLs already cached are left as they are
cache.sitemap
Queue
- Change SpeedWrite
Set how many URLs the render queue processes per hour, or restore the automatic delay. A faster rate can overload the origin
queue.changeSpeed
Connect Prerender to Claude, ChatGPT or Cursor
- 1
Connect Prerender in Corsair
Add your Prerender API key once in Corsair. Corsair stores the credential encrypted and makes the Prerender API calls for your agent, so it never goes into a prompt or a config file. Connect Prerender
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Prerender. On a ChatGPT personal plan, connect Prerender here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Prerender's read and write operations run right away and its 3 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/prerender, add the Prerender plugin, and connect with an API key. Then call methods like corsair.prerender.api.cache.clear() from your app. Corsair keeps each tenant isolated.
Yes. Prerender requires an API key from your Prerender account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Prerender, GitHub, Notion, Stripe, and the rest. Trigger Prerender from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for prerender service API for recaching pages, searching the cache, submitting sitemaps and tuning the render queue. Common builds include sync jobs, admin tooling, and agents that call Prerender APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Prerender API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/prerender in the open repo. When Prerender ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Prerender data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Prerender data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Prerender on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 3 destructive Prerender operations. You can change a link's mode at hub.corsair.dev/me.