Now available on the Mac App Store

One MCP gateway for ChatGPT, Claude & Codex.

Configure downstream servers once in MCP Beast. Claude Desktop and Codex connect locally; ChatGPT connects through optional MCP Beast Pro Remote Access. Each client discovers tools without loading every downstream schema up front.

ChatGPT Claude Desktop Codex Also supports Cursor

1. Configure once Add local commands, remote endpoints, OAuth, and headers in the Mac app.

2. Choose the connection Use local setup for Claude and Codex, or Pro Remote Access for ChatGPT.

3. Keep context focused Seven stable gateway tools find and call hidden downstream tools on demand.

Get MCP Beast for Mac See the gateway flow

On the Mac App Store · macOS 26 or later · Local and private by default

MCP Beast showing a selected MCP server with discovered tools

How it works

Stop rebuilding the same MCP setup in every client.

MCP Beast becomes the gateway your clients talk to while it manages downstream discovery, authentication, routing, retries, and result shaping.

Download MCP Beast from the Mac App Store.

Add your local commands, remote endpoints, and authenticated MCP servers once.

Connect Claude Desktop or Codex locally, or enable Pro Remote Access for ChatGPT.

Let each client discover and call downstream tools through the same gateway.

Client compatibility

ChatGPT, Claude, and Codex—without pretending they connect the same way.

Claude Desktop and Codex connect on your Mac. ChatGPT and other cloud-hosted clients require optional MCP Beast Pro Remote Access because they cannot reach localhost directly. Cursor remains supported as a local client.

ChatGPT

Pro Remote Access

ChatGPT cannot reach localhost. Connect it through MCP Beast Pro's optional outbound relay.

Claude Desktop

Local bridge

Use MCP Beast's generated bridge configuration for Claude Desktop's local MCP setup.

Codex

Local gateway

Add the MCP Beast endpoint once instead of repeating every downstream server.

Cursor

Also supported

Connect MCP Beast as a local custom MCP server and route configured tools through it.

Set up MCP Beast on your Mac

Context-efficient by design

Show agents the route, not every schema.

MCP Beast keeps downstream tools behind a compact dispatcher. Agents can find the right capability first, then request the full schema only for the tool they are ready to call.

use_mcp · list_mcps · search_tools · describe_tool · call_tool · get_mcp_status · refresh_mcp

1

Discover

A small, stable MCP Beast toolset is visible to the client.
2

Narrow

The agent searches MCP Beast's cached catalog for the relevant server and tool.
3

Load on demand

The selected tool's full schema is described only when the call needs it.
4

Route

MCP Beast calls the hidden downstream tool and returns a focused result.

Why it matters

Your agents get the right tools without the noise.

One registry for every MCP

Add local commands and remote MCP endpoints once, then keep status, auth, namespaces, icons, and discovered tools in one place.

Lower context by default

Clients see MCP Beast's compact dispatcher first, then search, describe, and call only the downstream tools that matter.

Safer tool routing

Read/write safety hints, compact result shaping, and rate-limit backoff help agents avoid noisy calls and accidental mutations.

OAuth and token friendly

Connect authenticated MCPs from the Mac app, including registered-client OAuth providers, while keeping secrets in macOS Keychain.

Multi-account ready

Use explicit namespaces for work, personal, staging, or customer MCPs so agents can route to the right account.

Supportable when things fail

Diagnostics reports redact secrets, runtime state is easier to inspect, and the menu bar keeps common actions close.

Authentication

Connect powerful MCPs without scattering secrets.

Add remote endpoints, local commands, headers, and OAuth-backed servers from one Mac app. MCP Beast stores sensitive headers, local environment variables, OAuth tokens, gateway tokens, and Remote Access tokens with Keychain-backed protection and masked diagnostics.

Built for real MCP setups

Fast when it works. Clear when it doesn't.

MCP Beast is more than a pass-through proxy. It keeps a cached catalog of configured MCPs, exposes a small dispatcher to clients, and helps agents narrow requests before spending context on full schemas or large results.

Compact search and describe flows reduce schema noise before a tool is called.

Read/write routing hints help agents choose safe tools for read-only tasks.

Rate-limit and timeout handling avoids hammering downstream MCPs when they ask for time.

Diagnostics reports redact secrets so support requests are easier and safer to share.

Menu bar shortcuts keep opening the app, Settings, copying the gateway URL, and reporting issues one click away.

MCP Beast Pro

Take your MCP setup beyond your Mac.

Remote Access lets ChatGPT, Claude web/mobile, and cloud agents reach MCP Beast through a secure outbound relay while your local gateway stays private.

Get MCP Beast for Remote Access

Private by default

Local first. Relay only when enabled.

Local endpoint: localhost:7331/mcp

Remote endpoint: mac.mcp-beast.ai

Auth: bearer tokens you can regenerate or disable.

FAQ

Built for the way MCP actually grows.

Is MCP Beast just a proxy?

No. MCP Beast is designed as a local registry and router. It can expose a compact dispatcher surface so agents can search, describe, and call the right downstream tool only when needed.

Does my MCP traffic leave my Mac?

Local mode stays on your Mac. LAN access is opt-in and protected by a bearer token. Remote Access is a Pro feature that uses an outbound relay when you explicitly enable it.

Which AI apps can use it?

Claude Desktop and Codex connect locally, and Cursor is also supported as a local client. ChatGPT, Claude web/mobile, and other cloud clients require the optional MCP Beast Pro Remote Access relay.

Why does context usage get smaller?

Many MCP clients load every tool schema from every configured server. MCP Beast exposes a compact dispatcher first, lets agents search for relevant tools, and reveals full schemas or larger results only when needed.

Can I use multiple accounts for the same MCP?

Yes. Give each downstream MCP an explicit namespace, such as a work and personal account, and MCP Beast will route calls through that stable name.

What happens when a downstream MCP is slow or rate limited?

MCP Beast is designed to keep cached tool discovery useful, back off repeated failing requests, and return clearer diagnostics so agents know when to retry or narrow the call.

Your MCP setup, in one place

Configure once. Connect your clients. Keep tool context focused.

Download MCP Beast for Mac and replace repeated server configuration with one private gateway.

Get MCP Beast for Mac