Synapse AI — Multi-Agent Orchestration Platform
Build AI workflows that actually ship.
Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
Build AI workflows that actually ship.
SynapseOrch: AI workflows that follow the plan. Describe a job, approve the steps, run them on any model, local or cloud. MCP server included. Open source (AGPL-3.0).
macOS / Linux:
curl -sSL https://raw.githubusercontent.com/synapseorch-ai/synapse-ai/main/setup.sh | bash
Windows (PowerShell):
irm https://raw.githubusercontent.com/synapseorch-ai/synapse-ai/main/setup.ps1 | iex
npm install -g synapse-orch-ai
synapse
pip install synapse-orch-ai
synapse
docker run -d \
-p 3000:3000 \
-v synapse-data:/data \
-v /var/run/docker.sock:/var/run/docker.sock \
synapseorchai/synapse-ai:latest
Then open http://localhost:3000. See the Docker guide in the docs for custom ports and environment variable configuration.
Security: publish only the frontend port
3000— the backend (8765) serves an internal API and should not be exposed on0.0.0.0(docker-compose binds it to127.0.0.1). The container auto-generates a shared internal token so that surface is authenticated by default. For any network-reachable deployment, enable login (Settings → Security) and/or setallow_stdio_mcp=false, since registering a stdio MCP server launches local commands.
Upgrade note (security hardening): the backend now auto-generates a shared internal token and, under docker-compose, binds its port to
127.0.0.1by default. The UI and its API are unaffected (the frontend proxies the backend internally). If you previously called the backend directly on:8765(e.g. external API clients), either point them at the frontend instead —http://host:3000/api/v1|v2/...— or setSYNAPSE_BACKEND_BIND=0.0.0.0in.envto keep publishing:8765.
Run unlimited agents and orchestrations concurrently. When you need to go beyond a single process, the distributed scale layer handles the load:
Three Docker images — pull only what you need:
docker pull synapseorchai/synapse-ai:latest # full app (standalone mode)
docker pull synapseorchai/synapse-ai-api-server:latest # stateless API server (scale mode)
docker pull synapseorchai/synapse-ai-worker:latest # worker process (scale mode, run as many as needed)
The docker-compose.yml in the repo spins up the full stack. Production K8s manifests are in infra/k8s/.
Multi-agent pipeline that researches a topic, drafts content in a Google Doc, and returns the shared link. (Video is 2x speed)
Multi-agent system with human-in-the-loop that writes code and generates pull requests autonomously.
Chat with the AI builder — describe what you want, and it creates the orchestration DAG for you.
synapse start # start backend + frontend, open browser
synapse stop # stop background processes
synapse upgrade # upgrade to the latest version
synapse uninstall # remove Synapse, wipe ~/.synapse, and uninstall the package
See CONTRIBUTING.md for dev setup, architecture details, how to add MCP tool servers, and the PR checklist.
Synapse AI is licensed under AGPL v3 — see LICENSE
SynapseOrch: AI workflows that follow the plan. Describe a job, approve the steps, run them on any model, local or cloud. MCP server included. Open source (AGPL-3.0).
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Synapse Ai s'exécute en local via stdio.
Dernière vérification : 2026-11-17. SynapseOrch: AI workflows that follow the plan. Describe a job, approve the steps, run them on any model, local or cloud. MCP server included. Open source (AGPL-3.0).