How to integrate Flowiseai MCP with Hermes

GET STARTED FOR FREE
Flowiseai logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Flowiseai account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Flowiseai with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Flowiseai with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Flowiseai

Ask your agent to connect to Flowiseai, or simply request any Flowiseai-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Flowiseai connection.

Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Flowiseai or request any Flowiseai-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Flowiseai MCP server, and what's possible with it?

The Flowiseai MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Flowiseai account. It provides structured and secure access to your FlowiseAI workspace, so your agent can manage chatflows, automate workflow creation, clone or delete existing flows, and handle tool configurations on your behalf.

  • Automated chatflow creation and management: Instantly create new chatflows, fetch details of existing ones, or update and organize your LLM workflows programmatically.
  • Seamless cloning and exporting of chatflows: Duplicate any chatflow with a single request or export them for backup, sharing, or versioning across projects.
  • Easy clean-up and deletion: Direct your agent to delete chatflows, remove outdated tools, or erase chat messages to keep your workspace tidy and relevant.
  • Tool and workflow introspection: Retrieve detailed metadata for specific tools or chatflows so your agent can make informed decisions about which components to use or modify.
  • Effortless import and migration: Import chatflows from exported JSON files, making it simple to migrate or restore entire AI workflows with minimal manual effort.

Supported Tools & Triggers

Tools
Clone ChatflowTool to clone an existing chatflow.
Create ChatflowTool to create a new chatflow in FlowiseAI.
Delete ChatflowTool to delete a chatflow by its ID.
Delete Chat MessagesTool to delete chat messages for a specific chatflow.
Delete Tool By IDTool to delete a specific FlowiseAI tool by ID.
Export ChatflowTool to export a chatflow by its ID.
Get All ChatflowsTool to retrieve all chatflows.
Get Single ChatflowTool to retrieve a chatflow by its ID.
Get Tool By IDTool to retrieve a specific FlowiseAI tool by its ID.
Import ChatflowTool to import a chatflow from an exported JSON file.
List All ToolsTool to retrieve a list of all tools.
List Chat MessagesTool to list chat messages of a chatflow.
Update Chatflow DetailsTool to update details of an existing chatflow.
Update Tool By IDTool to update a specific tool by its ID.

Way Forward

With Flowiseai connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

How to build Flowiseai MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Flowiseai MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Flowiseai MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Flowiseai MCP with Claude Code

Codex logo

Codex

Use Flowiseai MCP with Codex

OpenClaw logo

OpenClaw

Use Flowiseai MCP with OpenClaw

CLI logo

CLI

Use Flowiseai MCP with CLI

Google ADK logo

Google ADK

Use Flowiseai MCP with Google ADK

LangChain logo

LangChain

Use Flowiseai MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Flowiseai MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Flowiseai MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Flowiseai MCP with LlamaIndex

CrewAI logo

CrewAI

Use Flowiseai MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Flowiseai MCP?

With a standalone Flowiseai MCP server, the agents and LLMs can only access a fixed set of Flowiseai tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Flowiseai and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Hermes?

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Flowiseai tools.

Can I manage the permissions and scopes for Flowiseai while using Tool Router?

Yes, absolutely. You can configure which Flowiseai scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Flowiseai data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free