Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,12 +22,14 @@ DeployStack is **The First MCP-as-a-Service Platform**. We turn MCP from "comple
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.
Expand Down Expand Up @@ -81,17 +83,20 @@ some-mcp configure --api-key=xxx
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 × 175 tokens = 350 tokens consumed
- Result: 0.175% of context window used
- **Token Reduction: 99.5%** ✅

**How it works:**

1. LLM calls `discover_mcp_tools(query)` - "Find GitHub tools"
2. Router searches across all team MCP servers, returns relevant tool paths
3. LLM calls `execute_mcp_tool(path, args)` with selected tool
Expand All @@ -102,13 +107,15 @@ This means you can scale from 3 to 100+ MCP servers without degrading LLM perfor
### 🚀 Zero Installation Experience

**Before DeployStack:**

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

**After DeployStack:**

```json
{
"mcpServers": {
Expand Down
2 changes: 1 addition & 1 deletion package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

15 changes: 15 additions & 0 deletions services/satellite/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,20 @@
# Changelog

## 0.7.0 (2025-11-03)

* feat(backend): added mcp server source type ([a9429a6](https://github.com/deploystackio/deploystack/commit/a9429a6))
* feat(backend): resolve plugin path determination for production environment ([bb0f504](https://github.com/deploystackio/deploystack/commit/bb0f504))
* feat(frontend): add source field to MCP server and display in details ([2461f88](https://github.com/deploystackio/deploystack/commit/2461f88))
* feat(satellite): implement hierarchical tool search with Fuse.js ([5545c20](https://github.com/deploystackio/deploystack/commit/5545c20))
* docs(all): update README to clarify MCP challenges and solutions ([46ce1e9](https://github.com/deploystackio/deploystack/commit/46ce1e9))
* fix(backend): update welcome email instructions for MCP client setup ([2da79a9](https://github.com/deploystackio/deploystack/commit/2da79a9))
* chore(all): bump tailwindcss from 4.1.14 to 4.1.15 ([8365aa2](https://github.com/deploystackio/deploystack/commit/8365aa2))
* chore(all): update dependencies across services ([1b1aba7](https://github.com/deploystackio/deploystack/commit/1b1aba7))
* chore(backend): release v0.39.0 ([2518339](https://github.com/deploystackio/deploystack/commit/2518339))
* chore(backend): release v0.39.0 ([3c783bb](https://github.com/deploystackio/deploystack/commit/3c783bb))
* chore(frontend): release v0.34.0 ([f0e29de](https://github.com/deploystackio/deploystack/commit/f0e29de))
* chore(frontend): release v0.34.0 ([fe6aec7](https://github.com/deploystackio/deploystack/commit/fe6aec7))

## 0.6.0 (2025-10-24)

* chore(backend): release v0.38.0 ([1bcf0db](https://github.com/deploystackio/deploystack/commit/1bcf0db))
Expand Down
2 changes: 1 addition & 1 deletion services/satellite/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@deploystack/satellite",
"version": "0.6.0",
"version": "0.7.0",
"description": "DeployStack Satellite - MCP Server Management Service",
"main": "dist/index.js",
"scripts": {
Expand Down
4 changes: 2 additions & 2 deletions services/satellite/src/config/version.ts
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@ export interface VersionInfo {

// This will be replaced by the build script
let versionData: VersionInfo = {
version: '0.6.0',
buildTime: '2025-10-24T20:14:19.079Z',
version: '0.7.0',
buildTime: '2025-11-03T22:40:42.479Z',
source: 'release'
};

Expand Down