Aerostack
Aerostack
Private MCP Workspace

Three ways to run
private MCP servers.

Host MCPs on Aerostack, proxy servers on your own infrastructure, or install from the Hub marketplace. AES-GCM encrypted secrets, per-user analytics via Analytics Engine, and workspace tokens (mwt_ prefix) with seat limits built in.

Host on AerostackProxy your existing serverInstall from Hub
MCP Workspace12 MEMBERS@aliceadmin@bobdev@caroldevgithub-mcpinternal-dbjira-toolPrivateTEAM MEMBERSPRIVATE MCPs
//Before vs After

Stop sharing API keys. Start sharing access.

Before

Share API keys with every developer on the team

No visibility into who called what, or when

Rotate every key when someone leaves the company

Each dev installs MCPs locally — different versions, different configs

After

Keys stored in AES-GCM encrypted vault — never exposed to developers

Per-user workspace tokens (mwt_ prefix) with seat limits

Revoke one user without affecting the rest of the team

Full audit trail — every tool call attributed to a specific user

The enterprise killer feature: Proxy Mode

Your MCP server stays on your infrastructure. Aerostack becomes the gateway — handles secrets, access control, per-user analytics. Team members never see API keys. You get full observability via Analytics Engine without changing a line of your server code.

//How It Works

Four steps to private AI tools.

01

Create Workspace

Set up a private workspace from your dashboard in 30 seconds.

30 seconds
02

Add Your MCPs

Host on Aerostack, proxy your existing server, or install from the Hub marketplace. Three modes, one workspace.

3 modes
03

Invite Your Team

Add members by email, assign roles. Access is instant — zero machine configuration.

Role-based
04

Connect with One Line

Paste one mcp.json snippet. Every workspace MCP is immediately available in any client.

Any MCP client
//Setup

One snippet. All tools.

Paste this config into your MCP client. Every MCP in your workspace — github-mcp, internal-db, jira-tool — becomes available immediately. No installs. No per-tool credentials.

Claude Desktop
Cursor
VS Code MCP extension
Any MCP-compatible client

New team member? Same snippet, same token prefix, same access. Onboarded in under a minute.

claude_desktop_config.json
{
"mcpServers": {
"workspace": {
"url": "https://gateway.aerostack.dev/ws/acme",
"headers": {
"Authorization": "Bearer mwt_acme_••••••••"
}
}
}
}
//Access Control

Control who sees what.

Invite by email or role

Add members instantly. No machine-side setup required on their end.

Admin / Developer / Read-only roles

Control who can add MCPs, invite others, or just call tools.

Whitelist specific MCPs

Only want your team accessing 2–3 trusted MCPs? Whitelist them. Everything else is blocked.

YOUR TEAMDev 1adminDev 2devDev 3devmwt_acme_mwt_acme_Private MCP RegistryToken-Gated Accessgithub-mcpinternal-dbjira-toolcompany-searchTeam: @acmeGateway URL/ws/acme-workspaceSame toolsany modelClaudeChatGPTGemini✓ One token = all tools    ✓ New member onboarded in seconds    ✓ No per-tool credentials
//Observability

See everything your team does.

TOOL ANALYTICSgithub-mcp1,247internal-db891jira-tool612company-search421slack-notify287DEVELOPER ACTIVITY@alice1,10248msjust now@bob73471ms3m ago@carol50952ms8m ago@david287134ms22m ago@emma9689ms1h agoAVG RESPONSE TIME (ms)1501005030m20m10mnow

Tool call frequency — see which MCPs your team relies on most

Per-developer usage — attribution at the individual level

P95 response time — identify slow tools before they become problems

Error rates & alerts — catch failing MCPs the moment they break

//Features

Everything your team needs. Built in.

Team Access Control

Invite by email, assign roles. Revoke access instantly — zero machine-side changes required.

AES-GCM Encrypted Secrets

Credentials encrypted with AES-GCM at rest. Injected at runtime, never exposed to developers or stored in plaintext.

Observability & Logs

Every tool call logged with developer identity, latency, and response. Fully searchable.

Auto-Namespacing

Private tools are namespaced to your workspace. No naming collisions with public MCPs.

Proxy Mode (BYO Server)

Point to your own server. Aerostack becomes the gateway — handles secrets, access control, and per-user analytics. No migration needed.

Audit Trail

Complete history of who accessed what, when. Exportable logs for SOC2 and compliance.

//Use Cases

Built for teams that need control.

Internal Developer Platform

Wrap internal APIs, databases, and CI/CD pipelines in MCP servers. Your engineering team gets AI-powered access to company infrastructure — without exposing anything externally.

Company Knowledge Base

Private RAG over Confluence, Notion, Slack, and internal docs. AI assistants with real institutional knowledge — access limited to authorized team members only.

Customer-Facing AI Features

Ship AI features powered by private MCP skills. Your customers interact through your product UI — the MCP layer stays invisible and secure behind your workspace.

Not everything belongs in public.

Give your team private, managed MCP tools with enterprise-grade access control and full observability.