How to integrate Apify MCP with Hermes

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Apify 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 Apify 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 Apify 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 Apify 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 Apify

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

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

5. Done!

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

The Apify MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Apify account. It provides structured and secure access to your web scraping and automation workflows, so your agent can create actors, manage datasets, fetch scraped data, schedule tasks, and maintain webhooks on your behalf.

  • Automated Actor Creation and Management: Easily instruct your agent to programmatically create, configure, or delete Apify actors for custom web automation or scraping jobs.
  • Dataset Handling and Data Retrieval: Let your agent spin up new datasets, organize scraped results, and pull items from datasets for downstream analysis or reporting.
  • Task Scheduling and Automation: Have your agent create and manage recurring actor tasks, making it simple to automate data extraction or browser automation at set intervals.
  • Webhook Integration and Event Handling: Direct your agent to set up or remove webhooks for actor tasks, enabling real-time notifications or downstream integrations when a task completes or fails.
  • Actor and Build Metadata Access: Empower your agent to fetch detailed metadata about actors, including build information and configuration details, for monitoring or troubleshooting purposes.

Supported Tools & Triggers

Tools
Create ActorTool to create a new actor with specified configuration.
Create DatasetTool to create a new dataset.
Create Actor TaskTool to create a new actor task with specified settings.
Create Task WebhookTool to create a webhook for an actor task.
Delete ActorTool to delete an actor permanently.
Delete WebhookTool to delete a webhook by its id.
Get Actor DetailsTool to get details of a specific actor.
Get all webhooksTool to get a list of all webhooks created by the user.
Get dataset itemsTool to retrieve items from a dataset.
Get Default BuildTool to get the default build for an actor.
Get Key-Value RecordTool to retrieve a record from a key-value store.
Get list of buildsTool to get a list of builds for a specific actor.
Get list of runsTool to get a list of runs for a specific actor.
Get list of task runsTool to get a list of runs for a specific actor task.
Get list of tasksTool to fetch a paginated list of tasks belonging to the authenticated user.
Get list of task webhooksTool to get a list of webhooks for a specific actor task.
Get logTool to retrieve logs for a specific actor run or build.
Get OpenAPI DefinitionTool to get the openapi definition for a specific actor build.
Get Task InputTool to retrieve the input configuration of a specific task.
Resurrect RunTool to resurrect a finished actor run.
Run Actor AsynchronouslyTool to run a specific actor asynchronously.
Run Actor SyncTool to run a specific actor synchronously with input and return its output record.
Run Actor Sync & Get Dataset ItemsTool to run an actor synchronously and retrieve its dataset items.
Run Task AsynchronouslyTool to run a specific actor task asynchronously.
Store Data in DatasetTool to store data items in a dataset.
Store Data in Key-Value StoreTool to create or update a record in a key-value store.
Update Key-Value StoreTool to update a key-value store's properties.
Update Task InputTool to update the input configuration of a specific actor task.

Way Forward

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

FAQ

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

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

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

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