How to integrate Better stack MCP with Hermes

Better stack 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 Better stack 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 Better stack 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 Better stack 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 Better stack

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

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

5. Done!

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

The Better stack MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Better Stack account. It provides structured and secure access to your monitoring, logging, and incident management tools, so your agent can perform actions like retrieving uptime metrics, managing escalation policies, checking heartbeat statuses, and organizing log sources on your behalf.

  • Monitor health checks and availability: Let your agent fetch uptime percentages, availability summaries, and incident details for any monitor in your stack.
  • Automated escalation policy management: Instruct your agent to create or delete escalation policies, keeping your incident response workflows up-to-date without manual effort.
  • Heartbeat tracking and organization: Have your agent fetch specific heartbeat data, check heartbeat availability, or group related heartbeats for easier monitoring.
  • Log source grouping and management: Enable your agent to create or delete source groups, helping you organize log streams and maintain a tidy observability structure.
  • Webhook integration setup: Direct your agent to register outgoing webhooks so your stack can notify external systems of important events automatically.

Supported Tools & Triggers

Tools
Create Escalation PolicyTool to create a new escalation policy.
Create Heartbeat GroupTool to create a new heartbeat group.
Create Outgoing Webhook IntegrationTool to create a new outgoing webhook integration.
Create Source GroupTool to create a new source group.
Delete Escalation PolicyTool to delete an escalation policy by id.
Delete Source GroupTool to delete a source group by id.
Get HeartbeatTool to get a single heartbeat by id.
Get Heartbeat AvailabilityTool to retrieve availability summary for a specific heartbeat.
Get MonitorTool to get a single monitor.
Get Monitor AvailabilityTool to return an availability summary for a specific monitor.
Get Monitor Response TimesTool to return response times for a specific monitor.
Get Status PageTool to get a single status page by id.
Get Telemetry API TokenTool to retrieve the telemetry api token from the integration configuration.
Get Uptime API TokenTool to retrieve the configured uptime api token.
List Catalog RelationsTool to list all catalog relations.
List Google Monitoring IntegrationsTool to list all google monitoring integrations.
List Grafana IntegrationsTool to list all grafana integrations.
List HeartbeatsTool to list all heartbeats.
List MonitorsTool to list all monitors.
List New Relic IntegrationsTool to list new relic integrations.
List On-Call SchedulesTool to list all on-call schedules.
List Status Page ReportsTool to list all reports on a status page.
List Status PagesTool to list all your status pages.
Update HeartbeatTool to update an existing heartbeat configuration.
Update Heartbeat GroupTool to update an existing heartbeat group.
Update Source GroupTool to update an existing source group.

Way Forward

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

FAQ

What are the differences in Tool Router MCP and Better stack MCP?

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

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

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