Skip to main content
The Remote Yuno MCP Server implements the Model Context Protocol (MCP) to provide secure, remote access to Yuno services. It acts as a hosted proxy so AI agents and automation clients can call Yuno APIs over MCP without running a local process.
Looking for the one-click Claude/ChatGPT connector instead of building your own MCP client? See Use Yuno with Claude and ChatGPT.
Just need an agent to search and read Yuno’s documentation, with no API credentials and no ability to act on your account? See the read-only Documentation MCP instead.

​
Key capabilities

​
Security

  • API key auth: Requires YUNO_PUBLIC_API_KEY, YUNO_PRIVATE_SECRET_KEY, and YUNO_ACCOUNT_CODE
  • Stateless: The server keeps no session, so every request carries its own credentials

​
Protocols

  • Streamable HTTP transport in stateless mode: send requests with POST /mcp. GET and DELETE return 405 Method Not Allowed
  • JSON-RPC 2.0 for standardized request/response

​
When to use the remote server

Use the Remote MCP Server when you want a hosted endpoint with centralized observability instead of running an MCP process on each developer’s machine. Clients still authenticate with the same YUNO_PUBLIC_API_KEY, YUNO_PRIVATE_SECRET_KEY, and YUNO_ACCOUNT_CODE as the local MCP, passed as the public-api-key, private-secret-key, and account-code request headers rather than environment variables. For rapid prototyping on a developer machine, the local MCP (CLI-launched) may be sufficient.

​
Tool arguments

Tool arguments are snake_case. The server rejects an unknown key, including a camelCase spelling, instead of ignoring it. Sending idempotencyKey fails with an error that names the accepted field, idempotency_key. paymentAuthorize places a hold or refuses the call. Card and wallet methods, including Google Pay and Apple Pay, are authorized with capture disabled. A payment method the server cannot hold is refused with UNSUPPORTED_AUTHORIZATION, and nothing is sent upstream as a charge.

​
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): Replace the placeholder header values below with your YUNO_PUBLIC_API_KEY, YUNO_PRIVATE_SECRET_KEY, and YUNO_ACCOUNT_CODE credentials.
To add the server from Claude Code, run:
Your YUNO_PUBLIC_API_KEY, YUNO_PRIVATE_SECRET_KEY, and YUNO_ACCOUNT_CODE can all be obtained from the Yuno dashboard.