8000 GitHub - dujonwalker/project-nova: A multi-agent AI architecture that connects 25+ specialized agents through n8n and MCP servers. Project NOVA routes requests to domain-specific experts, enabling control of applications from knowledge bases to DAWs, home automation to development tools. Includes system prompts, Dockerfiles, and workflows for a complete AI assistant ecosystem.
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

A multi-agent AI architecture that connects 25+ specialized agents through n8n and MCP servers. Project NOVA routes requests to domain-specific experts, enabling control of applications from knowledge bases to DAWs, home automation to development tools. Includes system prompts, Dockerfiles, and workflows for a complete AI assistant ecosystem.

Notifications You must be signed in to change notification settings

dujonwalker/project-nova

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

12 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Project NOVA: Networked Orchestration of Virtual Agents

Project NOVA (Networked Orchestration of Virtual Agents) is a comprehensive, self-hosted AI assistant ecosystem that leverages n8n workflows, LLMs, and 25+ specialized Model Context Protocol (MCP) servers to create a powerful, extensible agent system capable of controlling both digital environments and physical devices in your home.

๐ŸŒŸ Features

  • Centralized AI Assistant Hub: Route requests to 25+ specialized agents through an intelligent router
  • Domain-Specific Capabilities: Knowledge management, development tools, media production, home automation, and more
  • Self-Hosted & Privacy-Focused: Run everything locally with open-source components
  • Containerized Architecture: Easy deployment with Docker, Dockerfiles, and docker-compose.yml files
  • SSE Transport Integration: Enhanced MCP server communication using supergateway
  • Extensible Framework: Add new specialized agents with provided templates

๐Ÿ—๏ธ Architecture Overview

Project NOVA uses a hub-and-spoke architecture where the main router agent analyzes user requests and delegates to specialized agents:

Architecture Diagram

๐Ÿ“š Reference Guide

Project NOVA includes a comprehensive reference guide to help you understand and use all available agents effectively:

The reference guide provides detailed information about each agent's capabilities, tools, example queries, and troubleshooting tips.

๐Ÿ“‹ Specialized Agents

Project NOVA includes over 25 specialized agents across multiple domains:

Knowledge Management & Note-Taking

Development & Repository Management

Media & Creative Tools

  • Ableton Copilot - Assists with music production in Ableton Live
  • OBS Agent - Controls OBS Studio for streaming and recording
  • Reaper Agent - Controls REAPER digital audio workstation
  • Reaper QA Agent - Analyzes and answers questions about REAPER projects
  • YouTube Agent - Transcribes YouTube videos for summarization and content analysis

AI & Automation

  • Flowise Agent - Connects to Flowise chatflows and AI assistants
  • Langfuse Agent - Accesses managed prompts from Langfuse
  • Puppeteer Agent - Provides browser automation for web scraping and testing
  • RAGFlow Agent - Retrieval-augmented generation with source citations
  • Fetch Agent - Retrieves web content from URLs with advanced options

Monitoring & Home Automation

๐Ÿš€ Getting Started

Prerequisites

Before setting up Project NOVA, ensure you have:

  • n8n Instance: A running n8n installation (v1.88.0 or later)
    • Critical: Version 1.88.0+ (released April 10, 2025) is required as it introduced the MCP Client Tool node
    • This node is essential for connecting to MCP-enabled services
  • Community Nodes:
    • nerding-io/n8n-nodes-mcp-client - Required as some agents use this community implementation
    • Project NOVA currently uses a mix of official and community MCP nodes
  • Docker Host: Environment for running containerized MCP servers
  • LLM Access: Either:
    • Cloud API access (OpenAI, Claude, Gemini, etc.)
    • Local Ollama instance with models that support tool use/function calling
  • Applications to Control:
    • The actual applications you want NOVA to control (most agents are designed for self-hosted applications)
    • Examples: Home Assistant, Gitea, Reaper, OBS Studio, TriliumNext, etc.
    • Each agent requires its corresponding application to be accessible

This repository contains all the tools and instructions needed to build your own AI assistant ecosystem using n8n as the workflow automation platform.

  1. Clone the repository:

    git clone https://github.com/dujonwalker/project-nova.git
    cd project-nova
  2. Import workflows in your n8n instance:

    • Bulk import via n8n CLI (easiest):
      # Navigate to your n8n installation directory
      n8n import:workflow --input=path/to/project-nova/n8n-workflows/*
    • Import via n8n Web Interface:
      • Navigate to your n8n dashboard
      • Click on "Workflows" in the sidebar
      • Use the "Import from file" option for each workflow
      • Start with core workflows first, then specialized agents
  3. Set up MCP servers:

    • Use the Dockerfiles and docker-compose.yml files provided in mcp-server-dockerfiles to build and run your servers
    • Or use the instructions to set up MCP servers directly on your host
  4. Configure your API keys:

    • Update credentials in each workflow for your LLM provider
    • Set up your preferred LLM API (OpenAI, Claude, Gemini, etc.)
    • For local deployment, configure Ollama with any models that support tool use/function calling (examples include qwen3, llama3.1, mistral, and others)
    • Give NOVA the keys to your apps (i.e., Paperless-NGX API key, Gitea API key, Home Assistant token, etc.)
  5. Start with the router agent:

    • Once your workflows and agents are set up, navigate to the router agent workflow in n8n
    • Use the chat trigger node to start a conversation with NOVA
    • The router will analyze your requests and direct them to the appropriate specialized agents

Note: The repository is structured to make replication as straightforward as possible. You can choose to implement all agents or just the ones you need.

Chat Interface

๐Ÿ“ Repository Structure

project-nova/
โ”œโ”€โ”€ README.md                      # This README file
โ”œโ”€โ”€ agents/                        # System prompts for all agents
โ”œโ”€โ”€ mcp-server-dockerfiles/        # Dockerfiles and docker-compose.yml files for MCP servers
โ”‚   โ”œโ”€โ”€ [server-name]-mcp/         # Each MCP server has its own directory
โ”‚   โ”‚   โ”œโ”€โ”€ Dockerfile             # Container definition
โ”‚   โ”‚   โ”œโ”€โ”€ docker-compose.yml     # Deployment configuration
โ”‚   โ”‚   โ”œโ”€โ”€ README.md              # Server-specific setup instructions
โ”‚   โ”‚   โ””โ”€โ”€ start.sh               # Entry point script (when applicable)
โ”œโ”€โ”€ n8n-workflows/                 # n8n workflow export files (.json)
โ”œโ”€โ”€ prompt-templates/              # Templates for creating new components
โ”‚   โ”œโ”€โ”€ agent-input-examples/      # Example inputs for each agent (.json)
โ”‚   โ”œโ”€โ”€ generate-agent.md          # Template for creating new agents
โ”‚   โ”œโ”€โ”€ generate-container.md      # Guide for containerizing MCP servers
โ”‚   โ””โ”€โ”€ generate-routing-agent.md  # Router agent generation template
โ””โ”€โ”€ reference-guide/               # Comprehensive documentation
    โ”œโ”€โ”€ agents-index.md            # Complete list of all agents
    โ”œโ”€โ”€ router-agent-quick-reference.md  # Router usage guide
    โ””โ”€โ”€ sub-agents-by-category/    # Detailed agent documentation by domain
        โ”œโ”€โ”€ knowledge-agents.md
        โ”œโ”€โ”€ devops-agents.md
        โ”œโ”€โ”€ media-agents.md
        โ””โ”€โ”€ automation-agents.md

๐Ÿ”ง Advanced Configuration

Adding a New Specialized Agent

  1. Use the generate-agent.md template to create a new agent system prompt
  2. Create a Dockerfile using generate-container.md as a guide
  3. Add n8n workflow configuration
  4. Update the router agent to include your new specialized agent

๐Ÿ” Use Cases

  • Home Automation: "Turn off the living room lights and start playing my evening playlist"
  • Knowledge Management: "Find my notes about the project meeting from last Tuesday"
  • Creative Production: "Help me set up a new Ableton Live project with a drum rack"
  • Development Assistance: "Check my Gitea repositories for any open pull requests"
  • System Management: "Monitor the CPU usage on my server for the last 24 hours"

๐Ÿ› ๏ธ Troubleshooting

  • Agent Not Responding: Check Docker container logs for the specific MCP server
  • Router Misidentifying Agent: Review the router-agent.md system prompt for accurate routing logic
  • API Connectivity Issues: Verify API keys in your .env file and container environment
  • Prompt Configuration: Make sure all sub-agents have the prompt (user message) set to {{ $json.input }} in their n8n workflow configuration

๐Ÿ“Š Performance Considerations

  • Recommended minimum specs: 4GB RAM, 2 CPU cores for basic setup
  • For running all agents simultaneously: 16GB RAM, 8 CPU cores recommended
  • Consider using local LLM inference options for reduced API costs and latency

๐Ÿ”ฎ Future Development

  • Integration with OpenWebUI to provide:
    • Voice interface integration
    • Sending and receiving files
  • More specialized agents for additional domains

๐Ÿ™ Acknowledgments

  • n8n for the incredible workflow automation platform
  • Model Context Protocol for standardizing AI tool interaction
  • Supergateway for enabling conversion from STDIO to SSE transport
  • nerding-io for their pioneering work on n8n-nodes-mcp that inspired this project
  • All the open-source projects that make the specialized agents possible

๐Ÿ“š Additional Resources

  • Project NOVA: Detailed Write-up - Comprehensive blog post with additional insights and implementation details
  • For questions or support, please open an issue in this repository

๐Ÿ” MCP Resources

If you're looking to expand your Project NOVA with additional agents, here are some valuable resources for finding MCP servers:

Verified Working MCP Servers

  • My Curated List of Working MCP Servers - A regularly updated collection of GitHub-hosted MCP servers I've personally tested and verified working with Project NOVA. Note that some servers hosted on other platforms (like gitea-mcp) won't appear in this GitHub-specific list.

Additional MCP Directories

These resources can help you discover new MCP servers to integrate into your own Project NOVA implementation.

About

A multi-agent AI architecture that connects 25+ specialized agents through n8n and MCP servers. Project NOVA routes requests to domain-specific experts, enabling control of applications from knowledge bases to DAWs, home automation to development tools. Includes system prompts, Dockerfiles, and workflows for a complete AI assistant ecosystem.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published
0