DeployStack - MCP Management Platform

🚀 Try it out · 🌐 Website · 📚 Documentation · Roadmap · Discord

Centralized MCP server management, credential vault, governance, and token optimization for developers and enterprises.

The Problem

MCP changes how AI agents use tools, but it has created two critical challenges:

Problem 1: Management Chaos

Credential Sprawl: Developers copy and paste sensitive API keys and tokens into insecure local configuration files, creating a huge security risk.
No Governance: Who is using which tools? Which agent is accessing sensitive customer data? Without a central control plane, companies are blind.
Developer Friction: Developers spend hours managing complex configurations for dozens of tools, a process that is both tedious and error-prone. Onboarding a new developer is a nightmare of configuration management.
Inconsistent Environments: Every developer has a slightly different local setup, leading to "it works on my machine" problems and configuration drift.

Problem 2: Context Window Consumption Crisis

Token Bloat: Each MCP server adds 5-15 tools to context. With 10 servers, that's 75,000+ tokens consumed before any work begins.
Performance Degradation: LLM accuracy drops significantly after 20-40 tools are loaded.
Hard Limits: Tools like Cursor enforce a 40-tool maximum, forcing developers to disable useful servers.
Cannot Scale: Teams hit performance walls when trying to use more than 5-8 MCP servers simultaneously.

Real-world example: Claude Code users report 82,000 tokens (41% of context window) consumed by MCP tools at startup, leaving only 6% for actual work.

DeployStack solves both problems with a complete MCP management platform and intelligent context window optimization.

Who DeployStack Is For

For Platform / DevOps Teams

End credential chaos: Move API keys from Slack DMs and .env files into an encrypted vault with automatic injection
Control MCP access: Role-based permissions determine who can use which MCP servers and tools
Prevent data exposure: Team isolation and audit logging show exactly what tools accessed what data
Centralize configuration: One source of truth instead of N developers × M configurations

For Developers

Zero setup: Add one URL to VS Code, get access to all team MCP tools instantly
No local installs: No npm install, no process management, no port conflicts
Just works: Same configuration everywhere - no more "works on my machine" debugging
Focus on code: Security and credentials are handled for you

For Engineering Managers

1-click team onboarding: New developer? They're productive with MCP tools in minutes, not hours
Reduce AI costs: 98% token reduction means lower API bills and better LLM performance
Full visibility: See which tools your team uses, how often, and what they access
Offboarding safety: When someone leaves, revoke access instantly - no credential rotation nightmare

🚀 How It Works: A Quick Tour

Global Satellite (Zero Installation)

Admin: Creates account at cloud.deploystack.io, adds MCP servers (like GitHub), stores API tokens securely in DeployStack vault
Developer: Gets OAuth credentials from dashboard
VS Code Setup: Adds one URL to MCP configuration: https://satellite.deploystack.io/mcp
Instant Access: All team MCP tools work immediately - no installation, no local processes
The Magic:
- VS Code calls satellite via HTTPS (like any other API)
- Satellite receives request, checks team permissions
- Spawns MCP server process with injected credentials
- Returns results via standard HTTP response
- Automatically shuts down idle processes to save resources

Before DeployStack:

# Manual setup nightmare
npm install -g some-mcp-cli
some-mcp configure --api-key=xxx
# Repeat for every tool, every developer

After DeployStack:

{
  "mcpServers": {
    "deploystack": {
      "type": "http",
      "url": "https://satellite.deploystack.io/mcp"
    }
  }
}

Key Features

🎯 Intelligent Context Window Optimization

DeployStack includes a hierarchical router that reduces MCP token consumption by 90%+:

Traditional Approach:

10 MCP servers × 15 tools = 150 tools loaded
150 tools × 500 tokens = 75,000 tokens consumed
Result: 37.5% of context window gone before you start

DeployStack Hierarchical Router:

Exposes only 2 meta-tools: discover_mcp_tools and execute_mcp_tool
2 tools × 686 tokens = 1372 tokens consumed
Result: 0.686% of context window used
Token Reduction: 98.3% ✅ How it works:

LLM calls discover_mcp_tools(query) - "Find GitHub tools"
Router searches across all team MCP servers, returns relevant tool paths
LLM calls execute_mcp_tool(path, args) with selected tool
Router executes the actual MCP tool and returns results

This means you can scale from 3 to 100+ MCP servers without degrading LLM performance.

🚀 Zero Installation Experience

Before DeployStack:

npm install -g some-mcp-cli
some-mcp configure --api-key=xxx
# Repeat for every tool, every developer

After DeployStack:

{
  "mcpServers": {
    "deploystack": {
      "type": "http",
      "url": "https://satellite.deploystack.io/mcp"
    }
  }
}

🔒 Enterprise Security & Governance

Credential Vault: Encrypted storage with automatic injection
Team Isolation: Complete separation between teams
Audit Logging: Track every tool interaction
Role-Based Access: Fine-grained permissions

Architecture: Two Ways to Deploy

Global Satellites (Managed by DeployStack)

Zero Installation: Just add URL to VS Code
Context Optimization: Hierarchical routing reduces token usage by 90%+
Freemium Model: Free tier with basic MCP servers
Instant Access: Pre-configured tools ready to use
Multi-tenant: Resource isolation between teams
Example: https://satellite.deploystack.io/mcp

Team Satellites (Deploy Your Own)

Enterprise Security: On-premise deployment within your network
Internal Access: Connect to company databases, APIs, file systems
Complete Isolation: Full team separation using Linux containers
Same Performance: Hierarchical routing reduces context consumption
GitHub Actions Style: Simple deployment with Docker
Example: https://team-satellite.yourcompany.com/mcp

Technical Flow

VS Code → HTTPS Request → DeployStack Satellite → MCP Server Process → External API
         ↓                 ↓                       ↓                   ↓
    (OAuth JWT)     (Team Permissions)      (Credential Injection)  (GitHub/etc)

Core Components:

Control Plane: cloud.deploystack.io - web dashboard for teams, credentials, configurations
Satellites: Managed MCP infrastructure - no local processes, just HTTPS
Process Manager: On-demand MCP server spawning with X-minute idle timeout
Team Isolation: Complete separation using Linux namespaces and resource limits

Why Satellite vs Traditional Gateway?

User Experience:

Gateway: "Install our CLI tool, configure localhost, manage processes"
Satellite: "Add this URL: https://satellite.deploystack.io/mcp"

Why This Matters:

Adoption Friction Kills Everything: Every MCP solution requiring CLI installation loses interested developers
"Another Local Proxy" Fatigue: Market saturated with similar gateway solutions requiring installation
Teams Can't Scale: Complex setups prevent MCP adoption beyond early adopters
Enterprise Path: Natural progression from managed service to on-premise deployment

Technical Benefits:

No Local Dependencies: No Node.js, npm, or port management
Familiar Pattern: Works like OpenAI API, Claude API, or any SaaS
Auto-scaling: Handles traffic spikes automatically
High Availability: multi-region deployment
Instant Updates: No user installations required for new features

Roadmap

Phase 1: Foundation (Completed)

[Done] Deployed cloud.deploystack.io hosted version with backend and frontend
[Done] Implemented a secure user and team management system with roles and permissions
[Done] Integrated OAuth for secure logins (e.g., GitHub)
[Done] Created the initial MCP Server Catalog for tool discovery
[Done] Established documentation and self-hosted Docker support
[Done] PostgreSQL-only database architecture - migrated from multi-database support (SQLite/Turso/PostgreSQL) to PostgreSQL-only for simplified maintenance and enterprise scalability

Phase 2: Enterprise Governance (Completed)

[Done] Auto-install MCP servers for new users with admin-controlled defaults
[Done] Featured MCP servers filtering for improved tool discovery
[Done] Global Event Bus System - event-driven architecture with plugin integration
[Done] Three-Tier MCP Configuration Architecture - complete database schema redesign separating template, team, and user-level configurations
[Done] Multi-User Configuration Management - support for multiple users within teams, each with personalized device-specific configurations
[Done] Advanced MCP Argument & Environment Variable Handling - complete service layer with schema validation and runtime configuration assembly
[Done] HTTP Headers & URL Query Parameters Support - three-tier configuration for HTTP/SSE transport with intelligent URL parsing, automatic secret detection, and transport type validation
[Done] Selective Secret Masking in Satellite Logs - backend sends secret metadata to satellites for selective masking of sensitive query parameters, headers, and environment variables in logs (first 3 chars + *****), preventing credential exposure in log files and monitoring systems

Phase 3: Satellite Infrastructure (Completed)

[Done] Global Satellite Infrastructure - managed MCP servers via HTTPS
[Done] Zero-Installation Experience - just add URL to VS Code
[Done] OAuth Authentication - token-based auth
[Done] Satellite Pairing Security - JWT-based token registration system for secure satellite onboarding
[Done] Public Launch - production satellite for community use
[Done] Resource Management - process isolation (remote MCP) and limits
[Done] GitHub README and Stars Integration - automatic GitHub data fetching, secure storage, XSS prevention, DoS protection, and audit logging for MCP server catalog enhancement
[Done] Background Job Queue System - complete 4-phase custom PostgreSQL-based job queue with worker infrastructure, admin API, frontend monitoring UI, and documentation for long-running tasks
[Done] Cron Job Scheduling System - recurring task scheduler using node-cron with integration into the job queue system, standard cron expression support, automatic lifecycle management, and complete separation of scheduling logic from execution for reliability and monitoring
[Done] Frontend Syntax Highlighting - reusable CodeHighlight component with Prism.js for JSON, JavaScript, TypeScript, Bash, and YAML code blocks
[Done] Resource Management - process isolation (stdio) and limits
[Done] MCP Registry - integration of the official MCP Registry

Phase 4: Context Window Optimization (Current Priority)

Goal: Reduce MCP token consumption by 90%+ through intelligent hierarchical routing

[Done] Hierarchical Router Implementation - 2-tool pattern with discover_mcp_tools and execute_mcp_tool achieving 99.5% token reduction
[Done] Semantic Tool Search - natural language queries with Fuse.js fuzzy matching across all installed MCP servers (2-5ms performance)
[Done] Tool Discovery API - returns tool paths, descriptions, transport types, and relevance scores
[Done] Smart Tool Execution - automatic routing to stdio or HTTP/SSE backends with credential injection
[Done] Performance Benchmarks - achieved 99.5% token reduction (exceeded 90%+ target): 2 meta-tools (350 tokens) vs 150 tools (75,000 tokens)
[Done] MCP Tool Metadata Collection - automatic tool discovery with token counting, event-driven metadata sync from satellites to backend, per-installation tool storage with descriptions and input schemas
[Done] Tool Display & Analytics API - team-aware endpoints for fetching tool lists per installation and aggregated token savings across all team installations
[Done] Token Analytics Dashboard - complete statistics dashboard with visual token comparison (stacked bar chart), 4 summary cards (installations, tools, savings %, DeployStack usage), side-by-side traditional vs hierarchical comparison, and expandable installation breakdown table with per-tool token counts
[To Do] OAuth 2.1 Authentication for MCP Servers - enable DeployStack to connect to OAuth-protected MCP servers (Box, Linear, GitHub Copilot) with on-the-fly endpoint discovery, PKCE flow, encrypted token storage, automatic refresh, and browser popup authentication
[To Do] Optimization Recommendations - suggest which servers to disable based on usage patterns
[To Do] Documentation & Case Study - technical deep-dive blog post with real-world metrics

Result: Teams can now scale from 3 to 100+ MCP servers without performance degradation. Context window consumption reduced from 37.5% to 0.175%. Full visibility into tool availability and token usage per installation.

Phase 5: Advanced Governance (Next 90 Days)

[In Progress] Build out Audit Logging features in the cloud UI
[Done] Develop Analytics dashboards for tool usage and performance
[Done] Per-tool access controls - team admins can disable individual tools per MCP installation
[To Do] Implement advanced policy controls (e.g., rate limiting, request validation)
[Done] Improve the searchable MCP Server Catalog with Featured page and category browsing
[Done] AI Instructions - ready-to-copy instruction files for AI coding assistants
[To Do] Deeper integration with IDEs and AI agent frameworks
[To Do] Per-team token budgets and cost attribution
[To Do] AI-powered tool recommendations based on conversation context

Phase 6: Advanced Architecture (Completed)

[Done] Multi-Transport Support - SSE, Streamable HTTP, Direct HTTP protocols
[Done] Real-Time Command Orchestration - instant status feedback
[Done] Satellite Job System - recurring background task management with JobManager, abstract BaseJob class, automatic error handling, execution metrics tracking, and extensible architecture for health checks, cleanup tasks, and periodic maintenance operations
[Done] Satellite Backend Events System - real-time event processing with convention-based auto-discovery handler pattern, batch processing (1-100 events), partial success handling, JSON schema validation per event type, and extensible architecture supporting MCP client connections, tool executions, server crashes, and custom event types
[Done] MCP Client Activity Tracking - personal dashboard feature tracking active MCP clients per user across all components (backend database with mcpClientActivity table, satellite in-memory tracker with 30-second background job reporting via event system, dashboard API endpoint with dual authentication and pagination, client name detection from OAuth/headers/user-agent)
[Done] Time-Series Metrics System - production-ready metrics infrastructure with 15-minute bucket aggregation, 3-day retention, automated cleanup
[Done] PostgreSQL-Only Database Architecture - complete migration to PostgreSQL with simplified schema management, environment-based configuration, streamlined migration system, and production-ready setup for enterprise scalability

Phase 7: Enterprise Features (Future)

[To Do] Complete Monitoring - satellite health and usage analytics
[To Do] Enterprise Security - advanced audit logging and compliance features
[To Do] Team Satellites - customer-deployed satellites for enterprise (security infrastructure completed, deployment tooling pending)
[To Do] Advanced Team Isolation - Linux namespaces and cgroups
[To Do] On-Premise Deployment - GitHub Actions runner-style deployment
[To Do] Enterprise Authentication - SSO integration (SAML, OIDC)

Phase 8: Ecosystem Expansion (Future)

[To Do] Multi-region satellite deployment
[To Do] AI agent framework integrations
[To Do] Performance SLAs and guarantees
[To Do] SOC 2 Type II certification

Try DeployStack

Get Started in 3 Minutes

Sign up: Create free account at cloud.deploystack.io
Get credentials: Copy OAuth client credentials from dashboard
Configure VS Code: Add satellite URL to MCP settings
Start using MCP tools: Instant access to team tools

Contributing

We're building the future of MCP adoption. Want to help?

Fork the repository
Create feature branch: git checkout -b feature/your-enhancement
Follow TypeScript and ESLint conventions
Add tests for new functionality
Submit pull request with clear description

Areas we need help:

Satellite infrastructure and scaling
MCP server integrations and testing
Documentation and developer experience
Enterprise features and security

License

Server Side Public License (SSPL) v1 - see LICENSE file for details.

DeployStack - MCP Management Platform

🚀 Try it out · 🌐 Website · 📚 Documentation · Roadmap · Discord

Centralized MCP server management, credential vault, governance, and token optimization for developers and enterprises.

The Problem

MCP changes how AI agents use tools, but it has created two critical challenges:

Problem 1: Management Chaos

Credential Sprawl: Developers copy and paste sensitive API keys and tokens into insecure local configuration files, creating a huge security risk.
No Governance: Who is using which tools? Which agent is accessing sensitive customer data? Without a central control plane, companies are blind.
Developer Friction: Developers spend hours managing complex configurations for dozens of tools, a process that is both tedious and error-prone. Onboarding a new developer is a nightmare of configuration management.
Inconsistent Environments: Every developer has a slightly different local setup, leading to "it works on my machine" problems and configuration drift.

Problem 2: Context Window Consumption Crisis

Token Bloat: Each MCP server adds 5-15 tools to context. With 10 servers, that's 75,000+ tokens consumed before any work begins.
Performance Degradation: LLM accuracy drops significantly after 20-40 tools are loaded.
Hard Limits: Tools like Cursor enforce a 40-tool maximum, forcing developers to disable useful servers.
Cannot Scale: Teams hit performance walls when trying to use more than 5-8 MCP servers simultaneously.

Real-world example: Claude Code users report 82,000 tokens (41% of context window) consumed by MCP tools at startup, leaving only 6% for actual work.

DeployStack solves both problems with a complete MCP management platform and intelligent context window optimization.

Who DeployStack Is For

For Platform / DevOps Teams

End credential chaos: Move API keys from Slack DMs and .env files into an encrypted vault with automatic injection
Control MCP access: Role-based permissions determine who can use which MCP servers and tools
Prevent data exposure: Team isolation and audit logging show exactly what tools accessed what data
Centralize configuration: One source of truth instead of N developers × M configurations

For Developers

Zero setup: Add one URL to VS Code, get access to all team MCP tools instantly
No local installs: No npm install, no process management, no port conflicts
Just works: Same configuration everywhere - no more "works on my machine" debugging
Focus on code: Security and credentials are handled for you

For Engineering Managers

1-click team onboarding: New developer? They're productive with MCP tools in minutes, not hours
Reduce AI costs: 98% token reduction means lower API bills and better LLM performance
Full visibility: See which tools your team uses, how often, and what they access
Offboarding safety: When someone leaves, revoke access instantly - no credential rotation nightmare

🚀 How It Works: A Quick Tour

Global Satellite (Zero Installation)

Admin: Creates account at cloud.deploystack.io, adds MCP servers (like GitHub), stores API tokens securely in DeployStack vault
Developer: Gets OAuth credentials from dashboard
VS Code Setup: Adds one URL to MCP configuration: https://satellite.deploystack.io/mcp
Instant Access: All team MCP tools work immediately - no installation, no local processes
The Magic:
- VS Code calls satellite via HTTPS (like any other API)
- Satellite receives request, checks team permissions
- Spawns MCP server process with injected credentials
- Returns results via standard HTTP response
- Automatically shuts down idle processes to save resources

Before DeployStack:

# Manual setup nightmare
npm install -g some-mcp-cli
some-mcp configure --api-key=xxx
# Repeat for every tool, every developer

After DeployStack:

{
  "mcpServers": {
    "deploystack": {
      "type": "http",
      "url": "https://satellite.deploystack.io/mcp"
    }
  }
}

Key Features

🎯 Intelligent Context Window Optimization

DeployStack includes a hierarchical router that reduces MCP token consumption by 90%+:

Traditional Approach:

10 MCP servers × 15 tools = 150 tools loaded
150 tools × 500 tokens = 75,000 tokens consumed
Result: 37.5% of context window gone before you start

DeployStack Hierarchical Router:

Exposes only 2 meta-tools: discover_mcp_tools and execute_mcp_tool
2 tools × 686 tokens = 1372 tokens consumed
Result: 0.686% of context window used
Token Reduction: 98.3% ✅ How it works:

LLM calls discover_mcp_tools(query) - "Find GitHub tools"
Router searches across all team MCP servers, returns relevant tool paths
LLM calls execute_mcp_tool(path, args) with selected tool
Router executes the actual MCP tool and returns results

This means you can scale from 3 to 100+ MCP servers without degrading LLM performance.

🚀 Zero Installation Experience

Before DeployStack:

npm install -g some-mcp-cli
some-mcp configure --api-key=xxx
# Repeat for every tool, every developer

After DeployStack:

{
  "mcpServers": {
    "deploystack": {
      "type": "http",
      "url": "https://satellite.deploystack.io/mcp"
    }
  }
}

🔒 Enterprise Security & Governance

Credential Vault: Encrypted storage with automatic injection
Team Isolation: Complete separation between teams
Audit Logging: Track every tool interaction
Role-Based Access: Fine-grained permissions

Architecture: Two Ways to Deploy

Global Satellites (Managed by DeployStack)

Zero Installation: Just add URL to VS Code
Context Optimization: Hierarchical routing reduces token usage by 90%+
Freemium Model: Free tier with basic MCP servers
Instant Access: Pre-configured tools ready to use
Multi-tenant: Resource isolation between teams
Example: https://satellite.deploystack.io/mcp

Team Satellites (Deploy Your Own)

Enterprise Security: On-premise deployment within your network
Internal Access: Connect to company databases, APIs, file systems
Complete Isolation: Full team separation using Linux containers
Same Performance: Hierarchical routing reduces context consumption
GitHub Actions Style: Simple deployment with Docker
Example: https://team-satellite.yourcompany.com/mcp

Technical Flow

VS Code → HTTPS Request → DeployStack Satellite → MCP Server Process → External API
         ↓                 ↓                       ↓                   ↓
    (OAuth JWT)     (Team Permissions)      (Credential Injection)  (GitHub/etc)

Core Components:

Control Plane: cloud.deploystack.io - web dashboard for teams, credentials, configurations
Satellites: Managed MCP infrastructure - no local processes, just HTTPS
Process Manager: On-demand MCP server spawning with X-minute idle timeout
Team Isolation: Complete separation using Linux namespaces and resource limits

Why Satellite vs Traditional Gateway?

User Experience:

Gateway: "Install our CLI tool, configure localhost, manage processes"
Satellite: "Add this URL: https://satellite.deploystack.io/mcp"

Why This Matters:

Adoption Friction Kills Everything: Every MCP solution requiring CLI installation loses interested developers
"Another Local Proxy" Fatigue: Market saturated with similar gateway solutions requiring installation
Teams Can't Scale: Complex setups prevent MCP adoption beyond early adopters
Enterprise Path: Natural progression from managed service to on-premise deployment

Technical Benefits:

No Local Dependencies: No Node.js, npm, or port management
Familiar Pattern: Works like OpenAI API, Claude API, or any SaaS
Auto-scaling: Handles traffic spikes automatically
High Availability: multi-region deployment
Instant Updates: No user installations required for new features

Roadmap

Phase 1: Foundation (Completed)

[Done] Deployed cloud.deploystack.io hosted version with backend and frontend
[Done] Implemented a secure user and team management system with roles and permissions
[Done] Integrated OAuth for secure logins (e.g., GitHub)
[Done] Created the initial MCP Server Catalog for tool discovery
[Done] Established documentation and self-hosted Docker support
[Done] PostgreSQL-only database architecture - migrated from multi-database support (SQLite/Turso/PostgreSQL) to PostgreSQL-only for simplified maintenance and enterprise scalability

Phase 2: Enterprise Governance (Completed)

[Done] Auto-install MCP servers for new users with admin-controlled defaults
[Done] Featured MCP servers filtering for improved tool discovery
[Done] Global Event Bus System - event-driven architecture with plugin integration
[Done] Three-Tier MCP Configuration Architecture - complete database schema redesign separating template, team, and user-level configurations
[Done] Multi-User Configuration Management - support for multiple users within teams, each with personalized device-specific configurations
[Done] Advanced MCP Argument & Environment Variable Handling - complete service layer with schema validation and runtime configuration assembly
[Done] HTTP Headers & URL Query Parameters Support - three-tier configuration for HTTP/SSE transport with intelligent URL parsing, automatic secret detection, and transport type validation
[Done] Selective Secret Masking in Satellite Logs - backend sends secret metadata to satellites for selective masking of sensitive query parameters, headers, and environment variables in logs (first 3 chars + *****), preventing credential exposure in log files and monitoring systems

Phase 3: Satellite Infrastructure (Completed)

[Done] Global Satellite Infrastructure - managed MCP servers via HTTPS
[Done] Zero-Installation Experience - just add URL to VS Code
[Done] OAuth Authentication - token-based auth
[Done] Satellite Pairing Security - JWT-based token registration system for secure satellite onboarding
[Done] Public Launch - production satellite for community use
[Done] Resource Management - process isolation (remote MCP) and limits
[Done] GitHub README and Stars Integration - automatic GitHub data fetching, secure storage, XSS prevention, DoS protection, and audit logging for MCP server catalog enhancement
[Done] Background Job Queue System - complete 4-phase custom PostgreSQL-based job queue with worker infrastructure, admin API, frontend monitoring UI, and documentation for long-running tasks
[Done] Cron Job Scheduling System - recurring task scheduler using node-cron with integration into the job queue system, standard cron expression support, automatic lifecycle management, and complete separation of scheduling logic from execution for reliability and monitoring
[Done] Frontend Syntax Highlighting - reusable CodeHighlight component with Prism.js for JSON, JavaScript, TypeScript, Bash, and YAML code blocks
[Done] Resource Management - process isolation (stdio) and limits
[Done] MCP Registry - integration of the official MCP Registry

Phase 4: Context Window Optimization (Current Priority)

Goal: Reduce MCP token consumption by 90%+ through intelligent hierarchical routing

[Done] Hierarchical Router Implementation - 2-tool pattern with discover_mcp_tools and execute_mcp_tool achieving 99.5% token reduction
[Done] Semantic Tool Search - natural language queries with Fuse.js fuzzy matching across all installed MCP servers (2-5ms performance)
[Done] Tool Discovery API - returns tool paths, descriptions, transport types, and relevance scores
[Done] Smart Tool Execution - automatic routing to stdio or HTTP/SSE backends with credential injection
[Done] Performance Benchmarks - achieved 99.5% token reduction (exceeded 90%+ target): 2 meta-tools (350 tokens) vs 150 tools (75,000 tokens)
[Done] MCP Tool Metadata Collection - automatic tool discovery with token counting, event-driven metadata sync from satellites to backend, per-installation tool storage with descriptions and input schemas
[Done] Tool Display & Analytics API - team-aware endpoints for fetching tool lists per installation and aggregated token savings across all team installations
[Done] Token Analytics Dashboard - complete statistics dashboard with visual token comparison (stacked bar chart), 4 summary cards (installations, tools, savings %, DeployStack usage), side-by-side traditional vs hierarchical comparison, and expandable installation breakdown table with per-tool token counts
[To Do] OAuth 2.1 Authentication for MCP Servers - enable DeployStack to connect to OAuth-protected MCP servers (Box, Linear, GitHub Copilot) with on-the-fly endpoint discovery, PKCE flow, encrypted token storage, automatic refresh, and browser popup authentication
[To Do] Optimization Recommendations - suggest which servers to disable based on usage patterns
[To Do] Documentation & Case Study - technical deep-dive blog post with real-world metrics

Phase 5: Advanced Governance (Next 90 Days)

[In Progress] Build out Audit Logging features in the cloud UI
[Done] Develop Analytics dashboards for tool usage and performance
[Done] Per-tool access controls - team admins can disable individual tools per MCP installation
[To Do] Implement advanced policy controls (e.g., rate limiting, request validation)
[Done] Improve the searchable MCP Server Catalog with Featured page and category browsing
[Done] AI Instructions - ready-to-copy instruction files for AI coding assistants
[To Do] Deeper integration with IDEs and AI agent frameworks
[To Do] Per-team token budgets and cost attribution
[To Do] AI-powered tool recommendations based on conversation context

Phase 6: Advanced Architecture (Completed)

[Done] Multi-Transport Support - SSE, Streamable HTTP, Direct HTTP protocols
[Done] Real-Time Command Orchestration - instant status feedback
[Done] Satellite Job System - recurring background task management with JobManager, abstract BaseJob class, automatic error handling, execution metrics tracking, and extensible architecture for health checks, cleanup tasks, and periodic maintenance operations
[Done] Satellite Backend Events System - real-time event processing with convention-based auto-discovery handler pattern, batch processing (1-100 events), partial success handling, JSON schema validation per event type, and extensible architecture supporting MCP client connections, tool executions, server crashes, and custom event types
[Done] MCP Client Activity Tracking - personal dashboard feature tracking active MCP clients per user across all components (backend database with mcpClientActivity table, satellite in-memory tracker with 30-second background job reporting via event system, dashboard API endpoint with dual authentication and pagination, client name detection from OAuth/headers/user-agent)
[Done] Time-Series Metrics System - production-ready metrics infrastructure with 15-minute bucket aggregation, 3-day retention, automated cleanup
[Done] PostgreSQL-Only Database Architecture - complete migration to PostgreSQL with simplified schema management, environment-based configuration, streamlined migration system, and production-ready setup for enterprise scalability

Phase 7: Enterprise Features (Future)

[To Do] Complete Monitoring - satellite health and usage analytics
[To Do] Enterprise Security - advanced audit logging and compliance features
[To Do] Team Satellites - customer-deployed satellites for enterprise (security infrastructure completed, deployment tooling pending)
[To Do] Advanced Team Isolation - Linux namespaces and cgroups
[To Do] On-Premise Deployment - GitHub Actions runner-style deployment
[To Do] Enterprise Authentication - SSO integration (SAML, OIDC)

Phase 8: Ecosystem Expansion (Future)

[To Do] Multi-region satellite deployment
[To Do] AI agent framework integrations
[To Do] Performance SLAs and guarantees
[To Do] SOC 2 Type II certification

Try DeployStack

Get Started in 3 Minutes

Sign up: Create free account at cloud.deploystack.io
Get credentials: Copy OAuth client credentials from dashboard
Configure VS Code: Add satellite URL to MCP settings
Start using MCP tools: Instant access to team tools

Contributing

We're building the future of MCP adoption. Want to help?

Fork the repository
Create feature branch: git checkout -b feature/your-enhancement
Follow TypeScript and ESLint conventions
Add tests for new functionality
Submit pull request with clear description

Areas we need help:

Satellite infrastructure and scaling
MCP server integrations and testing
Documentation and developer experience
Enterprise features and security

License

Server Side Public License (SSPL) v1 - see LICENSE file for details.

deploystack

更新履歴

DeployStack - MCP Management Platform

The Problem

Problem 1: Management Chaos

Problem 2: Context Window Consumption Crisis

Who DeployStack Is For

For Platform / DevOps Teams

For Developers

For Engineering Managers

🚀 How It Works: A Quick Tour

Global Satellite (Zero Installation)

Key Features

🎯 Intelligent Context Window Optimization

🚀 Zero Installation Experience

🔒 Enterprise Security & Governance

Architecture: Two Ways to Deploy

Global Satellites (Managed by DeployStack)

Team Satellites (Deploy Your Own)

Technical Flow

Why Satellite vs Traditional Gateway?

Roadmap

Phase 1: Foundation (Completed)

Phase 2: Enterprise Governance (Completed)

Phase 3: Satellite Infrastructure (Completed)

Phase 4: Context Window Optimization (Current Priority)

Phase 5: Advanced Governance (Next 90 Days)

Phase 6: Advanced Architecture (Completed)

Phase 7: Enterprise Features (Future)

Phase 8: Ecosystem Expansion (Future)

Try DeployStack

Get Started in 3 Minutes

Links

Contributing

License

更新履歴

DeployStack - MCP Management Platform

The Problem

Problem 1: Management Chaos

Problem 2: Context Window Consumption Crisis

Who DeployStack Is For

For Platform / DevOps Teams

For Developers

For Engineering Managers

🚀 How It Works: A Quick Tour

Global Satellite (Zero Installation)

Key Features

🎯 Intelligent Context Window Optimization

🚀 Zero Installation Experience

🔒 Enterprise Security & Governance

Architecture: Two Ways to Deploy

Global Satellites (Managed by DeployStack)

Team Satellites (Deploy Your Own)

Technical Flow

Why Satellite vs Traditional Gateway?

Roadmap

Phase 1: Foundation (Completed)

Phase 2: Enterprise Governance (Completed)

Phase 3: Satellite Infrastructure (Completed)

Phase 4: Context Window Optimization (Current Priority)

Phase 5: Advanced Governance (Next 90 Days)

Phase 6: Advanced Architecture (Completed)

Phase 7: Enterprise Features (Future)

Phase 8: Ecosystem Expansion (Future)

Try DeployStack

Get Started in 3 Minutes

Links

Contributing

License