@egerie/mcp

Local connector that plugs an MCP-capable LLM application (Claude, ChatGPT, Le Chat, Copilot, Cursor…) into the Egerie API MCP server, so you can query your cyber-risk and compliance data in natural language.

It is a thin, auditable bridge: it exposes a local MCP server to your LLM app and forwards tool calls to Egerie over HTTPS, attaching a machine (client_credentials) access token that it mints and refreshes silently. You configure it once with your own Egerie API credentials.

Security at a glance

• No secret is bundled. The connector reads your Auth0 credentials from environment variables at runtime.
• Your credentials never leave your machine, except to your Egerie Auth0 tenant to obtain a token.
• Read-only. Phase 1 exposes read-only tools only.
• Auditable. The whole connector is ~40 lines in a single index.js, built on the official MCP SDK — what you install is the source, readable in node_modules/@egerie/mcp/index.js.

Requirements

• Node.js ≥ 18
• An Egerie API machine-to-machine application (client_id + client_secret) authorized on the Egerie Core API, carrying the tech_admin and compliance permissions.

Configuration

| Variable | Description | |---|---| | EGERIE_MCP_URL | Your Egerie MCP endpoint, e.g. https://<tenant>.egerie.eu/api/api/mcp | | EGERIE_AUTH0_DOMAIN | Your Egerie Auth0 domain, e.g. login.egerie.eu | | EGERIE_AUTH0_AUDIENCE | The Egerie Core API audience | | EGERIE_CLIENT_ID | Your M2M application client id | | EGERIE_CLIENT_SECRET | Your M2M application client secret |

Install

Claude Code / Claude Desktop

claude mcp add egerie \
  --command "npx -y @egerie/mcp" \
  --env EGERIE_MCP_URL=https://<tenant>.egerie.eu/api/api/mcp \
  --env EGERIE_AUTH0_DOMAIN=login.egerie.eu \
  --env EGERIE_AUTH0_AUDIENCE=<audience> \
  --env EGERIE_CLIENT_ID=<client-id> \
  --env EGERIE_CLIENT_SECRET=<client-secret>

Generic MCP client (JSON config)

{
  "mcpServers": {
    "egerie": {
      "command": "npx",
      "args": ["-y", "@egerie/mcp"],
      "env": {
        "EGERIE_MCP_URL": "https://<tenant>.egerie.eu/api/api/mcp",
        "EGERIE_AUTH0_DOMAIN": "login.egerie.eu",
        "EGERIE_AUTH0_AUDIENCE": "<audience>",
        "EGERIE_CLIENT_ID": "<client-id>",
        "EGERIE_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}

How it works

1. On start, it opens a session to your Egerie MCP endpoint and mints an access token from your Auth0 tenant.
2. It re-uses that token until ~1 minute before expiry, then mints a fresh one — no re-login, no manual step.
3. Your LLM app talks to the local connector; the connector relays tool listing and tool calls upstream.

Publishing (maintainers)

Tag a version (vX.Y.Z) — the GitLab CI publish job runs npm publish --access public using the NPM_TOKEN masked CI variable (a granular npm token scoped to this package).