Skip to main content
Glama
README.md
<p align="center">
  <h1 align="center">🚀 VegaMCP v7.2</h1>
  <p align="center">
    <strong>Full Spectrum Testing Edition — AI Agent Swarm Platform</strong>
  </p>
  <p align="center">
    <a href="FEATURES.md">Features</a> •
    <a href="#quick-start">Quick Start</a> •
    <a href="#configuration">Configuration</a>
  </p>
</p>

---

> **VegaMCP** is a production-grade MCP (Model Context Protocol) server providing an autonomous AI agent swarm, persistent semantic memory, browser automation, multi-model reasoning, security gateway, agent graphs, zero-trust identity, A2A protocol, Docker sandbox v5.0, AI-first testing suite (mobile, web, API, desktop, accessibility, security, visual), and 78+ tools — all accessible via any MCP-compatible client.
> 
> *Version 7.2 (Sovereign Intelligence) introduces the production Claw Command Center, ultra-fast SQLite chat syncing, local vector Semantic Memory, LLM Output Evaluation, and 6 Unified Omni-Clusters.*

## 📖 Complete Features
**Read [FEATURES.md](./FEATURES.md) for a comprehensive list of all 17 unified V7 capability clusters including Docker Sandbox v5.0.**

## Quick Start

### Prerequisites
- **Node.js** 20+
- **npm** 9+

### Installation

```bash
# Clone the repository
git clone https://github.com/Pastarafian/VegaMCP.git
cd VegaMCP

# Install dependencies
npm install

# Copy environment config
cp .env.example .env
# Edit .env with your API keys

# Build
npm run build
```

### Connect to VS Code (Gemini / Copilot)

Create `.vscode/mcp.json` in your workspace:

```json
{
  "servers": {
    "REDACTED": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/VegaMCP/build/index.js"],
      "cwd": "/path/to/VegaMCP"
    }
  }
}
```

> **Note:** API keys can be set in the `env` block of `mcp.json` or in the `.env` file (`dotenv` is loaded automatically).

## Configuration

Copy `.env.example` to `.env` and configure:

```bash
# At least one reasoning model key required
OPENROUTER_API_KEY=          # Supports ALL models via OpenRouter
DEEPSEEK_API_KEY=            # Direct DeepSeek API (R1 + Chat)
KIMI_API_KEY=                # Kimi K2.5 for coding

# Optional integrations
GITHUB_TOKEN=                # GitHub API (60→5000 req/hr)
TAVILY_API_KEY=              # AI-powered web search
SEARXNG_URL=                 # Self-hosted search fallback
SENTRY_AUTH_TOKEN=           # Error tracking
SENTRY_ORG=
SENTRY_PROJECT=

# Budget controls
TOKEN_DAILY_BUDGET_USD=5.00
TOKEN_HOURLY_BUDGET_USD=1.00

# Tool profiles
VEGAMCP_TOOL_PROFILE=full    # full | minimal | research | coding | ops
```

## Project Structure

```
VegaMCP/
├── src/
│   ├── index.ts                     # Server entry point + hub router
│   ├── mcp-extensions.ts            # Sampling, logging, progress, roots
│   ├── mcp-protocol/               # v6.0 / v7.0 protocol modules
│   ├── db/                          # SQLite + vector store
│   ├── swarm/                       # Agent swarm (10 agents)
│   ├── tools/                       # All tool implementations
│   ├── resources/                   # MCP resource providers
│   ├── prompts/                     # MCP prompt templates
│   └── security/                    # Rate limiter, validator, guard
├── .env.example                     # Environment template
├── package.json
└── tsconfig.json
```

## License

MIT

---

<p align="center">
  Built with TypeScript • MCP SDK • sql.js • Playwright • DeepSeek • A2A Protocol
</p>

TDQS

C2.2/5.0

Scored across 6 tools

Disambiguation1/5

Tools have extremely broad and overlapping descriptions (e.g., omni_assistant and omni_research both cover RAG and knowledge; omni_automation and omni_swarm both involve orchestration). An agent would struggle to distinguish which tool to use for a given task.

Naming Consistency4/5

All tools follow a consistent 'omni_<noun>' pattern. However, the nouns (assistant, automation, research, swarm, systems, testing) are vague and do not clearly indicate the tool's unique scope.

Tool Count2/5

With only 6 tools covering an enormous range of capabilities (from AI assistants to infrastructure to testing), the set is under-scoped. Each tool effectively contains multiple distinct functionalities that should probably be separate tools.

Completeness3/5

The tool set covers many domains (AI, automation, research, orchestration, infrastructure, testing), but there are noticeable gaps such as dedicated monitoring, deep analytics, or security scanning beyond basic mentions. The overlap also indicates incomplete separation of concerns.

Maintenance

ActivityInactive
ResponsivenessNo issues