ReDock + Cursor
Code in Cursor, run on the dock.
Cursor speaks MCP. Point it at ReDock and the agent in your editor can start the site it is editing, tail its logs, query its database and share it, with the permissions you set in ReDock.
Free · works with Cursor as Cursor · official marks, interoperability only What ReDock does with it
Your editor, with a dock.
MCP, no glue One config entry; ReDock shows it to you.
Logs next to code The editor agent reads the site's explained errors while it fixes them.
Same permissions ReDock's per-site fence applies to Cursor exactly as to the built-in agent.
Build it in an afternoon
Fix a bug with the site running
Three steps, one window, receipts for the parts the agent did.
- 01Add ReDock's MCP server to Cursor.
- 02Open the plugin repo; ask Cursor to reproduce the error on https://site.test and read the log.
- 03Let it patch, rebuild, and check the page; receipts land in ReDock's Activity.
Cursor on the blog
MCP Claude Desktop + your local sites: connecting an MCP server that can ship Connect Claude Desktop to a local MCP server at localhost:47200 and it can create, run, author, share, and deploy real websites, no terminal, no API keys. Read → MCP Claude MCP tutorial: build and publish a website by chatting A practical Claude MCP tutorial: connect Claude to ReDock's local MCP server and go from empty Mac to a published website in one conversation. Read → MCP Cursor + MCP: letting your editor's agent run real websites Cursor's agent can call MCP tools. Point it at ReDock on localhost:47200 and it can create, run, author, and deploy real local sites, without leaving the editor. Read → MCP Easy MCP setup: zero config, no terminal, no JSON files Easy MCP setup means pointing a client at a running server, no JSON editing, no terminal. ReDock exposes its whole surface at localhost:47200. Read →
Calm ships tonight.
Download ReDock, berth your first site, and watch the AI work, receipts and all. Five minutes, no terminal.
Free · macOS and Windows · your sites stay on your machine