Skip to main content
Connect Flowise agents to Civic’s MCP Hub. Flowise supports MCP tool servers natively through its MCP Tool node — no code required.

​
Prerequisites

  • A Flowise instance (cloud or self-hosted)
  • A Civic account at nexus.civic.com with a configured toolkit
  • A Civic token

​
Get Your Credentials

You need your Civic MCP URL and a Civic token before configuring Flowise.

Get Your Credentials

How to generate a Civic token and configure toolkit URL parameters

​
Connect Civic to Flowise

1

Open your chatflow or agentflow

In Flowise, open an existing chatflow or agentflow, or create a new one.
2

Add an MCP Tool node

In the node panel, search for MCP Tool and drag it onto the canvas.
3

Configure the MCP server

In the MCP Tool node settings:
  • MCP Server URL: https://nexus.civic.com/hub/mcp?profile=your-toolkit
  • Transport: Streamable HTTP
  • Headers: Add Authorization with value Bearer your-civic-token
4

Connect to your agent

Connect the MCP Tool node to your agent node. Flowise will discover all available Civic tools and make them accessible to the agent.
5

Test the connection

Save and test your flow. Ask your agent to use a Civic tool (e.g., “What emails do I have unread?”). The agent will call the tool through the Civic Hub.

​
Locking to a Toolkit

For production flows, lock to a specific toolkit by adding the profile parameter to your MCP URL: 
https://nexus.civic.com/hub/mcp?profile=your-production-toolkit
When a profile is set, the session is locked — the agent cannot switch toolkits or modify its own guardrails.

​
Next Steps

Agent Deployment

Profile locking, URL params, and production agent configuration

Guardrails

Constrain what tools your Flowise agent can call

Audit Trail

Query what your agent did via Civic Chat

Get Credentials

Token generation and URL parameter reference