How to integrate Control d MCP with Hermes

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Control d 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 Control d 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 Control d 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 Control d 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 Control d

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

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

5. Done!

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

The Control d MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Control d account. It provides structured and secure access to your DNS filtering and device management environment, so your agent can perform actions like managing devices, enforcing policies, retrieving analytics, and monitoring network access on your behalf.

  • Device inventory management: Easily list all devices on your account or remove specific devices by their identifier for streamlined device control.
  • Profile and rule administration: Direct your agent to delete profiles, custom rules, or schedules—helping you maintain and enforce up-to-date network policies.
  • Network access monitoring: Retrieve a list of known access IPs to keep tabs on which endpoints are connecting to your network infrastructure.
  • Analytics endpoints discovery: Quickly fetch available analytics storage regions and endpoints so you can integrate and analyze DNS traffic data efficiently.
  • Organization details access: Have the agent fetch and present your organization's account details for easy reference and auditing.

Supported Tools & Triggers

Tools
Delete Device by IDPermanently delete a Control-D device/endpoint by its ID.
Delete ProfilePermanently deletes a Control D profile by its unique identifier (PK).
Delete Profile Rule by Rule IDDelete a custom DNS rule from a Control D profile by its rule identifier (hostname/domain).
Delete Rule from FolderDelete a custom DNS rule from a specific folder in a Control D profile.
Delete Profile ScheduleTool to delete a specific schedule within a profile.
List Known Access IPsList up to the latest 50 IP addresses that were used to query against a specific Device (resolver).
Get Analytics EndpointsTool to list analytics storage regions and their endpoints.
Get Analytics LevelsTool to retrieve available analytics log levels for Control D devices.
Get Billing PaymentsTool to retrieve billing history of all payments made.
Get Billing ProductsRetrieve all products currently activated on the Control D account.
Get DevicesLists all Control D devices (endpoints) associated with the account.
Get Device TypesList all allowed device types in Control D.
Get IPTool to retrieve the current IP address and datacenter information for the API request.
Get Network StatsTool to retrieve network stats on available services in different POPs (Points of Presence).
Get Organization MembersTool to view organization membership.
Get Organization DetailsTool to view the authenticated organization's details.
Get Sub-OrganizationsTool to view sub-organizations and their details.
Get ProfilesTool to list all profiles associated with the authenticated account.
Get Profile OptionsRetrieves all available configuration options for DNS profiles in Control D.
Get Profile by IDTool to retrieve details of a specific profile by its ID.
Get Profile AnalyticsRetrieve analytics data for a Control D profile.
Get Profile Analytics LogsRetrieves DNS query activity logs for a specific Control D profile.
Get Analytics Log EntryTool to retrieve a specific analytics log entry by its ID.
Get Profile Analytics SummaryTool to fetch a summary of analytics data for a given profile.
Get Profile Analytics Top DomainsTool to fetch top domains accessed within a specific profile.
Get Profile Top ServicesTool to fetch top services accessed within a profile.
Get Profile FiltersList all native (Control D curated) filters for a profile and their current states.
List External Filters for ProfileTool to list third-party filters for a specific profile.
Get Profile FoldersList all rule folders (groups) within a Control D profile.
List Custom DNS Rules for ProfileRetrieve custom DNS rules for a Control D profile.
Get Specific Rule in FolderTool to retrieve a specific rule within a folder by its ID.
Get Profile SchedulesTool to list schedules associated with a specific profile.
Get Profile ScheduleTool to retrieve a specific schedule by its ID within a profile.
Get Profile ServicesTool to list services associated with a specific profile.
Get ProxiesTool to retrieve the list of usable proxy locations that traffic can be redirected through.
Get Service CategoriesList all available service categories in Control D.
List Services by CategoryRetrieves all services within a specific ControlD service category.
Get UsersRetrieve the authenticated user's account information from Control D.
Create DeviceCreate a new device (DNS endpoint) in Control D.
Create ProfileCreate a new blank profile or clone an existing one.
Create Custom DNS RuleCreate custom DNS rules for a profile to control domain resolution.
Create Custom Rules in Profile FolderTool to create custom rules within a specific folder for a profile.
Create Profile ScheduleCreate a new time-based schedule within a Control D profile.
Modify DeviceModify an existing Control D device's settings.
Modify OrganizationModify organization settings such as name, contact details, website, and device limits.
Modify ProfileModify an existing profile by its ID.
Bulk Update Profile FiltersTool to bulk update filters on a specific profile.
Update External Filters for ProfileTool to update external filters for a specific profile.
Modify Profile FilterModify the enabled state of a specific native filter on a profile.
Modify Custom Rule for ProfileModify an existing custom DNS rule for a profile in Control D.
Update Custom Rule by Rule IDTool to update an existing custom rule by its ID.
Move Profile Rule to FolderTool to move a specific custom rule into a different folder.
Update Profile ScheduleTool to update a specific schedule within a profile.
Modify Service for ProfileTool to modify a specific service rule for a profile.

Way Forward

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

FAQ

What are the differences in Tool Router MCP and Control d MCP?

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

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

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