MCPENROUZa PENROUZ product
RU
MCPENROUZ · Cursor

MCPENROUZ in Cursor

One JSON configuration for a project or all workspaces. Add the server and complete authorization.

Start setupConfiguration files
MCP server URL
https://mcp.penrouz.com/mcp

Set up the server in Cursor

First install MCPENROUZ on your device, sign in with PENROUZ ID and choose a folder with read access. Keep the device online, then connect your AI to the same account below.

  1. Choose the configuration scope

    For all projects, open ~/.cursor/mcp.json. For one project, use .cursor/mcp.json inside that project. Create the file if it does not exist.

  2. Add the MCPENROUZ entry

    Copy the configuration below or download the template. Merge the server entry into your existing mcpServers object.

  3. Authorize the connection

    Open Customize → MCPs, enable the server and follow the PENROUZ ID sign-in prompt. Enable the required tools for the agent and check your device list.

Ready-to-use JSON

.cursor/mcp.json
{
  "mcpServers": {
    "mcpenrouz": {
      "url": "https://mcp.penrouz.com/mcp"
    }
  }
}
Download cursor.mcp.json

If the file exists, merge only the mcpenrouz entry and keep your other servers and settings. ~ means your user home folder.

Cursor supports remote HTTP and OAuth with dynamic client registration. A cloud agent may need its own sign-in. Organization allowlists can limit access to custom servers.

Check the connection

Enable MCPENROUZ tools in your AI client and send this request. It asks for device and folder lists without changing files.

First request · read only
Show my available MCPENROUZ devices and their status. Then list the folders I can read on the device I select.

Signing in is the first stage. The connection is ready when your AI can see your device and complete an allowed request. Review clients and access in the dashboard.

If setup is incomplete

Signed in, but no devices appear

Check that the device app is running, the device is confirmed and the AI client uses the same PENROUZ ID. Open Devices and AI clients in the dashboard.

The configuration file is not recognized

Check the path, filename and format for your client. VS Code Local uses servers, Copilot uses mcpServers, and Gemini CLI uses httpUrl. Attaching JSON to an ordinary chat message does not install a connection.

OAuth or adding a server is unavailable

Update the client and sign in again from its MCP settings. In a managed workspace, check access with your administrator. Plan, browser and environment requirements depend on the client.

More connection troubleshooting

Official sources