Synaplan Multimodal Gateway

git clone https://github.com/metadist/synaplan.git cd synaplan docker compose up -d

That third step is the whole setup.You never touch a config file to connect an AI provider.

- Paste it in the UI.Admin → AI Providers(/admin/setup) lists every provider with aConnectedbadge and a free-tier hint.
- Tested before it's saved.The key is validated against the live provider API, so a typo fails immediately instead of at your first chat.
- Encrypted at rest.It lives encrypted in your own database, not in a plaintext file on disk.
- Active instantly.No restart and no rebuild — the next message already uses it.
- Defaults repair themselves.If the default chat model points at a provider you have no key for, Synaplan repoints it to one that works, so chat is never dead on a fresh install.
- .envstill works.Keys already inbackend/.envare imported into the encrypted store on first use, and a key you later save in the UI wins permanently.

No cloud key at all?Start withENABLE_LOCAL_GPT_OSS=true docker compose up -dto pull a local chat model (gpt-oss:20b, ~14 GB, GPU or a strong CPU recommended). Chat begins working when the download finishes;docker compose logs -f backendshows progress.

Click any screenshot to see it full size.

Regenerate these assets after a UI change withscripts/build-readme-tour.sh.

The same assistant, the same knowledge base, the same model policy — on every channel your team already uses.

- Docker+Docker Compose v2(Docker Desktop on macOS/Windows, or Docker Engine + the Compose plugin on Linux)
- Git
- 8 GB RAMminimum (16 GB recommended for the local-AI standard install)
- ~9 GB free diskfor the standard install (~5 GB for minimal, +~14 GB if you enable the local chat model)
- Free TCP ports5173,8000,8082,8025,3307,6333,11435

Apple Silicon (M1–M4) Macs — build the backend image, don't pull it.The three-step start above already does this:docker compose up -dbuilds the backend and worker locally from a multi-arch base image, so PHP/FrankenPHP runsnatively onarm64with no emulation tax. That is by far the fastest setup, and it is the default — you don't have to do anything special. The pre-builtghcr.io/metadist/synaplanimage published for production deployments islinux/amd64only, so pulling it instead means running the whole backend under emulation. The first local build takes a few minutes; every later start is a cache hit. Two optional dev tools (phpMyAdmin, MailHog) are still amd64-only upstream images — if you keep them, enableDocker Desktop → Settings → General → "Use Rosetta for x86/amd64 emulation on Apple Silicon"(macOS 13+) so those two emulate quickly.

The standard install downloads the local embedding model (bge-m3, ~1 GB) in the background for RAG and semantic search; progress is shown in the app.

Prefer the shell to the UI for provider keys? Keys inbackend/.envstill work — the backend reads that file when the container starts and imports the key into the encrypted store on first use. Write the key before starting, or restart the containers afterwards:

echo "GROQ_API_KEY=your_key" >> backend/.env docker compose -f docker-compose-minimal.yml up -d # already running? pick up the new key with: # docker compose restart backend worker

Synaplan is provider-neutral: connect the providers you want inAdmin → AI Providers(keys are validated live and stored encrypted in the database, active without a restart), or set the env variables below inbackend/.env— those are read at container start and imported into the encrypted store on first use. Each user picks a different modelper task(chat, vision, image, video, audio, embeddings) — nothing is hardcoded.

Qdrant runs as an internal Docker service — no configuration needed. It powers AI memories, RAG document search, and the feedback system.

Starts automatically withdocker compose up -d. Synaplan works fully without it (memories and vector search will be disabled).

Both compose files also start three internal services (no host ports, no setup needed):

git clone https://github.com/metadist/synaplan-tts.git && cd synaplan-tts && docker compose up -d

# Logs docker compose logs -f backend # Restart docker compose restart backend # Reset database docker compose down -v && docker compose up -d # Run tests make test # Code quality make lint

In-repo guides (for developers working on this codebase):

synaplan/ ├── backend/ # Symfony PHP API ├── frontend/ # Vue.js SPA ├── docs/ # Documentation ├── _docker/ # Docker configs └── plugins/ # Plugin system

The 1Password MCP server creates a bridge that allows MCP clients such as Codex and Kiro to manage your 1Password Environments with secure authorization prompts.

This is the 1st, easiest, and cheapest PPT, slides, presentation AI generation MCP Server in the world.

Persistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.

A MCP server that enables AI assistants to interact with Anki, the spaced repetition flashcard application.

Enables LLM clients to interact with macOS applications through AppleScript. Built using the @beyondbetter/bb-mcp-server library, this server provides safe, controlled execution of predefined scripts with optional support for arbitrary script execution.

An MCP server for WordPress plugin audits

Turn your AI assistant into a digital marketing hub that creates, organizes, and analyzes links and QR Codes on demand.

Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.