Skip to main content
hc
Submit
mcpSource-backed
Unla logo

Unla MCP Gateway

Lightweight Go MCP gateway that turns existing MCP servers and REST APIs into managed SSE or Streamable HTTP MCP endpoints through configuration.

by AmoyLab · submitted by oktofeesh1·added 2026-06-05·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/unla-mcp-gateway
Source URLs
https://docs.unla.amoylab.com, https://github.com/AmoyLab/Unla
Brand
Unla
Brand domain
docs.unla.amoylab.com
Brand asset source
brandfetch
Safety notes
Unla can expose existing MCP servers and REST APIs as new MCP endpoints, so the final tool surface depends on every imported config., Generated endpoints may proxy read/write API operations; review tool descriptions and permissions before connecting an autonomous agent., The upstream README notes that Unla is under rapid development and that documentation can lag behind implementation., Replace default admin credentials and secrets before exposing the management UI or gateway outside a trusted development network., Hot-loaded gateway configuration, multi-tenant routing, OAuth pre-authentication, and management UI access should be governed like production API infrastructure.
Privacy notes
Unla may receive prompts, tool names, tool arguments, REST API parameters, upstream MCP responses, generated endpoint metadata, logs, admin credentials, JWT secrets, OAuth tokens, and configuration history., Imported REST API and MCP server configs can include private upstream URLs, headers, tokens, tenant identifiers, and service credentials., Persisted config backends and container logs may retain sensitive endpoint definitions and operational metadata., Do not commit real gateway configs, API credentials, admin passwords, JWT secrets, OAuth client secrets, or exported tenant data.
Author
AmoyLab
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

25 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

2 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Includes a review or approval gate.

0/5 ready
Install & runtime1Network & hosting1Review & approval2General125 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.

4 areas
  • SafetyNetwork accessUnla can expose existing MCP servers and REST APIs as new MCP endpoints, so the final tool surface depends on every imported config.
  • SafetyPermissions & scopesGenerated endpoints may proxy read/write API operations; review tool descriptions and permissions before connecting an autonomous agent.
  • SafetyGeneralThe upstream README notes that Unla is under rapid development and that documentation can lag behind implementation.
  • SafetyCredentials & tokensReplace default admin credentials and secrets before exposing the management UI or gateway outside a trusted development network.
  • SafetyCredentials & tokensHot-loaded gateway configuration, multi-tenant routing, OAuth pre-authentication, and management UI access should be governed like production API infrastructure.
  • PrivacyCredentials & tokensUnla may receive prompts, tool names, tool arguments, REST API parameters, upstream MCP responses, generated endpoint metadata, logs, admin credentials, JWT secrets, OAuth tokens, and configuration history.
  • PrivacyCredentials & tokensImported REST API and MCP server configs can include private upstream URLs, headers, tokens, tenant identifiers, and service credentials.
  • PrivacyNetwork accessPersisted config backends and container logs may retain sensitive endpoint definitions and operational metadata.
  • PrivacyCredentials & tokensDo not commit real gateway configs, API credentials, admin passwords, JWT secrets, OAuth client secrets, or exported tenant data.

Safety notes

  • Unla can expose existing MCP servers and REST APIs as new MCP endpoints, so the final tool surface depends on every imported config.
  • Generated endpoints may proxy read/write API operations; review tool descriptions and permissions before connecting an autonomous agent.
  • The upstream README notes that Unla is under rapid development and that documentation can lag behind implementation.
  • Replace default admin credentials and secrets before exposing the management UI or gateway outside a trusted development network.
  • Hot-loaded gateway configuration, multi-tenant routing, OAuth pre-authentication, and management UI access should be governed like production API infrastructure.

Privacy notes

  • Unla may receive prompts, tool names, tool arguments, REST API parameters, upstream MCP responses, generated endpoint metadata, logs, admin credentials, JWT secrets, OAuth tokens, and configuration history.
  • Imported REST API and MCP server configs can include private upstream URLs, headers, tokens, tenant identifiers, and service credentials.
  • Persisted config backends and container logs may retain sensitive endpoint definitions and operational metadata.
  • Do not commit real gateway configs, API credentials, admin passwords, JWT secrets, OAuth client secrets, or exported tenant data.

Prerequisites

  • Docker available for the all-in-one deployment, or Kubernetes and Helm if using the packaged cluster deployment.
  • Administrator username, administrator password, and JWT secret replaced before first start.
  • At least one existing MCP server or REST API configuration ready to import into the gateway.
  • Network, TLS, reverse proxy, and port exposure reviewed before sharing generated MCP endpoints.
  • Storage choice and config persistence model reviewed for disk, SQLite, PostgreSQL, or MySQL backed deployments.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
25 minutes
Difficulty
advanced
Full copyable content
{
  "mcpServers": {
    "unla": {
      "url": "UNLA_STREAMABLE_HTTP_ENDPOINT"
    }
  }
}

About this resource

Content

Unla is a Go-based MCP gateway for converting existing MCP servers and REST APIs into managed MCP endpoints without changing the upstream service code. It can proxy MCP servers, map REST API definitions into MCP tools, and expose the result through SSE or Streamable HTTP endpoints.

The project includes an all-in-one container, a management UI, configuration examples, config persistence options, hot reload support, OAuth pre-authentication, and Kubernetes or Helm deployment assets. It is most useful when a team wants one operational gateway for several MCP-facing integrations instead of wiring each MCP client directly to every upstream server or API.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository, README, environment example, gateway configs, deployment files, release page, container package page, and documentation site for current setup, supported transports, management UI behavior, and upgrade notes.

Features

  • Convert REST API configurations into MCP tools.
  • Proxy existing MCP servers behind Unla-managed endpoints.
  • Expose MCP SSE and Streamable HTTP transports.
  • Serve a browser-based management UI for adding and editing gateway configs.
  • Persist configuration through disk, SQLite, PostgreSQL, or MySQL.
  • Hot reload configuration through signals, HTTP, or Redis PubSub.
  • Support multi-tenant deployment patterns and recoverable sessions.
  • Use OAuth-based pre-authentication for MCP servers.
  • Deploy through Docker, Kubernetes, or Helm.

Installation

The README documents an all-in-one container for quick starts:

docker run --name unla \
  -p 8080:80 \
  -p 5235:5235 \
  -e ENV=production \
  -e APISERVER_JWT_SECRET_KEY=YOUR_RANDOM_SECRET \
  -e SUPER_ADMIN_USERNAME=YOUR_ADMIN_USER \
  -e SUPER_ADMIN_PASSWORD=YOUR_ADMIN_PASSWORD \
  ghcr.io/amoylab/unla/allinone:latest

After startup, sign in to the management UI, add an MCP server or REST API configuration, and connect your MCP client to the generated /sse or /mcp endpoint for that server namespace. Replace the placeholder secret and administrator credentials before using the service with real integrations.

Use Cases

  • Put a managed MCP gateway in front of several internal MCP servers.
  • Convert legacy REST APIs into MCP tools through YAML configuration.
  • Provide separate gateway endpoints for teams, tenants, or environments.
  • Test API-to-MCP mappings through the built-in management UI.
  • Add OAuth pre-authentication and centralized routing before MCP traffic reaches upstream services.
  • Package an MCP gateway with Docker, Kubernetes, or Helm for repeatable deployment.

Safety and Privacy

Unla is access infrastructure. Treat every imported API and downstream MCP server as part of the exposed tool surface. Generated endpoints should stay behind trusted network, TLS, authentication, and tenant-boundary controls until the mapped tools have been reviewed.

The gateway can retain sensitive configuration and route sensitive tool traffic. Protect the management UI, container environment, config persistence backend, logs, OAuth settings, upstream headers, and imported API definitions. Keep real admin credentials, JWT secrets, API tokens, OAuth secrets, and tenant-specific configs out of repositories and PR discussions.

Duplicate Check

No AmoyLab/Unla entry, Unla MCP Gateway entry, or matching source URL was found in content/mcp.

#gateway#proxy#rest-api#streamable-http#management-ui

Source citations

Add this badge to your README

Show that Unla MCP Gateway is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/unla-mcp-gateway.svg)](https://heyclau.de/entry/mcp/unla-mcp-gateway)

How it compares

Unla MCP Gateway side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field
Unla logoUnla MCP Gateway

Lightweight Go MCP gateway that turns existing MCP servers and REST APIs into managed SSE or Streamable HTTP MCP endpoints through configuration.

Open dossier
agentgateway logoAgentgateway MCP Gateway

Apache-2.0 agentic proxy that can expose stdio, HTTP, SSE, and Streamable HTTP MCP servers through a managed gateway with federation, OAuth/JWT authentication, RBAC/CEL policy, CORS, TLS, observability, and Kubernetes Gateway API support.

Open dossier
mcp-proxy Transport Bridge

MCP transport bridge that converts between stdio, SSE, and Streamable HTTP so local MCP clients can reach remote servers, or remote clients can reach local stdio servers.

Open dossier
tbxark MCP Proxy Server

MIT-licensed MCP proxy server that aggregates multiple downstream MCP servers behind one HTTP service, exposing each configured server through SSE or Streamable HTTP endpoints with auth tokens and tool filtering.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandUnla logoUnlaagentgateway logoagentgateway——
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorAmoyLabagentgatewaySergey Parfenyuktbxark
Added2026-06-052026-06-062026-06-062026-06-06
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Unla can expose existing MCP servers and REST APIs as new MCP endpoints, so the final tool surface depends on every imported config. Generated endpoints may proxy read/write API operations; review tool descriptions and permissions before connecting an autonomous agent. The upstream README notes that Unla is under rapid development and that documentation can lag behind implementation. Replace default admin credentials and secrets before exposing the management UI or gateway outside a trusted development network. Hot-loaded gateway configuration, multi-tenant routing, OAuth pre-authentication, and management UI access should be governed like production API infrastructure.✓Agentgateway can aggregate and expose many downstream MCP targets through one endpoint; every target's permissions become part of the gateway surface. Stdio targets are spawned by the gateway process, so commands such as package runners or containers inherit the gateway host's trust boundary. Demo configs use permissive CORS and local authorization servers; lock down origins, headers, issuers, audiences, JWKS, and resource metadata before production use. CEL/RBAC policies can inspect MCP tool names, arguments, results, prompts, resources, request bodies, JWT claims, API keys, and backend metadata; test policies before relying on them. Remote MCP proxying, OAuth provider adaptation, Kubernetes routing, TLS termination, and guardrails are infrastructure changes that should go through normal security review.✓mcp-proxy can expose local stdio MCP servers as network services; keep the host bound to `127.0.0.1` unless remote access is intentional. Passing `--host=0.0.0.0`, permissive CORS, or named-server routes can make tools reachable by other systems on the network. Proxy configuration can include bearer tokens, OAuth client secrets, headers, server commands, environment variables, and working directories. The proxy can spawn arbitrary configured MCP server commands; only use trusted command strings and config files. Remote SSE or Streamable HTTP servers should be authenticated and trusted before forwarding client requests or tool outputs.✓tbxark MCP Proxy Server can spawn stdio subprocess MCP servers and connect to remote SSE or Streamable HTTP MCP endpoints. Every exposed route inherits the permissions of its downstream server; use per-server `authTokens` and tool filters instead of exposing all tools broadly. The docs support remote config URLs and an `--insecure` TLS flag; avoid untrusted configs and do not disable TLS verification outside controlled testing. Token-in-route fallback can expose credentials through browser history, proxy logs, metrics, and referrers; prefer authorization headers when clients support them. Logging can be enabled globally or per server, so review logs before routing secrets, prompts, tool arguments, or tool outputs.
Privacy notes✓Unla may receive prompts, tool names, tool arguments, REST API parameters, upstream MCP responses, generated endpoint metadata, logs, admin credentials, JWT secrets, OAuth tokens, and configuration history. Imported REST API and MCP server configs can include private upstream URLs, headers, tokens, tenant identifiers, and service credentials. Persisted config backends and container logs may retain sensitive endpoint definitions and operational metadata. Do not commit real gateway configs, API credentials, admin passwords, JWT secrets, OAuth client secrets, or exported tenant data.✓MCP requests, tool arguments, tool results, prompt names, resource names, session IDs, JWT/API-key claims, raw request/response bodies, logs, traces, and telemetry may pass through the gateway. CEL policy and observability features may buffer or inspect request and response bodies depending on configuration. OAuth/JWT metadata, bearer tokens, API keys, DCR secrets, Keycloak/Auth0/Okta settings, and upstream MCP credentials must be protected as secrets. Any data returned by downstream MCP tools can still be sent onward by the MCP client to the configured model provider.✓MCP requests, responses, tool outputs, progress events, headers, OAuth tokens, API access tokens, and session identifiers may pass through the proxy process. Named server config files can contain command arguments, environment variables, and credentials for downstream MCP servers. Exposed network endpoints can reveal tool names, server status, and results to clients that can reach the proxy. Logs and troubleshooting output may include endpoint URLs, command names, headers, connection errors, or server names. Store config files outside shared repositories when they include tokens or private server details.✓The proxy may process downstream server commands, environment variables, headers, auth tokens, remote config URLs, tool names, tool arguments, tool outputs, prompts, resources, logs, and route keys. Stdio subprocesses inherit configured environment variables and can access whatever local paths, network services, or credentials those commands can reach. Remote config files can reveal internal MCP server names, endpoint URLs, auth headers, tool filters, and secret placeholders. Keep config files, tokens, `.env` values, logs, and Docker volume mounts out of public repositories and shared support output.
Prerequisites
  • Docker available for the all-in-one deployment, or Kubernetes and Helm if using the packaged cluster deployment.
  • Administrator username, administrator password, and JWT secret replaced before first start.
  • At least one existing MCP server or REST API configuration ready to import into the gateway.
  • Network, TLS, reverse proxy, and port exposure reviewed before sharing generated MCP endpoints.
  • Agentgateway binary, container image, or source checkout from the upstream release/container/docs path.
  • At least one downstream MCP target, such as a stdio command, remote MCP server, SSE server, or Streamable HTTP server.
  • MCP client that can connect to the exposed Streamable HTTP or SSE route.
  • Auth, CORS, TLS, route, and policy configuration reviewed before shared or remote exposure.
  • Python 3.10 or newer.
  • uv, pipx, or Docker for installation.
  • A known MCP endpoint or local stdio MCP server to bridge.
  • Review of required headers, OAuth client credentials, CORS origins, host, port, and named-server configuration.
  • Go toolchain for source install, or Docker for the GHCR image deployment path.
  • A v2 JSON configuration file defining `mcpProxy` and downstream `mcpServers`.
  • Downstream MCP server commands, URLs, headers, environment variables, and secrets prepared before proxy startup.
  • Public base URL, bind address, route type, auth token policy, logging policy, and tool filters reviewed before exposing the proxy beyond localhost.
Install
docker run --name unla -p 8080:80 -p 5235:5235 -e ENV=production -e APISERVER_JWT_SECRET_KEY=YOUR_RANDOM_SECRET -e SUPER_ADMIN_USERNAME=YOUR_ADMIN_USER -e SUPER_ADMIN_PASSWORD=YOUR_ADMIN_PASSWORD ghcr.io/amoylab/unla/allinone:latest
docker pull ghcr.io/agentgateway/agentgateway
uv tool install mcp-proxy
go install github.com/tbxark/mcp-proxy@latest
Config
{
  "mcpServers": {
    "unla-sse": {
      "url": "UNLA_SSE_ENDPOINT"
    }
  }
}
{
  "mcpServers": {
    "agentgateway": {
      "url": "LOCAL_AGENTGATEWAY_MCP_URL",
      "headers": {
        "Authorization": "Bearer AGENTGATEWAY_MCP_TOKEN"
      }
    }
  }
}
Manual-only setup:
mcp-proxy https://example.com/sse
{
  "mcpProxy": {
    "baseURL": "MCP_PROXY_BASE_URL",
    "addr": ":9090",
    "name": "MCP Proxy",
    "version": "1.0.0",
    "type": "streamable-http",
    "options": {
      "authTokens": [
        "REPLACE_WITH_PROXY_TOKEN"
      ]
    }
  },
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": [
        "mcp-server-fetch"
      ],
      "options": {
        "toolFilter": {
          "mode": "allow",
          "list": [
            "fetch"
          ]
        }
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Enterprise Network Proxy and mTLS Setup for Claude Code

Configure corporate proxies and mutual TLS for Claude Code in locked-down networks.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.