How to integrate Imagekit io MCP with Hermes

Imagekit io 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 Imagekit io 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 Imagekit io 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 Imagekit io 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 Imagekit io

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

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

5. Done!

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

The Imagekit io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your ImageKit.io account. It provides structured and secure access to your media library, so your agent can perform actions like organizing folders, managing files, handling bulk operations, editing metadata, and cleaning up assets on your behalf.

  • Bulk file operations: Effortlessly move, copy, or update tags on multiple files at once to streamline large-scale asset management.
  • Folder organization and management: Ask your agent to create new folders for better asset structuring or delete old folders—including all their contents—when you need to tidy up.
  • Custom metadata control: Let your agent create or delete custom metadata fields, so your media assets stay rich with the information your workflows need.
  • File and version cleanup: Instruct the agent to permanently delete files or remove outdated file versions to keep your storage lean and organized.
  • Bulk job monitoring: Have your agent track the status of ongoing bulk jobs, like folder copies or moves, so you always know what’s happening behind the scenes.

Supported Tools & Triggers

Tools
Bulk Job StatusTool to check status of a bulk job.
Bulk Move FilesTool to move multiple files in bulk.
Bulk Remove TagsTool to remove tags from multiple files in bulk.
Copy FolderTool to initiate a bulk copy of a folder.
Create Custom Metadata FieldTool to create a custom metadata field.
Create FolderTool to create a new folder.
Delete Custom Metadata FieldTool to delete a custom metadata field.
Delete FileTool to delete a file.
Delete File VersionTool to delete a specific non-current file version.
Delete FolderTool to delete a folder.
Delete Multiple FilesTool to delete multiple files.
Get Upload Authentication ParametersTool to generate authentication parameters for client-side file uploads.
Get File DetailsTool to retrieve details of a specific file.
Get File MetadataTool to retrieve metadata of an uploaded file.
Get File Version DetailsTool to retrieve details of a specific file version.
Get UsageTool to retrieve account usage metrics.
List and Search AssetsTool to list and search assets in your ImageKit account.
List Custom Metadata FieldsTool to list all custom metadata fields.
List File VersionsTool to list all versions of a file.
Move FolderTool to initiate a bulk move of a folder.
Purge ImageKit CacheTool to purge CDN and ImageKit caches for a given URL.
Check purge cache statusTool to check the status of a cache purge request.
Rename FileTool to rename a file.
Restore File VersionTool to restore a specific non-current file version as the current one.
Update Custom Metadata FieldTool to update an existing custom metadata field.
Update File DetailsTool to update details of a file.

Way Forward

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

FAQ

What are the differences in Tool Router MCP and Imagekit io MCP?

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

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

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