How to integrate Kit MCP with Hermes

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

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

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

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

5. Done!

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

The Kit MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kit account. It provides structured and secure access to your subscriber lists, tags, forms, and automations, so your agent can perform actions like managing subscribers, creating tags, updating custom fields, and handling broadcasts on your behalf.

  • Subscriber management and automation: Add new subscribers to forms, remove subscribers, or update their details to keep your audience lists accurate and engaged.
  • Custom field and tag creation: Automatically create, update, or delete custom fields and tags, making it easy to segment and personalize your communications.
  • Webhook and event setup: Set up or remove webhooks so your agent can listen for subscriber or purchase events and trigger automations as needed.
  • Broadcast and campaign control: Delete obsolete broadcasts or manage your messaging campaigns directly through your agent for streamlined outreach.
  • Account insights and configuration: Retrieve detailed account information, including plan details and primary contact, to keep your integrations and automations running smoothly.

Supported Tools & Triggers

Tools
Add Subscriber to FormTool to add a subscriber to a specific form by id.
Create Custom FieldTool to create a new custom field for subscriber data.
Create TagTool to create a new tag in the account.
Create WebhookTool to create a new webhook subscription.
Delete BroadcastTool to delete a specific broadcast.
Delete Custom FieldTool to delete a specific custom field.
Delete SubscriberTool to delete (unsubscribe) a subscriber by id.
Delete TagTool to delete a tag by id.
Delete WebhookTool to delete a webhook by id.
Get AccountTool to retrieve current account information.
Get Account ColorsTool to retrieve list of colors associated with the account.
Get BroadcastTool to retrieve details of a specific broadcast by id.
Get Broadcast StatsTool to retrieve statistics for a specific broadcast by id.
Get Creator ProfileTool to retrieve the creator profile information for the account.
Get Email StatsTool to retrieve email statistics for the account.
List BroadcastsTool to retrieve a paginated list of all broadcasts.
List Custom FieldsTool to retrieve a paginated list of custom fields.
List FormsTool to list all forms.
List SegmentsTool to retrieve a paginated list of segments.
List SequencesTool to retrieve a paginated list of all sequences.
List SubscribersTool to retrieve a list of subscribers.
List Subscribers For FormTool to retrieve subscribers for a specific form by id.
List TagsTool to retrieve a list of all tags.
List Tag SubscribersTool to retrieve subscribers for a specific tag.
Tag SubscriberTool to associate a subscriber with a specific tag by id.
Tag Subscriber by EmailTool to associate a subscriber with a tag using an email address.
Update Account ColorsTool to update the list of colors for the account.
Update Custom FieldTool to update a custom field's label.
Update TagTool to update a tag's name by id.

Way Forward

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

FAQ

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

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

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

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