Hermes

Use runStdioMcpServer to expose Corsair as a local MCP server that Hermes spawns on demand. The Corsair side is identical to every other harness. The only difference is where you register the server in Hermes.

Install

npm install @corsair-dev/mcp

Create the server script

mcp-server.ts

import 'dotenv/config';
import { runStdioMcpServer } from '@corsair-dev/mcp';
import { corsair } from './corsair';

runStdioMcpServer({ corsair }).catch((err) => {
    console.error('[corsair-mcp] Fatal:', err);
    process.exit(1);
});

Configure Hermes

{
  "mcpServers": {
    "corsair": {
      "command": "npx",
      "args": ["tsx", "mcp-server.ts"]
    }
  }
}

If your credentials aren’t loaded from a .env file, add an env block with CORSAIR_KEK.

Register this under Hermes’s MCP configuration. Check the Hermes docs for the exact config path, as it differs per version.

Usage

Once connected, Hermes can call Corsair tools directly:

Setup corsair, then list all Slack channels.

Hermes calls list_operations to discover available endpoints, get_schema to inspect parameters, then run_script to execute.

npm install @corsair-dev/cli

yarn add @corsair-dev/cli

pnpm install @corsair-dev/cli

bun add @corsair-dev/cli

Copy and paste this prompt into Hermes to give it everything it needs to work with Corsair:

Run `pnpm corsair` to access Corsair's integrations.

Get Started

Frameworks

Adapters

Workflows (beta)

Reference

Install

Create the server script

Configure Hermes

Usage

​Install

​Create the server script

​Configure Hermes

​Usage

Install

Create the server script

Configure Hermes

Usage