Stdio: a program
Configuration accepts a command and arguments.
Guides · MCPENROUZ
MCP stdio and HTTP: which connection should you use?
Stdio starts a local program. Streamable HTTP connects to a server URL. Use HTTP MCP with OAuth for MCPENROUZ.
Free2 devices · 100 tool calls per hour
Example task
URL = https://mcp.penrouz.com/mcp Transport = Streamable HTTP Auth = OAuth
Your device · your permissions
HTTP: a URL
Configuration accepts a server address.
OAuth
Check authorization support separately.
Get started
Check the client
Look for remote MCP and Streamable HTTP support.
Add the URL
Connect directly when HTTP and OAuth are available.
Assess a bridge
For stdio, use a bridge with HTTP and OAuth. Review its documentation and session storage.
Example task
A prompt for your AI
URL = https://mcp.penrouz.com/mcp Transport = Streamable HTTP Auth = OAuth
Permissions
Do not put a URL in a command field or replace OAuth with a device token.
Details
Two setup steps
The agent connects the device to the service. MCP configuration gives the AI client service tools. These steps do not replace each other.
Client format
Use your client’s example. Cursor and VS Code have different JSON root keys, while Codex uses TOML. Check the format before copying.
Frequently asked questions
Why is there no URL field?
The client may be stdio-only. Check its transport documentation.
Does everyone need a bridge?
No. HTTP MCP clients with OAuth connect directly.
Can I copy another JSON config?
Check the format: VS Code uses servers, Cursor uses mcpServers.
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.