Easy MCP setup: zero config, no terminal, no JSON files

Easy MCP setup means you point an AI client at a server that is already running and start working — no config files to hand-edit, no terminal commands, no JSON to get wrong. The server exposes its tools; the client discovers them; you go. ReDock takes that shape: install the app, and its whole surface is served as MCP tools at localhost:47200 for any client to connect to.

Most MCP friction comes from setup, not from the protocol itself. If you’ve stared at a config file wondering which key goes where, this is the version without that step.

Why MCP setup gets hard

The Model Context Protocol is simple on the wire. The pain is usually in one of three places:

• Hand-edited config. Many servers expect you to write a JSON block naming a command, its arguments, and its environment. One misplaced comma and nothing loads.
• stdio subprocesses. When a client launches the server as a child process, you’re responsible for the command line, the working directory, and the environment it inherits.
• No feedback. If the server fails to start, you often get silence, not a reason.

None of this is inherent to MCP. It’s what happens when the server is a script you’re expected to wire up yourself. A running application with an HTTP endpoint sidesteps all three. If you want the wire-level picture, MCP over HTTP explained walks through it.

The zero-config path

ReDock is a native macOS app (macOS 12+, built on Tauri and Rust — not Electron). It runs your local sites — WordPress, headless WordPress, Astro, Next.js, Node, Bun, PHP, MySQL — each at https://name.test with a locally trusted certificate, no terminal involved.

Because the app is already running, its MCP server is too. There’s nothing to spawn. The setup is:

1. Install ReDock and open it.
2. In your AI client, add an HTTP MCP server pointing at localhost:47200.
3. Connect. The client lists the tools and you’re working.

No command string, no arguments, no environment variables. The install guide covers the app side, and your first site gets a real site running in a few clicks.

One endpoint, every client

Because ReDock listens on an HTTP port instead of being spawned per-client, more than one client can connect to the same server at once. Claude Desktop, Claude Code, and Cursor can all point at localhost:47200 and see the same sites, the same tools, the same state. Configure once, use everywhere.

That’s a practical difference for day-to-day work. You can be authoring WordPress content from Claude Desktop while your editor’s agent runs the same site’s dev server, and neither had to launch its own copy of anything. For a client-by-client walkthrough, see Claude Desktop + your local sites and Cursor + MCP.

What “connected” actually gets you

Setup is the boring part; the point is what the tools do. Once connected, an agent can create sites, start and stop them, author WordPress through real Gutenberg blocks and patterns, magic-login to wp-admin, share a site over a Cloudflare tunnel, and deploy to Cloudflare Workers. The full tools list covers the surface, and the MCP docs document each verb.

One habit makes this trustworthy: ReDock reports honest state. When a tool says a site is running, that comes from the real process, not from “we sent the start command.” For an agent recovering from a hiccup, that’s the difference between fixing a problem and inventing one.

ReDock is free, and there are no API keys to manage — the built-in agent and local-LLM catalog run on your machine.

FAQ

Do I need to edit a JSON config file to use ReDock’s MCP server?

No. The server runs with the app. You point your client at localhost:47200 in the client’s own settings — there’s no ReDock config file to hand-edit.

Do I need the terminal at any point?

No. ReDock runs sites, certificates, and the MCP server without a terminal. Everything is driven from the app or through the MCP tools.

Can more than one AI client connect at the same time?

Yes. Because the server listens on an HTTP port, Claude Desktop, Claude Code, and Cursor can all connect to the same endpoint concurrently and share state.

ReDock gives your agents a full local web stack behind one endpoint, with nothing to configure — download ReDock.