Guides · MCPENROUZ

Remote MCP over Streamable HTTP

The client uses the public HTTPS /mcp address with Streamable HTTP. The address is shared by your devices.

Free2 devices · 100 tool calls per hour
Example task
Name: MCPENROUZ
Transport: Streamable HTTP
URL: https://mcp.penrouz.com/mcp
Authentication: OAuth
Your device · your permissions
01

Server by URL

Use a service address rather than an executable path.

02

Client OAuth

Authorize the application for your account.

03

Device selection

Select the machine in a tool call.

Get started

  1. Check the transport

    Look for remote MCP or Streamable HTTP in the client documentation.

  2. Enter the exact URL

    Use https://mcp.penrouz.com/mcp, including /mcp. The homepage is not the tool endpoint.

  3. Complete OAuth

    After sign-in, check tools and request devices.

Official client or protocol documentation ↗

Example task

A prompt for your AI
Name: MCPENROUZ
Transport: Streamable HTTP
URL: https://mcp.penrouz.com/mcp
Authentication: OAuth

Permissions

An ordinary browser without authorization can receive 401 at /mcp. This is expected tool protection.

Details

Two connections

The AI client connects to the cloud address. Your local agent establishes its own outbound HTTPS connection without opening an inbound MCP port.

Correct mode

Choose HTTP/Streamable HTTP for this endpoint. Stdio needs a different configuration and a compatible bridge.

Frequently asked questions

Does each machine need a URL?

No. OAuth maps one URL to your account; the tool selects the device.

Why do I get 401?

Complete OAuth sign-in in the client.

Can I choose SSE?

This guide targets Streamable HTTP. Check server and client support before changing transports.

Next steps

MCPENROUZ · FREE

Connect a device. Start with reads.

Choose a working folder and AI client. Add writes and terminal access as your task requires.