Aegis

io.github.getaegisPublished by GitHub account getaegisv1.0.5Updated Oct 24, 2026

Credential isolation for AI agents. Inject secrets at the network boundary.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local-first credential isolation proxy that lets an AI assistant call external APIs through Aegis, which injects stored secrets at the network boundary.

What you can do
Make authenticated API calls to configured services, with Aegis injecting the stored credential instead of exposing it to the assistant (aegis_proxy_request). List the available service names, never the secrets themselves (aegis_list_services). Check Aegis status and health (aegis_health). Requests pass through the same pipeline as the HTTP gate: domain allowlists, agent authentication, body inspection, rate limiting and audit logging.
When to use it
Use it when an assistant needs to call services such as Slack, GitHub or Stripe but you do not want raw API keys in MCP config or reachable by the model, and you want domain restrictions and an audit trail on outbound calls.
Requirements
Runs locally over stdio as the npm package @getaegis/cli (Node.js 20 or newer). Requires initialization with aegis init and the secrets AEGIS_MASTER_KEY and AEGIS_SALT; credentials must be added to a vault first. Optional settings include AEGIS_DATA_DIR, AEGIS_POLICIES_DIR, AEGIS_POLICY_MODE, AEGIS_PORT, AEGIS_REQUIRE_AGENT_AUTH, AEGIS_VAULT, AEGIS_METRICS and log options. Network access to the target APIs is needed.
Before you install
The vault is only as safe as AEGIS_MASTER_KEY and AEGIS_SALT; losing them can make stored credentials unrecoverable, and leaking them exposes every secret. The proxy makes real outbound calls that can change or send data in third-party services, and may incur costs (for example Stripe). Agent authentication is off by default (AEGIS_REQUIRE_AGENT_AUTH false), so enable it and scope grants per agent. Audit logs and metrics may record request details.

Installation

In SourceWeft

  1. Open Aegis in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Aegis

[CI] [npm version] [Docker] [License]

Stop putting API keys where AI agents can read them.

Aegis is a local-first credential isolation proxy for AI agents. It sits between your agent and the APIs it calls — injecting secrets at the network boundary so the agent never sees, stores, or transmits real credentials.

[Aegis demo]

How It Works

[How Aegis works — agent sends request through Gate, credentials injected at the network boundary]

Why?

AI agents (Claude, GPT, Cursor, custom bots) increasingly call real APIs — Slack, GitHub, Stripe, databases. The current pattern is dangerous:

  1. Agents see raw API keys — one prompt injection exfiltrates them
  2. No domain guard — a compromised agent can send your Slack token to evil.com
  3. No audit trail — you can't see what an agent did with your credentials
  4. No access control — every agent can use every credential

Aegis solves all four. Your agent makes HTTP calls through a local proxy. Aegis handles authentication, enforces domain restrictions, and logs everything.

Quick Start

bash
# Installnpm install -g @getaegis/cli
# Initialize (stores master key in OS keychain by default)aegis init
# Add a credentialaegis vault add \  --name slack-bot \  --service slack \  --secret "xoxb-your-token-here" \  --domains slack.com
# Start the proxyaegis gate --no-agent-auth
# Test it — Aegis injects the token, forwards to Slack, logs the request# X-Target-Host tells Gate which upstream server to forward to (optional if credential has one domain)curl http://localhost:3100/slack/api/auth.test \  -H "X-Target-Host: slack.com"

Production Setup (with agent auth)

bash
# Create an agent identityaegis agent add --name "my-agent"# Save the printed token — it's shown once only
# Grant it access to specific credentialsaegis agent grant --agent "my-agent" --credential "slack-bot"
# Start Gate (agent auth is on by default)aegis gate
# Agent must include its tokencurl http://localhost:3100/slack/api/auth.test \  -H "X-Target-Host: slack.com" \  -H "X-Aegis-Agent: aegis_a1b2c3d4..."

MCP Integration

Aegis is a first-class MCP server. Any MCP-compatible AI agent can use it natively — no HTTP calls needed.

Before (plaintext key in config):

json
{  "mcpServers": {    "slack": {      "command": "node",      "args": ["slack-mcp-server"],      "env": { "SLACK_TOKEN": "xoxb-1234-real-token-here" }    }  }}

After (Aegis — no key visible):

json
{  "mcpServers": {    "aegis": {      "command": "npx",      "args": ["-y", "@getaegis/cli", "mcp", "serve"]    }  }}

Generate the config for your AI host:

bash
aegis mcp config claude   # Claude Desktopaegis mcp config cursor   # Cursoraegis mcp config vscode   # VS Codeaegis mcp config cline    # Clineaegis mcp config windsurf # Windsurf

The MCP server exposes three tools:

ToolDescription
aegis_proxy_requestMake an authenticated API call (provide service + path, Aegis injects credentials)
aegis_list_servicesList available services (names only, never secrets)
aegis_healthCheck Aegis status

The MCP server replicates the full Gate security pipeline: domain guard, agent auth, body inspection, rate limiting, audit logging.

Setup Guides

Features

FeatureDescription
Encrypted VaultAES-256-GCM encrypted credential storage with PBKDF2 key derivation
HTTP Proxy (Gate)Transparent credential injection — agent hits localhost:3100/{service}/path
Domain GuardEvery outbound request checked against credential allowlists. No bypass
Audit LedgerEvery request (allowed and blocked) logged with full context
Agent IdentityPer-agent tokens, credential scoping, and rate limits
Policy EngineDeclarative YAML policies — method, path, rate-limit, time-of-day restrictions
Body InspectorOutbound request bodies scanned for credential-like patterns
MCP ServerNative Model Context Protocol for Claude, Cursor, VS Code, Windsurf, Cline
Web DashboardReal-time monitoring UI with WebSocket live feed
Prometheus Metrics/_aegis/metrics endpoint for Grafana dashboards
Webhook AlertsHMAC-signed notifications for blocked requests, expiring credentials
RBACAdmin, operator, viewer roles with 16 granular permissions
Multi-VaultSeparate vaults for dev/staging/prod with isolated encryption keys
Shamir's Secret SharingM-of-N key splitting for team master key management
Cross-Platform Key StorageOS keychain by default (macOS, Windows, Linux) with file fallback
TLS SupportOptional HTTPS on Gate with cert/key configuration
Configuration Fileaegis.config.yaml with env var overrides and CLI flag overrides

Example Integrations

Step-by-step guides with config files and policies included:

  • Slack Bot — Protect your Slack bot token with domain-restricted proxy access
  • GitHub Integration — Secure GitHub PAT with per-agent grants and read-only policies
  • Stripe Backend — Isolate Stripe API keys with body inspection and rate limiting
  • OpenClaw Skill — Aegis skill for OpenClaw personal AI assistant

Security

  • Published STRIDE threat model — 28 threats analysed, 0 critical/high unmitigated findings
  • Full security architecture documentation (trust boundaries, crypto pipeline, data flow)
  • AES-256-GCM + ChaCha20-Poly1305 encryption at rest
  • Domain guard enforced on every request — no bypass
  • Agent tokens stored as SHA-256 hashes — cannot be recovered, only regenerated
  • Request body inspection for credential pattern detection
  • Open source (Apache 2.0) — read the code

How Aegis Compares

.env filesVault/DopplerInfisicalAegis
Agent sees raw keyYesYes (after fetch)Yes (after fetch)No — never
Domain restrictionsNoNoNoYes
MCP-nativeNoNoAddingYes
Local-firstYesNoNoYes
Setup10 sec30+ min15+ min~2 min

See full comparison for detailed breakdowns against each approach.

Documentation

DocumentDescription
Usage GuideFull reference: CLI commands, configuration, RBAC, policies, webhooks, troubleshooting
Security ArchitectureTrust boundaries, crypto pipeline, data flow diagrams
Threat ModelSTRIDE analysis — 28 threats, mitigations, residual risks
ComparisonDetailed comparison with .env, Vault, Doppler, Infisical
FAQCommon questions and objections
RoadmapFeature roadmap
ContributingCode style, PR process, architecture overview

Install

bash
# npmnpm install -g @getaegis/cli
# Homebrewbrew tap getaegis/aegis && brew install aegis
# Dockerdocker run ghcr.io/getaegis/aegis --help

Requires Node.js ≥ 20 — check with node -v

Development

bash
git clone https://github.com/getaegis/aegis.gitcd aegisyarn installyarn buildyarn test

See CONTRIBUTING.md for code style, PR process, and architecture overview.

License

Apache 2.0

Source: README.md at commit f1321b3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts