mcpField
A
aegis

aegis

Local
github.com/getaegisSecurity15Updated 12w ago

About aegis

aegis is a local-first credential isolation proxy for AI agents, keeping real secrets out of agent reach while controlling and recording API access. Its MCP server exposes authenticated requests and service status through the same security pipeline.

Key features

  1. 01Encrypted credential vault
  2. 02Credential injection at the network boundary
  3. 03Domain restrictions and request inspection
  4. 04Per-agent access, scopes, and rate limits
  5. 05Audit logging and policy controls

Use cases

  1. 01Let an agent call an API without exposing its key
  2. 02Restrict credentials to approved domains and agents
  3. 03Review allowed and blocked credential requests

MCP support

The MCP server exposes tools to make authenticated API requests, list available services without revealing secrets, and check Aegis status. It applies the Gate security pipeline, including domain checks, agent authentication, body inspection, rate limiting, and audit logging.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"getaegis-aegis": {
"command": "npx",
"args": [
"-y",
"@getaegis/cli"
],
"env": {
"AEGIS_MASTER_KEY": "<AEGIS_MASTER_KEY>",
"AEGIS_SALT": "<AEGIS_SALT>",
"AEGIS_DATA_DIR": "<AEGIS_DATA_DIR>",
"AEGIS_PORT": "<AEGIS_PORT>",
"AEGIS_LOG_LEVEL": "<AEGIS_LOG_LEVEL>",
"AEGIS_LOG_FORMAT": "<AEGIS_LOG_FORMAT>",
"AEGIS_VAULT": "<AEGIS_VAULT>",
"AEGIS_REQUIRE_AGENT_AUTH": "<AEGIS_REQUIRE_AGENT_AUTH>",
"AEGIS_POLICY_MODE": "<AEGIS_POLICY_MODE>",
"AEGIS_POLICIES_DIR": "<AEGIS_POLICIES_DIR>",
"AEGIS_METRICS": "<AEGIS_METRICS>"
}
}
}
}
Run commandnpx -y @getaegis/cli
Environment variables to set
AEGIS_MASTER_KEYSecretMaster encryption key for the credential vault
AEGIS_SALTSecretHex-encoded 32-byte salt for key derivation (generated by aegis init)
AEGIS_DATA_DIRDirectory for vault databases and registry (default: .aegis/)
AEGIS_PORTGate proxy port (default: 3100)
AEGIS_LOG_LEVELLog verbosity: debug, info, warn, error (default: info)
AEGIS_LOG_FORMATLog output format: json or pretty (default: json)
AEGIS_VAULTNamed vault to use (default: default)
AEGIS_REQUIRE_AGENT_AUTHSecretRequire agent authentication on every request (true/false, default: false)
AEGIS_POLICY_MODEPolicy enforcement mode: enforce, dry-run, or off (default: enforce)
AEGIS_POLICIES_DIRDirectory containing YAML policy files
AEGIS_METRICSEnable Prometheus metrics endpoint (true/false, default: true)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@getaegis/cli1.0.5

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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

# Install
npm install -g @getaegis/cli

# Initialize (stores master key in OS keychain by default)
aegis init

# Add a credential
aegis vault add \
  --name slack-bot \
  --service slack \
  --secret "xoxb-your-token-here" \
  --domains slack.com

# Start the proxy
aegis 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)
# Create an agent identity
aegis agent add --name "my-agent"
# Save the printed token — it's shown once only

# Grant it access to specific credentials
aegis agent grant --agent "my-agent" --credential "slack-bot"

# Start Gate (agent auth is on by default)
aegis gate

# Agent must include its token
curl 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):

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

After (Aegis — no key visible):

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

Generate the config for your AI host:

aegis mcp config claude   # Claude Desktop
aegis mcp config cursor   # Cursor
aegis mcp config vscode   # VS Code
aegis mcp config cline    # Cline
aegis 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

# npm
npm install -g @getaegis/cli

# Homebrew
brew tap getaegis/aegis && brew install aegis

# Docker
docker run ghcr.io/getaegis/aegis --help

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

Development

git clone https://github.com/getaegis/aegis.git
cd aegis
yarn install
yarn build
yarn test

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

License

Apache 2.0

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.