Remote Yuno MCP Server

The Remote Yuno MCP Server implements the Model Context Protocol (MCP) to provide secure, remote access to Yuno services. It acts as a hardened proxy so AI agents and automation clients can call Yuno APIs over MCP with enterprise‑grade security and session controls.

Key capabilities

Security

API key auth: Requires YUNO_PUBLIC_API_KEY, YUNO_PRIVATE_SECRET_KEY, and YUNO_ACCOUNT_CODE
IP validation: Sessions are bound to client IPs
Rate limiting: 15 requests per minute per session
Session timeouts: 30 minutes idle; 6 hours absolute

Protocols

Streamable HTTP transport for bidirectional communication
JSON‑RPC 2.0 for standardized request/response

Session management

Automatic creation, refresh, and cleanup
Scheduled cleanup every 5 minutes
Redis backend for persistent session and rate‑limit storage

When to use the remote server

Use the Remote MCP Server when you want centralized security, observability, and policy enforcement (IP binding, rate limits, TTLs), or when teams and tools should connect without distributing raw API credentials locally. For rapid prototyping on a developer machine, the local MCP (CLI‑launched) may be sufficient.

Connecting from MCP‑compatible clients

The Remote MCP Server exposes an HTTP transport endpoint. Configure your MCP client to connect to your provisioned URL and pass the required headers.

Sample configuration (HTTP transport):

{
  "mcpServers": {
    "Yuno": {
      "transport": "http",
      "url": "https://prod.y.uno/yuno-mcp/mcp",
      "headers": {
        "public-api-key": "<YOUR_PUBLIC_API_KEY>",
        "private-secret-key": "<YOUR_PRIVATE_SECRET_KEY>",
        "account-code": "<YOUR_ACCOUNT_CODE>"
      }
    }
  }
}

📘
Your PUBLIC_API_KEY, PRIVATE_SECRET_KEY, and ACCOUNT_CODE can all be obtained from the Yuno dashboard.

Related information

For local development and how MCP maps Yuno API endpoints into tools, see Building AI Integrations with Yuno's LLMs and MCP.