How to integrate Appveyor MCP with Hermes

GET STARTED FOR FREE
Appveyor 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 Appveyor 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 Appveyor 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 Appveyor 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 Appveyor

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

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

5. Done!

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

The Appveyor MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Appveyor account. It provides structured and secure access to your CI/CD pipelines, so your agent can perform actions like managing builds, retrieving artifacts, listing projects, and overseeing users and roles on your behalf.

  • Project and build discovery: Quickly list all your Appveyor projects and their build jobs, making it easy for your agent to monitor or summarize your CI activity.
  • Artifact retrieval: Direct your agent to fetch build artifacts after a job completes, so you can automate download or inspection workflows without manual intervention.
  • Deployment environment overview: Ask your agent to enumerate all available deployment environments, helping you plan and automate deployment tasks with up-to-date environment data.
  • User and team management: Effortlessly list all users in your Appveyor account, making it simple to audit team membership or automate notifications and permissions.
  • Role inspection and permission management: Let your agent retrieve and review roles and their details, enabling automated governance checks and streamlined access control workflows.

Supported Tools & Triggers

Tools
Get Build ArtifactsTool to get the list of artifacts for a specific build job.
Get EnvironmentsTool to get a list of all deployment environments.
Get ProjectsTool to get a list of all projects for the authenticated account.
Get RoleTool to retrieve details of a specific role.
Get RolesTool to retrieve all roles in the account.
Get UsersTool to retrieve all users in the account.

Way Forward

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

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Appveyor MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Appveyor MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Appveyor MCP with Claude Code

Codex logo

Codex

Use Appveyor MCP with Codex

OpenClaw logo

OpenClaw

Use Appveyor MCP with OpenClaw

CLI logo

CLI

Use Appveyor MCP with CLI

Google ADK logo

Google ADK

Use Appveyor MCP with Google ADK

LangChain logo

LangChain

Use Appveyor MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Appveyor MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Appveyor MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Appveyor MCP with LlamaIndex

CrewAI logo

CrewAI

Use Appveyor MCP with CrewAI

FAQ

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

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

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

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

Book a call↗Get started for free