mirror of
https://github.com/FlowiseAI/Flowise.git
synced 2026-10-12 10:09:53 +00:00
* feat: implement the custom MCP Server in tool - Implemented MCPServersTable for displaying MCP server data with status badges and tools count. - Created CustomMcpServerDialog for adding and editing custom MCP servers with validation and authorization features. - Integrated MCP server management into the Tools view with tabbed navigation for Custom Tools and Custom MCP Servers. - Added pagination and loading states for MCP servers. * tfix nodes.test.ts ESM load crash * feat(custom-mcp): harden security, scalability, and UI polish * enhance custom mcp server creation flow and UI updates * feat(mcp): add MCP server handshake timeout, enhance UI UX for editing custom mcp server --------- Co-authored-by: Henry <[email protected]>
Flowise Docker Hub Image
Starts Flowise from DockerHub Image
Usage
- Create
.envfile and specify thePORT(refer to.env.example) docker compose up -d- Open http://localhost:3000
- You can bring the containers down by
docker compose stop
🌱 Env Variables
If you like to persist your data (flows, logs, credentials, storage), set these variables in the .env file inside docker folder:
- DATABASE_PATH=/root/.flowise
- LOG_PATH=/root/.flowise/logs
- SECRETKEY_PATH=/root/.flowise
- BLOB_STORAGE_PATH=/root/.flowise/storage
Flowise also support different environment variables to configure your instance. Read more
Queue Mode:
Building from source:
You can build the images for worker and main from scratch with:
docker compose -f docker-compose-queue-source.yml up -d
Monitor Health:
docker compose -f docker-compose-queue-source.yml ps
From pre-built images:
You can also use the pre-built images:
docker compose -f docker-compose-queue-prebuilt.yml up -d
Monitor Health:
docker compose -f docker-compose-queue-prebuilt.yml ps