How to integrate Fibery MCP with Hermes

GET STARTED FOR FREE
Fibery 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 Fibery 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 Fibery 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 Fibery 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 Fibery

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

4. Done. You're all set with a new Fibery 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 Fibery or request any Fibery-related task. It will prompt you to authenticate and authorize access.

5. Done!

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

The Fibery MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fibery account. It provides structured and secure access to your workspace data, so your agent can perform actions like querying entities, managing custom apps, running GraphQL queries, and organizing files—all with zero manual integration code.

  • Entity query and retrieval: Instantly fetch detailed information or lists of entities based on type, filters, and fields, making it easy to surface project or task data as needed.
  • Custom app and endpoint management: Let your agent list, inspect, or delete custom apps and endpoints, streamlining workspace configuration and app lifecycle management.
  • Flexible data manipulation with GraphQL: Execute custom GraphQL queries and mutations against your Fibery space to fetch, update, or manipulate structured data programmatically.
  • File and resource cleanup: Remove outdated files or entities efficiently, helping keep your workspace organized and clutter-free with automated deletions.
  • Authentication and workspace insights: Validate tokens securely and retrieve workspace or app metadata, ensuring your agent always operates with up-to-date context and permissions.

Supported Tools & Triggers

Tools
Delete Custom App EndpointTool to delete a specific custom app endpoint.
Delete EntityTool to delete a specific Fibery entity by its ID.
Delete FileTool to delete a specific file.
Execute GraphQL QueryTool to execute GraphQL queries or mutations against a Fibery space.
Authenticate (validate token via API call)Tool to validate existing Fibery personal API token by performing a real API call.
Get App InformationTool to retrieve application information.
Get Custom App EndpointsTool to list custom app endpoints.
Get Custom AppsTool to list all custom apps in the Fibery workspace.
Get EntitiesTool to query Fibery entities.
Get Fibery EntityTool to retrieve detailed info of a specific Fibery entity by its ID.
Get FileTool to retrieve a file by its secret or id.
Get GraphQL SchemaTool to retrieve the GraphQL schema for the current workspace.
Get User PreferencesTool to retrieve the current user's UI preferences.
Refresh access tokenTool to refresh an access token using a refresh token.
Authenticate with username and passwordTool to authenticate with Fibery using resource owner password credentials.
Create EntityTool to create a new Fibery entity.
Fetch Data from SourceTool to fetch data from a specified source.
POST_FETCH_DATA_COUNTTool to return the count of records for a given Fibery type (source).
Fetch Datalist OptionsTool to fetch options for a datalist filter field.
Fetch SchemaTool to fetch predefined data schema.
Exchange OAuth2 authorization codeTool to finalize OAuth2 authentication for Fibery custom apps.
Revoke Access TokenTool to revoke an existing Fibery API access token.
Validate Fibery accountTool to validate account credentials.
Validate FilterTool to validate filter definitions.
Update EntityTool to update an existing Fibery entity.
Update User PreferencesTool to update the current user's preferences by using the Commands API.
Upload FileTool to upload a file to Fibery.

Way Forward

With Fibery 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 Fibery MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Fibery MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Fibery MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Fibery MCP with Claude Code

Codex logo

Codex

Use Fibery MCP with Codex

OpenClaw logo

OpenClaw

Use Fibery MCP with OpenClaw

CLI logo

CLI

Use Fibery MCP with CLI

Google ADK logo

Google ADK

Use Fibery MCP with Google ADK

LangChain logo

LangChain

Use Fibery MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Fibery MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Fibery MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Fibery MCP with LlamaIndex

CrewAI logo

CrewAI

Use Fibery MCP with CrewAI

FAQ

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

With a standalone Fibery MCP server, the agents and LLMs can only access a fixed set of Fibery tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Fibery 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 Fibery tools.

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

Yes, absolutely. You can configure which Fibery 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 Fibery 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