ouicu
Related Servers
Alternatives to ouicu
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceGive AI agents access to your localhost dev server. Zero-config tunnel that works with Claude Code, OpenClaw, and any MCP-compatible agent. No interstitial pages, no account required.MIT
- FlicenseNot gradedqualityAmaintenanceConnects web-based AI chat clients such as Claude, ChatGPT, and Grok to a local machine through a single OAuth-gated MCP endpoint so they can browse, read, write, and edit files, run whitelisted shell commands, search content, use Git, query SQLite, drive browsers and DevTools, and manage background tasks, ports, and clipboard. It also exposes localhost and LAN services via a protected HTTP client, letting remote or mobile clients debug and operate local projects without granting unrestricted shell access.-
- AlicenseAqualityDmaintenanceConnects AI tools to local dev servers, enabling them to view pages, call APIs, read/edit files, and run commands with safety guardrails.13MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to delegate coding tasks to local Codex or Claude Code CLIs, monitor their progress, read results, continue sessions, and browse the files in user-approved project workspaces. It exposes these capabilities over Streamable HTTP through a Cloudflare tunnel or locally over stdio, so a remote or cloud client can drive agents running on the user's own machine.45 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to access files and terminal of a local computer via a public HTTPS endpoint, secured with GitHub OAuth.-
- FlicenseNot gradedqualityDmaintenanceExposes local OpenCode instances as remote MCP servers for Claude and ChatGPT, enabling terminal access, session management, and interactive human-in-the-loop workflows. It simplifies deployment for local machines using Cloudflare Tunnels to provide secure public connectivity and OAuth support.-
TDQS
Scored across 1 tool
There is only one tool, so there is nothing to confuse it with. Its purpose (authenticate to ouicu before other tools become available) is unmistakable.
The single tool follows the server-prefixed snake_case convention (ouicu_login), which is readable and predictable. No competing conventions exist to create inconsistency.
A server exposing exactly one tool is far too thin for the apparent scope, even allowing for the fact that it is a login gate for other tools that are not described here. The surface gives an agent almost nothing to work with.
Only an authentication step is exposed; no domain operations (read/write/etc.) are available, leaving a severe gap. The description hints other ouicu tools exist after login, but they are not part of the evaluated surface.