About Uno MCP Stdio
Uno MCP Stdio is an MCP server published by agentrix-ai in the Security category: uno MCP Stdio Client - Local stdio proxy for Uno MCP Gateway with OAuth authentication.
The repository has 1 stars and 0 forks, with the last commit 6 days ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/agentrix-ai/uno-mcp-stdioThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Uno MCP Stdio
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- ✓Tests presentA test suite exists in the repository.
- !Dependencies pinnedNo lockfile. Installs can pull different code over time.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Uno MCP Stdio
Local stdio proxy for Uno MCP Gateway - Provides local proxy for MCP clients that don't support OAuth authentication.
🎯 Problem Solved
Many MCP clients (such as Manus, Cherry Studio) don't support OAuth 2.0 authentication and cannot directly connect to MCP servers that require authentication.
uno-mcp-stdio acts as a local proxy:
- Communicates with MCP clients using stdio mode (supported by all clients)
- Securely stores OAuth tokens locally
- Proxies requests to remote Uno Gateway, automatically attaching authentication information
┌─────────────────┐ stdio ┌─────────────────┐ HTTPS ┌─────────────────┐
│ MCP Client │ ◄────────────► │ uno-mcp-stdio │ ◄────────────► │ Uno Gateway │
│ (No OAuth) │ │ (Local Proxy) │ + Bearer │ (Remote) │
└─────────────────┘ └─────────────────┘ └─────────────────┘
🚀 Quick Start
Installation
# Run directly with uvx (recommended)
uvx uno-mcp-stdio
# Or install with pip
pip install uno-mcp-stdio
uno-mcp-stdio
First Run
OAuth authentication is required on first run:
$ uvx uno-mcp-stdio
🔐 Authentication required
📋 Please open the following link in your browser to complete authentication:
https://mcpmarket.cn/oauth/authorize?...
⏳ Waiting for authentication...
✅ Authentication successful! Token saved
🚀 Uno MCP Stdio is ready
Configure MCP Client
Configure stdio server in your MCP client:
Manus / Cherry Studio Configuration Example:
{
"mcpServers": {
"uno": {
"command": "uvx",
"args": ["uno-mcp-stdio"]
}
}
}
If installed with pip:
{
"mcpServers": {
"uno": {
"command": "uno-mcp-stdio"
}
}
}
⚙️ Configuration
Environment Variables
| Variable | Description | Default |
|---|---|---|
UNO_GATEWAY_URL |
Uno Gateway URL | https://uno.mcpmarket.cn/mcp |
UNO_CREDENTIALS_PATH |
Token storage path | ~/.uno-mcp/credentials.json |
UNO_DEBUG |
Debug mode | false |
Token Storage
Authenticated tokens are stored in ~/.uno-mcp/credentials.json:
{
"access_token": "xxx",
"refresh_token": "xxx",
"expires_at": 1736345678,
"token_type": "Bearer"
}
Clear Authentication
# Delete token file to re-authenticate
rm ~/.uno-mcp/credentials.json
🔐 Authentication Flow
1. Start uno-mcp-stdio
│
▼
2. Check ~/.uno-mcp/credentials.json
│
├─ Valid token → Proxy requests directly
│
└─ No/expired token → Start authentication flow
│
▼
3. Start temporary HTTP server (localhost:random port)
│
▼
4. Generate OAuth URL, display to user
│
▼
5. User completes authorization in browser
│
▼
6. MCPMarket callback to local server
│
▼
7. Exchange token, save to file
│
▼
8. Close temporary server, start proxying
🛠️ Development
# Clone repository
git clone https://github.com/agentrix-ai/uno-mcp-stdio.git
cd uno-mcp-stdio
# Install dependencies
uv sync
# Run
uv run uno-mcp-stdio
# Debug mode
UNO_DEBUG=true uv run uno-mcp-stdio
📄 License
MIT
🌐 Languages
README fetched from the repository 3 days ago. The original is authoritative.