RavensPort

Give each AI agent its own MCP endpoint — pooling the servers you choose, exposing only the tools you allow, with OAuth handled for you.

winget install RavensPort

Documentation · Microsoft Store · Releases

_{winget and the installer give you the full app. The Store build has no Proton Pass and no
mTLS — why.}

A tray-resident desktop app that runs a local reverse proxy on 127.0.0.1. It owns the OAuth2
flow and token lifecycle for upstream APIs and MCP servers, then lets you compose those servers
into filtered, per-agent MCP endpoints. Windows is the supported platform; an experimental
Debian/Ubuntu build is available for x86-64 and arm64.

What it does

MCP Funnel — per-agent endpoints pooling several MCP servers, with per-tool filtering
API to MCP — turn an API you already proxy into an MCP endpoint from a JSON manifest, or
import an OpenAPI document and pick which of its operations become tools
OAuth2, handled — Google, GitHub, Nextcloud or any custom provider; device-code sign-in;
client-credentials and Google service accounts for logins with nobody at the keyboard; static
API keys for the services that never offered OAuth. Tokens refresh in the background
Secrets stay in your password manager — 1Password or Proton Pass holds every credential,
and nothing is written to this PC
A proxy key per endpoint — every route, funnel and bridge has its own, so a key leaked from
one client cannot reach the rest. Optionally require a client certificate as well

Install

winget install RavensPort

Or take the installer from Releases, or the
Microsoft Store. Windows 10/11. Full
instructions, including building from source, are in
Installation.

Debian / Ubuntu _experimental

v5.0.0 moved the interface to Avalonia and added a .deb for Debian and Ubuntu. Since v5.0.1 there
is one for x86-64 (amd64) and one for 64-bit Arm (arm64, which covers a Raspberry Pi running
64-bit Raspberry Pi OS), and apt picks the right one. Install it from the RavensPort apt
repository, and apt upgrade keeps it current:

sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://abishekvupputur.github.io/ravensPort/apt/ravensport.asc \
  | sudo tee /etc/apt/keyrings/ravensport.asc > /dev/null
echo "deb [signed-by=/etc/apt/keyrings/ravensport.asc] https://abishekvupputur.github.io/ravensPort/apt ./" \
  | sudo tee /etc/apt/sources.list.d/ravensport.list
sudo apt update
sudo apt install ravensport

Or take the .deb from Releases and sudo apt install ./ravensport_<version>_<amd64|arm64>.deb,
or build one from a checkout with packaging/build-deb.sh.

It has had far less use than the Windows build, and a few things differ by necessity — the Proton
Pass session key lives in the desktop keyring rather than behind Windows Hello, and pass-cli must
be installed in a system location. Everything is on the wiki:
Linux build.

Documentation

Everything lives in the wiki.

Page
Concepts	How credentials, routes, funnels and bridges fit together
Setting up a credential	Every sign-in method, and how to test one
Setting up a route	Proxying an upstream, and choosing how the credential is sent
API to MCP	Manifests, variants, and importing an OpenAPI document
MCP Funnel	Pooling sources into one endpoint and filtering what it exposes
Calling the proxy	Proxy keys, how long they last, and why there is one per endpoint
Client certificates (mTLS)	Requiring a certificate as well as a key
Where your configuration lives	What is in the vault, what is on disk, and what syncs
Logs	What is recorded, what is redacted, and where it goes
Troubleshooting	When something does not work
Building	Building, testing and packaging from source
Linux build	Building, installing and running the experimental Debian/Ubuntu package

Manifests ready to use are in templates/api-mcp/, and the format is
documented in AUTHORING.md.

License

MIT — see LICENSE. Third-party dependencies (all MIT or Apache-2.0) are listed in
THIRD-PARTY-NOTICES.md, which also covers what redistributing the
published exe requires.