AI access on ReDock Web

ReDock Web serves an MCP door at https://app.redock.xyz/mcp. Point Claude, Claude Code, Cursor or any MCP client at it. The first connection lands on a consent page here, which names the workspace and the level being asked for. Approve it and the app appears under Connected apps with the date, the level and a Revoke.

A per-site address, https://app.redock.xyz/mcp/s/<fingerprint>, reaches that one site and nothing else in the workspace. It is on the site’s own AI tab.

The policy

Under Usage policy, seven switches decide what an AI app may do on its own:

1. publish or trash content
2. change what the front page is
3. switch the theme
4. install, remove, update or toggle plugins
5. change site settings
6. run database writes
7. create users or change roles

Switch one off and an AI app is refused it at the door and told to ask a person. It does not stop you: your team still does it from these pages, and so does anything you queue as a job. A single site can be made stricter than the workspace, on its own AI tab. Every refusal is on the Activity page.

API tokens

For a script rather than an app that signs in, mint a token under API tokens, scoped to the workspace or to one site, at the level you choose. It goes through the same door, the same policy and the same records, and it is revoked on the next call.