VegaMCP
Provides Docker sandbox v5.0 for isolating AI agent processes and running containerized tasks.
Provides integration with the GitHub API for repository management and rate limit improvements.
Provides self-hosted web search fallback for enhanced search capabilities.
Provides error tracking and monitoring for server errors and performance issues.
Provides persistent semantic memory and ultra-fast chat syncing via SQLite.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@VegaMCP use the agent swarm to analyze my codebase"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 for a comprehensive list of all 17 unified V7 capability clusters including Docker Sandbox v5.0.
Related MCP server: Gravitas-Core-MCP
Quick Start
Prerequisites
Node.js 20+
npm 9+
Installation
# 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 buildConnect to VS Code (Gemini / Copilot)
Create .vscode/mcp.json in your workspace:
{
"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
envblock ofmcp.jsonor in the.envfile (dotenvis loaded automatically).
Configuration
Copy .env.example to .env and configure:
# 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 | opsProject 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.jsonLicense
MIT
Available Tools
6 toolsomni_assistantC
Core AI intelligence: reasoning, budget, auto-update, prompts, web search (speed/balanced/quality modes + domain filter), code analysis, docs, sequential thinking, expert toolkits, knowledge engine, memory graph, semantic memory (vector search), context7 library docs.
Inputs: tool_target (required), payload (required).
omni_automationC
Action & control: browser, workflow, filesystem, shell, git, MCP tasks, API requests, sandbox, watchers, webhooks, schedule, notify, the_claw, claw_command_center, vps_control, image_generation.
Inputs: tool_target (required), payload (required).
omni_researchD
Research & Science: graph RAG, agentic RAG, self evolution, hypothesis gen, quality gate, synthesis engine, LLM router, memory bridge, tool discovery, sentinel, LLM output evaluation.
Inputs: tool_target (required), payload (required).
omni_swarmC
Agent orchestration: swarm ops, agent intel/ops, A2A protocol, agent graphs, agentic sampling, multimodal embeddings, session manager, MCP relay.
Inputs: tool_target (required), payload (required).
omni_systemsD
Infrastructure: database, postgres_client, health check, analytics, skills, seed data, sentry, OAuth, gateway, tool search, MCP apps, vault, dynamic indexing.
Inputs: tool_target (required), payload (required).
omni_testingC
QA & Security: mobile, web, API, DB, server, desktop, accessibility, security, visual, advanced testing, security scanner, stress test, zero trust.
Inputs: tool_target (required), payload (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 6 tools
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.
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.
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.
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
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
- AlicenseBqualityDmaintenanceProduction-grade, autonomous Model Context Protocol (MCP) server that elevates AI models from stateless code generators into persistent, self-verifying software engineers.211MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceProduction-ready MCP server providing RAG, hierarchical memory, and 8+ tools for AI agents via the Model Context Protocol.54Apache 2.0