Ramen: self-hosted MCP for teams

Name: Ramen: self-hosted MCP for teams
Author: bkraad47

by bkraad47version 0.8.0i★ –iRuns in the cloud

Registry nameio.github.bkraad47/ramen

Install

Overview

Description from the maker (original English)

Multi-zone MCP server for GKE/EKS/AKS: Python tools from git, NeMo guardrails, SSO, autoscaling.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Developer tools
You need to fill in: Authorization, ramen-group, ramen-zone

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: Authorization, ramen-group, ramen-zone

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http ramen 'https://{ramen_edge}/mcp' --header 'Authorization: Bearer {key}' --header 'ramen-group: {group}' --header 'ramen-zone: {zone}'

Fill in the empty values before running it.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ramen": {
      "url": "https://{ramen_edge}/mcp",
      "headers": {
        "Authorization": "Bearer {key}",
        "ramen-group": "{group}",
        "ramen-zone": "{zone}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ramen": {
      "type": "http",
      "url": "https://{ramen_edge}/mcp",
      "headers": {
        "Authorization": "Bearer {key}",
        "ramen-group": "{group}",
        "ramen-zone": "{zone}"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

Authorization secret HTTP header
Group MCP key, or use OAuth sign-in instead
ramen-group required HTTP header
Ramen group to route to
ramen-zone required HTTP header
Ramen zone to route to

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account bkraad47, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 1396 servers in this category
Published to the registry more recently than 70% of the other 1396 servers in this category
Basic checks equal to or better than 100% of the other 1396 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ramen: self-hosted MCP for teams safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization, ramen-group, ramen-zone

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.8.0) reached the registry 21 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Build your MCP tools in Python, deploy them across zones on GKE, EKS and AKS .

Rust MCP node + Python 3.12 runtime workers, Streamable HTTP at the edge and gRPC inside, guardrails per tool,

Entra ID and Google Workspace sign-in, autoscaling — managed from one FastAPI console.

Docs: https://bkraad47.github.io/ramen/ · Get started · How it works · The MCP repo · Connect a client with OAuth · Deploy on GCP · AWS · Azure · Contracts · Releases

Streamable HTTP is the front door. Every worker serves POST /mcp — a URL and a bearer header, nothing to

install — next to the gRPC service it has had since 0.3.1, on the same port, through the same guards. The stdio

bridge stays for clients that only speak stdio.

Status. Current release 0.8.0, verified live on GKE, EKS and AKS on 2026-10-17 — smoke, the 63-check release suite and six load-test scenarios on each cloud — then torn down; CI proves both transports on Linux and Windows. The single record of what each run covered, and what is tested only, is Transport → What is verified.

Build and deploy your own MCP tools across zones. Ramen turns a git repo of tools, resources and prompts into a fleet of MCP workers behind a cloud load balancer, and keeps who-can-call-what, secrets, guardrails, canary gates and the audit trail in one console. It is a platform for *your* tools, not a gateway in front of someone else's. Each worker pairs a Rust MCP node (Streamable HTTP and gRPC on one port, bearer auth, IP allow-lists, health, logs) with a Python 3.12 runtime that pip-installs and runs your code: user code never runs in the process that holds the keys. The shape, the data model and why each piece is where it is: How it works.

Git → bucket → worker. Deploy syncs the repo to a bucket; workers load by content hash. No git creds on pods.
Canary by default, gated. Roll a canary, smoke-test tools/list, diff its tool schemas against stable (breaking changes stop unless you say breaking: true), run the repo's golden cases, then roll stable. Failure leaves stable untouched.
Multi-zone from day one. Group → Environment → Zone → Worker; the load balancer routes on ramen-group / ramen-zone, so one client config works for every zone.
Guardrails inside the worker. Opt a tool into a check before the call and after the result, run in the Python runtime next to it: NVIDIA NeMo Guardrails rails (deterministic or LLM-backed, your model and key) or a policy.py of your own. A blocked call is a readable tool error and the access log names the rail. Fail-closed by default.
Your identity provider decides, your admins override. Add Microsoft Entra ID, Google Workspace or any OIDC provider on the Config page, on any cloud; read a person's groups from Graph or Cloud Identity at sign-in, map them to roles per group, and keep what admins set by hand.
Roles per group, and roles you define. Group Admin, Viewer, MCP User or a custom role on one of those bases (analyst on Viewer), usable in memberships, provider rules and per-tool access; a role can be OAuth only. Decide per environment who may see and who may call each tool; a drift signal flags a caller repeating one call.
Autoscaling by Ramen. Each zone runs between 1 worker and a max that admins set; the console scales up fast under load and back down when quiet, the same on all three clouds, with no HPA and every step in the audit log.
Three clouds. Terraform and Helm for GKE, EKS and AKS, with the same console and guards on each (Deploy to the cloud).
Enterprise controls. rmk_ MCP keys and rmn_ API keys stored as salted hashes, IP rules per zone at the node and at the cloud edge, secrets that are never displayed, Redis throttles, an audit line for every action.
One Deployment per zone, not one per tool. A worker loads *every* tool of the group, so thirty tools run on one Deployment per zone (two pods with a canary) behind one load balancer; autoscaling adds pods for load, not for tool count.

Start here · the demo group repo [ramen-demo-mcp-group](https://github.com/bkraad47/ramen-demo-mcp-group)

(point a group at it and press Deploy) · the stdio bridge [ramen-mcp-bridge on PyPI](https://pypi.org/project/ramen-mcp-bridge/)

(uvx ramen-mcp-bridge@latest) · the images [bkraad47/ramen-worker](https://hub.docker.com/r/bkraad47/ramen-worker)

and [bkraad47/ramen-console](https://hub.docker.com/r/bkraad47/ramen-console) on Docker Hub and GHCR.

Quickstart (local, 5 commands)

Needs Docker with compose v2, uv, git and make. make up pulls the release's two images from Docker Hub, about a minute; make up BUILD=1 builds them from source instead (three to five minutes).

git clone https://github.com/bkraad47/ramen && cd ramen

make up # Firestore emulator + console https://localhost:8443 + one worker (localhost:8080: Streamable HTTP + gRPC) make demo # zone, group demo from the demo repo, an rmk_ key, a canary deploy, then a tools/call

PASS: demo_calculator_tool(2,3,add) -> 5 <- the success line

open https://localhost:8443 # self-signed cert; admin@ramen.local + the generated password: grep ADMIN_PASSWORD deploy/local/.env make down # stop and remove volumes

make demo is safe to re-run: an existing zone, group or environment answers "exists" and a fresh key is generated each time. Nothing in the stack is a static secret: make up generates the admin password, Fernet key, MCP key, admin key and session secret into deploy/local/.env (git-ignored), and scripts/check_secrets.py fails CI if a literal one ever returns.

Connect a client

A worker is a URL (/mcp) and two routing headers, ramen-group and ramen-zone. The credential decides whose name a call runs under:

A group key (rmk_) in Authorization: Bearer, for agents and automation. Any HTTP-capable client.
A person's sign-in through the console (OAuth 2.1, with a Ramen password, Entra ID or Google): Claude Code over HTTP, or any stdio client through the bridge.

Every form, with the pages you will see: Get started → Connect a client · Connect with OAuth · Transport → Connecting. In a cloud, the group page's How MCP users sign in card prints the exact commands for your install.

Screenshots

Login	Dashboard, load per zone and group

Group: environments, deploy jobs, zones/workers, MCP keys	Deploy job with streamed log

Secrets (names only, values never shown)	Logs (one JSON line per MCP call, downloadable)

Identity providers: Entra ID with group lookup and role rules	Custom roles, one OAuth-only

Zone actions: count, max, last autoscale decision	Zones and workers with the max per group

Transport and security, in short

Workers speak Streamable HTTP (POST /mcp, MCP spec 2025-06-18) and gRPC (ramen.v1.Mcp/Call) on one port through one implementation of every guard, so a check is on both transports or on neither. TLS ends at the load balancer. The node checks the credential, the source range at the provider's x-forwarded-for hop, blocked names and the size and in-flight caps. The runtime reaches the bucket as the zone's own cloud identity, and guardrails run between the runtime and your tool. Hop by hop, with what protects each and what is verified: Transport. Boundaries and non-goals: Threat model.

Deploy to the cloud

Target	What Terraform and Helm build	Guide
GCP	GKE Autopilot, Firestore, GCS, Secret Manager, global HTTPS LB (GKE Gateway, header-routed gRPC and Streamable HTTP), Cloud Armor	docs · `deploy/README.md`
AWS	EKS, DynamoDB, S3, Secrets Manager, ALB (gRPC and HTTP/1.1 target groups), WAF (Terraform or CloudFormation)	docs
Azure	AKS (workload identity), Table Storage, Blob Storage, Key Vault, Envoy Gateway with a Let's Encrypt certificate	docs
Local	docker compose: Firestore emulator, console, one worker; CI e2e on every push	`deploy/local/README.md`

Bring-up is the same on each: terraform apply → helm upgrade --install (the release's public images, or make push to your own registry) → add a zone and a group in the console → Deploy. About 25 minutes, mostly waiting for the cluster and the load balancer. The edge gets a publicly trusted certificate on a free sslip.io hostname (Let's Encrypt on AKS), so clients use https:// /mcp and the bridge points at :443 --tls with nothing to import. What each cloud run covered: Transport → What is verified.

Write your own tools

A group repo is

Only the beginning is shown; read the rest in the repo

Ramen: self-hosted MCP for teams

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Quickstart (local, 5 commands)

PASS: demo_calculator_tool(2,3,add) -> 5 <- the success line

Connect a client

Screenshots

Transport and security, in short

Deploy to the cloud

Write your own tools