Multi-agent MCP Network
Multi-Agent MCP Network
A production-ready Model Context Protocol (MCP) server that exposes multiple specialized AI agents through a unified interface. Each agent is an expert in its domain and they collaborate through an intelligent orchestrator.
Architecture
┌─────────────────────┐
│ Client / MCP Host │
└──────────┬──────────┘
│
┌──────────▼──────────┐
│ REST API (Express) │
│ MCP Server (SDK) │
└──────────┬──────────┘
│
┌──────────▼──────────┐
│ Orchestrator │
│ ┌─────┴─────┐ │
│ │ Router │ │
│ │ Workflow │ │
│ └─────┬─────┘ │
└──────────┬──────────┘
│
┌────────────────────┼────────────────────┐
▼ ▼ ▼ ▼ ▼
┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐
│CEO │ │CTO │ ... │Mktg│ │ QA │ │ ...│
└────┘ └────┘ └────┘ └────┘ └────┘
│ │ │ │
└────────┴──────────┴──────────┘
│
┌──────────▼──────────┐
│ Memory Layer │
│ PostgreSQL + Qdrant│
└─────────────────────┘Agents
Agent | Role | Expertise |
CEO | Business Strategy | Market analysis, product roadmap, pricing, investment, startup advice |
CTO | Technology | Software architecture, backend, frontend, databases, AI/ML, DevOps, cloud |
Designer | Design | UI/UX, brand identity, logos, color palettes, design systems |
Sales | Revenue | Lead generation, cold emails, CRM, sales funnels, outreach |
Marketing | Growth | SEO, content, ads, social media, email campaigns, competitor analysis |
QA | Quality | Code review, bug finding, testing, security, performance |
Tech Stack
Runtime: Node.js 20+, TypeScript
Framework: Express, FastMCP SDK (
@modelcontextprotocol/sdk)Databases: PostgreSQL (pgvector), Qdrant (vector), Redis (cache)
AI: OpenAI, Anthropic Claude, Google Gemini
Infrastructure: Docker, Docker Compose
Quick Start
Prerequisites
Node.js 20+
Docker & Docker Compose
At least one AI provider API key (OpenAI, Anthropic, or Gemini)
1. Clone & Install
cd multi-agent-mcp
npm install2. Configure Environment
cp .env.example .envEdit .env and add your API keys:
OPENAI_API_KEY=sk-...
ANTHROPIC_API_KEY=sk-ant-...
GEMINI_API_KEY=...
API_KEY=sk-mcp-your-secret-key
JWT_SECRET=your-random-secret3. Start Infrastructure
docker compose up -d postgres qdrant redis4. Run Database Migrations
npm run db:migrate5. Start the Server
Development mode:
npm run devProduction mode:
npm run build
npm start6. Start MCP Server (for MCP clients)
npm run mcpAPI Endpoints
All endpoints require x-api-key header matching your API_KEY env var.
Method | Endpoint | Description |
POST |
| Send query to orchestrator (auto-routes to agents) |
POST |
| Ask CEO directly |
POST |
| Ask CTO directly |
POST |
| Ask Designer directly |
POST |
| Ask Sales directly |
POST |
| Ask Marketing directly |
POST |
| Ask QA directly |
POST |
| Save or search memory |
GET |
| List all projects |
GET |
| Get project details |
GET |
| List tasks |
GET |
| Health check |
Chat Example
curl -X POST http://localhost:3001/chat \
-H "Content-Type: application/json" \
-H "x-api-key: sk-mcp-your-secret-key" \
-d '{"query": "I want to launch an AI SaaS for small businesses"}'MCP Tools
When running as an MCP server (via npm run mcp), the following tools are exposed:
Tool | Description |
| Business strategy advice |
| Technical architecture guidance |
| UI/UX and brand design |
| Sales and lead generation |
| Marketing and growth |
| Code review and quality |
| Multi-agent collaboration |
| Create a new project |
| Store long-term memory |
| Retrieve memories |
| Semantic document search |
| Business strategy generation |
| UI design generation |
| System architecture design |
| Marketing plan generation |
| Sales plan generation |
| Full project review |
Docker Deployment
Start everything with one command:
docker compose up --buildThis starts:
app- The Multi-Agent MCP serverpostgres- PostgreSQL with pgvectorqdrant- Vector database for embeddingsredis- Cache layer
Environment Variables
Variable | Required | Description |
| Yes | API authentication key |
| Yes | JWT signing secret |
| No* | OpenAI API key |
| No* | Anthropic API key |
| No* | Google Gemini API key |
| No | PostgreSQL connection string |
| No | Qdrant endpoint |
| No | Redis connection string |
*At least one AI provider API key is required.
Project Structure
src/
├── agents/ # Agent implementations
│ ├── BaseAgent.ts # Abstract base class
│ ├── CEOAgent.ts
│ ├── CTOAgent.ts
│ ├── DesignerAgent.ts
│ ├── SalesAgent.ts
│ ├── MarketingAgent.ts
│ └── QAAgent.ts
├── orchestrator/ # Routing & workflow
│ ├── Router.ts # Intent detection, agent selection
│ └── Workflow.ts # Multi-agent execution, response merging
├── memory/ # Persistence layer
│ ├── postgres.ts # PostgreSQL client
│ ├── qdrant.ts # Qdrant vector client
│ ├── logger.ts # Winston logger
│ └── migrate.ts # DB migration runner
├── tools/ # MCP server
│ └── server.ts # FastMCP SDK server with tool registration
├── config/ # Configuration
│ └── index.ts # Env var loading
├── types/ # TypeScript types
│ └── index.ts # All type definitions
└── index.ts # Express REST API entry pointAdding a New Agent
Create
src/agents/YourAgent.tsextendingBaseAgentAdd your agent role to
AgentRoleenum insrc/types/index.tsAdd a system prompt in
SYSTEM_PROMPTSinsrc/types/index.tsRegister the agent in
Router.tsconstructorAdd MCP tool in
src/tools/server.tsAdd REST endpoint in
src/index.tsAdd SQL seed in
sql/schema.sql
License
MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/abdulsammad-lgtm/--Multi-agent-MCP---Network---CEO---CTO---Designer---Sale---Marketing---QA-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server