[!수신] **이 프로젝트는 진행중인 작업이며 생산 준비를 고려하지 않아야합니다. ** · 나는 공정하게 전반적인 건축은 소리가 끊어지고, 나 자신은 구현에 의존한다. 그래서 should 작업 :tm : . 그러나 확실히 알파 소프트웨어. · 변화를 파괴! :) · 또한, docs에 너무 많이 의존하지 마십시오, 그들은 신속하게 드리프트, 나는 항상 변경하거나 추가 / 제거 기능을 할 때 업데이트하지 않습니다. 그들은 주로 저에게 닻에 여기 있고 나의 처음 시각에 집중할 것을 돕습니다.

[!팁] 당신의 API를 위한 MCP 서버를 얻는 가장 쉬운 방법을 찾고? 체크 아웃 stainless✨. 최고의 SDK와 MCP 생성을 제공합니다. 완전한 MCP 서버를 구축하고 몇 분 안에 Cloudflare 및 Docker Hub에 게시하십시오! · 면책 조항: mcp-front의 저자는 초기 스테인리스 직원입니다

MCP (Model Context Protocol) 서버의 인증 게이트웨이. 팀은 내부 데이터베이스, API 및 도구로 클로드를 사용하여 인터넷에 배포합니다.

문제

내부 MCP 서버(database, Linear, Notion, internal APIs)로 Claude를 사용하기 위해 팀을 원합니다.

mcp-front

[!WARNING] This project is a work in progress and should not be considered production ready.

Though I’m fairly confident the overall architecture is sound, and I myself rely on the implementation — so it should work :tm:. But definitely alpha software.

Expect breaking changes! :)

Also, don’t rely too much on the docs, they drift fairly quickly, I do not always keep them updated when doing changes or adding/removing features. They are mostly here to anchor me and help me stay focus on my initial vision.

[!TIP] Looking for the easiest way to get an MCP server for your API? Check out Stainless✨. We offer best-in-class SDK and MCP generation. Build a complete MCP server and publish it to Cloudflare and Docker Hub in a few minutes!

Disclaimer: the author of mcp-front is an early Stainless employee

An authentication gateway for MCP (Model Context Protocol) servers. Let your team use Claude with internal databases, APIs, and tools without exposing them to the internet.

The problem

You want your team to use Claude with internal MCP servers (databases, Linear, Notion, internal APIs). But MCP servers don’t have built-in multi-user authentication. You either expose them to the public internet, build authentication yourself, or run separate instances per user. None of these are great.

The solution

mcp-front sits between Claude and your MCP servers as an authentication gateway. Your team authenticates via OAuth once (Google, Azure AD, GitHub, or any OIDC provider). When Claude connects, mcp-front validates the token, checks the user belongs to your organization, and proxies to the actual MCP server in your secure environment.

For stdio servers, each user gets an isolated subprocess. For services that need individual API keys (Notion, Linear), users connect them once through a web UI and mcp-front injects tokens automatically. Tokens are scoped to specific services (RFC 8707) — a token for your Postgres server won’t work for Linear.

Organization-wide access control with per-user isolation. No modifications to your MCP servers. Nothing exposed to the internet.

How it works

1. User adds https://your-domain.com//sse to Claude