How to integrate Retailed MCP with Hermes

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

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

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

5. Done!

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

The Retailed MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Retailed account. It provides structured and secure access to your retail data and e-commerce integrations, so your agent can perform actions like product searches, dynamic price retrieval, trend analysis, inventory checks, and API usage monitoring on your behalf.

  • Real-time product search and discovery: Instantly search for products across supported platforms and retrieve detailed information based on your custom criteria.
  • Dynamic pricing and size-based quotes: Ask your agent to pull the latest pricing for specific products and sizes from marketplaces like GOAT and StockX.
  • Trend analysis and market insights: Have the agent surface the latest trending products from StockX, helping you spot opportunities and popular items quickly.
  • Comprehensive product metadata access: Retrieve in-depth product metadata from StockX by SKU or URL for more informed decisions and listings.
  • API usage and quota monitoring: Let your agent track your current API usage statistics, so you stay on top of your account limits and avoid surprises.

Supported Tools & Triggers

Tools
Get GOAT Product PricesTool to retrieve pricing information for a specific product on goat.
Get StockX ProductTool to retrieve detailed stockx product information.
StockX SearchTool to search stockx marketplace for products and pricing information.
StockX TrendsTool to get the latest trending products from stockx.
Get API UsageTool to retrieve current api usage statistics.
Search ProductsSearch for products in retailed matching query criteria.

Way Forward

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

FAQ

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

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

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

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