Log inSubmit server
Aegis logo

Aegis

by getaegis

Isolates agent credentials behind a local proxy with domain controls, authentication, request inspection, and audit logging.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Aegis

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "getaegis-aegis": {
      "command": "npx",
      "args": [
        "-y",
        "@getaegis/cli"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @getaegis/cli

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 11d ago.

Overview

getaegis/aegis is a credential isolation proxy and MCP server for routing AI-agent API requests without exposing raw secrets. It stores credentials in an encrypted vault, injects them at the network boundary, restricts outbound domains, authenticates agents, and records requests. Use it when an agent needs access to services such as Slack, GitHub, or Stripe but should not receive reusable API keys. It can run as a transparent HTTP proxy or through MCP tools.

Use cases

  • Protect Slack bot tokens from direct agent access
  • Restrict GitHub API credentials by agent and domain
  • Inspect and rate-limit requests to Stripe
  • Route MCP API calls through an audited credential proxy

Key features

  • Encrypted credential vault
  • Domain-restricted HTTP proxy
  • Native MCP server with three tools
  • Per-agent authentication and grants
  • Request body inspection and audit logging
  • Optional policies, metrics, and webhooks

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

18/18 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @getaegis/cli (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars14Stargazers on the source repository.
npm downloads440Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Aegis works

What getaegis/aegis does

getaegis/aegis places a controlled boundary between an AI agent and the APIs the agent needs to call. Credentials are stored in an encrypted vault and added to outbound requests by the proxy rather than being passed to the agent. The repository describes support for AES-256-GCM encrypted credential storage, OS keychain storage by default, and file fallback across macOS, Windows, and Linux.

The proxy can restrict each credential to an allowlist of domains. It also supports agent identities, credential grants, rate limits, request body inspection, and audit records for both permitted and blocked requests. Optional policy files can apply method, path, rate, and time-of-day rules. A web dashboard, Prometheus metrics endpoint, webhook alerts, RBAC, and separate vaults are also documented features.

How it works

In HTTP proxy mode, an agent sends a request to the local Gate process using a service path. A target-host header can identify the upstream domain when needed. Gate authenticates the agent when authentication is enabled, checks the destination against the credential’s domain restrictions, inspects the request, injects the selected secret, forwards the request, and records the result.

The MCP mode exposes the same security pipeline without requiring the agent to make HTTP calls directly. The MCP configuration points to the CLI’s mcp serve command, while the vault remains outside the agent’s configuration. This makes the getaegis/aegis MCP server suitable for MCP-compatible hosts that need credentialed API access without embedding secrets in environment variables.

Setup and configuration

Install the CLI with npm, Homebrew, or Docker. The documented runtime requirement is Node.js 20 or newer. Run aegis init to initialize the installation; the master key is stored in the operating system keychain by default. Add credentials with aegis vault add, including a name, service, secret, and permitted domain.

For an unauthenticated local test, start Gate with aegis gate --no-agent-auth. For a controlled deployment, create an agent identity, retain the one-time token, grant that agent access to a specific credential, and start Gate with its default authentication behavior.

MCP hosts can use npx -y @getaegis/cli mcp serve. The CLI also provides generated configuration commands for Claude Desktop, Cursor, VS Code, Cline, and Windsurf.

Tools and capabilities

The getaegis/aegis MCP server provides three documented tools:

  • aegis_proxy_request makes an authenticated API request using a named service and path; the server injects the corresponding credential.
  • aegis_list_services returns available service names without returning secrets.
  • aegis_health checks Aegis status.

The MCP implementation applies the Gate pipeline, including domain checks, agent authentication, body inspection, rate limiting, and audit logging. The project also documents examples for Slack, GitHub, Stripe, and OpenClaw, with policies and configuration files for those examples. TLS can be enabled for Gate, and the repository includes security architecture and threat-model documentation for reviewing its trust boundaries and controls.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Aegis

getaegis/aegis is an MCP server that connects AI agents to credentialed APIs through a local security proxy. Its main tools are `aegis_proxy_request` for authenticated calls, `aegis_list_services` for secret-free service names, and `aegis_health` for status checks. It injects credentials without exposing them to the agent.

Install it with `npm install -g @getaegis/cli`, Homebrew, or Docker. The documented Node.js requirement is version 20 or newer. For MCP, run `npx -y @getaegis/cli mcp serve` in the host configuration.

getaegis/aegis provides configuration commands for Claude Desktop, Cursor, VS Code, Cline, and Windsurf. Run `aegis mcp config` with the corresponding client name to generate a host configuration.

getaegis/aegis keeps credentials in its encrypted vault and injects them at the network boundary when forwarding requests. The agent supplies a service and path through the proxy or MCP tool instead of receiving the raw secret.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAegis AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/getaegis-aegis?style=directory)](https://allmcps.com/mcp/getaegis-aegis)
HTML Embed
<a href="https://allmcps.com/mcp/getaegis-aegis"><img src="https://allmcps.com/api/badge/getaegis-aegis?style=directory" alt="Aegis on AllMCPs" /></a>