> ## Documentation Index
> Fetch the complete documentation index at: https://docs.civic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flowise

> Connect a Flowise agent to Civic's MCP Hub

Connect [Flowise](https://flowiseai.com/) 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 [app.civic.com](https://app.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.

<Card title="Get Your Credentials" icon="key" href="/civic/quickstart/credentials">
  How to generate a Civic token and configure toolkit URL parameters
</Card>

## Connect Civic to Flowise

<Steps>
  <Step title="Open your chatflow or agentflow">
    In Flowise, open an existing chatflow or agentflow, or create a new one.
  </Step>

  <Step title="Add an MCP Tool node">
    In the node panel, search for **MCP Tool** and drag it onto the canvas.
  </Step>

  <Step title="Configure the MCP server">
    In the MCP Tool node settings:

    * **MCP Server URL**: `https://app.civic.com/hub/mcp?profile=your-toolkit`
    * **Transport**: `Streamable HTTP`
    * **Headers**: Add `Authorization` with value `Bearer your-civic-token`
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Locking to a Toolkit

For production flows, lock to a specific toolkit by adding the `profile` parameter to your MCP URL:

```
https://app.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

<CardGroup cols={2}>
  <Card title="Agent Deployment" icon="robot" href="/civic/quickstart/clients/agents">
    Profile locking, URL params, and production agent configuration
  </Card>

  <Card title="Guardrails" icon="shield" href="/civic/concepts/guardrails">
    Constrain what tools your Flowise agent can call
  </Card>

  <Card title="Audit Trail" icon="list-check" href="/civic/concepts/audit">
    Query what your agent did via Civic Chat
  </Card>

  <Card title="Get Credentials" icon="key" href="/civic/quickstart/credentials">
    Token generation and URL parameter reference
  </Card>
</CardGroup>