# Install mcp-remote with Homebrew Remote proxy for Model Context Protocol with OAuth support. Version 0.1.38 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:mcp-remote ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install mcp-remote ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:mcp-remote - **Package manager:** Homebrew - **Version:** 0.1.38 - **Source summary:** Remote proxy for Model Context Protocol with OAuth support - **Homepage:** - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - mcp-remote (alias) - mcp-remote-client (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.1.38 ## Project history and usage mcp-remote is a TypeScript CLI that lets stdio-only MCP clients connect to remote MCP servers, including servers that require OAuth. Its README explicitly frames it as a temporary bridge until popular clients support remote authorized MCP servers directly. ### Project history The repository was created in March 2025, after the MCP authorization specification introduced a secure model for remote MCP servers. The README calls the project a working proof of concept and explains the gap it fills: many clients could launch local stdio servers, while remote HTTP/SSE servers and OAuth flows were not yet uniformly supported. The project evolved around practical client configuration examples for Claude Desktop, Cursor, Windsurf, and similar tools. Later README sections document transport strategies, custom headers, static OAuth metadata, proxy environment support, debug logs, and client-mode troubleshooting. ### Adoption history mcp-remote gained adoption as a one-line `npx` adapter in client configuration files. GitHub metadata showed more than a thousand stars and hundreds of forks by July 2026, and tags indicated continued 0.1.x package iteration. Its usage is closely tied to the adoption curve for remote MCP servers. As hosted MCP services appeared before every client had native remote OAuth support, mcp-remote gave users a package-level compatibility layer that could be installed or executed on demand. ### How it is used Typical use places `npx mcp-remote https://remote.mcp.server/sse` in the `command` and `args` section of an MCP client configuration. The README documents flags for headers, resource isolation, HTTP allowances, transport order, OAuth callback port, ignored tools, and proxy environment variables. The tool stores credential information in `~/.mcp-auth` unless `MCP_REMOTE_CONFIG_DIR` points elsewhere. The README also documents a `mcp-remote-client` mode for running an authorization flow from the command line when troubleshooting stale credentials or token refresh problems. ### Why package nerds care mcp-remote is a textbook bridge package: it exists because the protocol moved faster than client feature support. Package managers matter here because users can patch a capability gap with one command in an MCP client config instead of replacing the host application. The credential cache and OAuth behavior also make it more than a thin transport pipe. For package maintainers and users, it codifies a reusable auth-and-transport shim around remote MCP services while the ecosystem converges on native implementations. ### Timeline - 2025: GitHub repository created for geelen/mcp-remote. - 2025: README documents MCP authorization support and stdio-to-remote bridging. - 2025: Client configuration examples cover Claude Desktop, Cursor, and Windsurf. - 2026: 0.1.x tags and repository activity continue as remote MCP adoption grows. ### Related projects - sparfenyuk/mcp-proxy provides a broader MCP transport bridge without the same OAuth-centered positioning. - modelcontextprotocol/inspector can test MCP servers and includes transport/debugging tooling. - The MCP authorization specification is the upstream protocol feature that motivated the project. ### Sources - - - - - ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Credential files - Unix: ~/.mcp-auth ## Combined YAML source View the package source record on GitHub. [combined/mcp-remote.yml](https://github.com/mxcl/pkgdb/blob/main/combined/mcp-remote.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph