Ironbrain.Mcp 0.2.6

Ironbrain.Mcp (ironbrain-mcp)

stdio MCP server for the Ironbrain platform (HITL Outbox). Bots authenticate with an Ironbrain account (Supabase JWT) and enqueue actions for human confirmation — they do not hold IMAP/SMTP secrets.

Distinct from Ironbrain.MailCal.Mcp / ironbrain-mailcal (local mail/calendar with adapter secrets on the bot host).

Prefer this package (or HTTP POST /api/mcp) over MailCal when the same capability exists on the platform — secrets stay server-side and Freigabe stays in Ironbrain.

Current package version: 0.2.6 (polished OAuth local callback + platform CTA).
nuget.org may lag until Trusted Publishing ships 0.2.6 — see docs/mcp.md § Maintainer publish.

dotnet tool update -g Ironbrain.Mcp
# pin when needed:
dotnet tool update -g Ironbrain.Mcp --version 0.2.3

Restart the MCP server (or start a new Cloud Agent thread) so tools/list refreshes.

Bot bootstrap (catalog visibility)

After Connect / auth succeeds:

1. Call whoami → check authenticated and short capabilitiesSummary (readyToolCount, availableWriteActionCount, canEnqueueSendEmail, allowMcpConfirm, hint).
2. Call list_available_actions → full catalog (same as GET /api/capabilities: accounts, tools, actions + availability / reasonCode / HITL fields).
3. Only then call enqueue_* / read tools. Do not fall back to MailCal MCP just because the catalog was never queried.

Cloud Agents: prefer remote Streamable HTTP at https://app.ironbrain.de/api/mcp (same tools). Stdio ironbrain-mcp is for local desktop / optional Cloud fallback.

Changelog

0.2.6

• OAuth callback page: branded success/error HTML on the local redirect host (http://127.0.0.1:8765/callback) with a CTA to app.ironbrain.de.

0.2.5

• enqueue_save_draft: IMAP APPEND into Drafts with \Draft (no SMTP send). From = IMAP account identity. Default HITL AllowAuto @ confidence ≥ 0.8.
• get_email: returns To, Cc, Message-ID (via API + Ironbrain.Email 0.1.3).

0.2.4

• enqueue_forward_email: ForwardEmail HITL; original attachments fetched on confirm.

0.2.3

• NuGet ↔ HTTP parity: ship connector admin tools, enqueue_mcp_tool, enqueue_trash_email, reject_action that were already on POST /api/mcp / main but not on nuget.org 0.2.1.
• Docs: bot bootstrap via whoami.capabilitiesSummary + list_available_actions; prefer platform MCP over MailCal.
• Includes 0.2.2 OAuth authorize redirect_uri fix (never published separately).

0.2.2

• Fix OAuth authorize redirect_uri double-encoding (%253A… → invalid_redirect_uri). Authorize URL is built with a single EscapeDataString pass; browser open uses /usr/bin/open argv on macOS. Plain IRONBRAIN_OAUTH_REDIRECT_URI only (not pre-encoded).
• Default OAuth scopes → openid only until custom ironbrain.* scopes are registered on the Supabase OAuth client (prod currently returns unsupported scope: ironbrain.api). Override with IRONBRAIN_OAUTH_SCOPES when allowlisted.

0.2.1

• get_action: GET /api/outbox/actions/{id} — bots learn approve vs deny (terminal statuses) and read grantToken after Freigabe confirm.
• Read tools accept pending_freigabe envelopes when HITL ≠ AllowAlways; optional confidence / rationale; after confirm re-call with grantToken (sent as X-Ironbrain-Read-Grant).
• Docs: docs/mcp.md, docs/outbox.md §7.2.

0.2.0

• Documents and ships the full MailCal platform-parity tool set already on main (email reads, calendar reads, move/archive/reply/add-appointment enqueue).
• Calendar reads: multi-calendar still requires calendarId per call — no silent all-calendar aggregate (web merges after per-id).
• whoami returns structured auth/connection errors (auth_failed / connection_failed + hint) instead of opaque MCP failures; auth probe uses capabilities only.
• tools/list confirm-gate fails open (hides confirm_action) when the capabilities probe errors, so discovery is not blocked by a brief API outage; HTTP clients use a 15s timeout.
• OAuth 2.1 + PKCE (Supabase AS): preferred auth via IRONBRAIN_OAUTH_CLIENT_ID; dual support with legacy password grant / IRONBRAIN_ACCESS_TOKEN (IRONBRAIN_AUTH_MODE=auto|oauth|legacy). See docs/mcp-oauth.md.

0.1.0

• Initial platform MCP: whoami, list_pending_actions, enqueue_send_email, capabilities catalog.

Tools (v0.2.5)

Today’s calendar (per calendar)

Multi-calendar accounts must query one calendar at a time. Do not assume MCP aggregates all calendars (the web UI merges after per-id fetches; an optional MCP helper is not in this package yet).

1. list_calendars
2. For each calendar id → list_appointments(date="today", calendarId=<id>, range="day")
3. Merge / present results in the client if you need a combined “today” view

Install / update (refresh Cursor mcp.json)

After NuGet publish (Trusted Publishing / PM) or from a local pack:

# From nuget.org (after Trusted Publishing of 0.2.3)
dotnet tool update -g Ironbrain.Mcp
# or first-time:
dotnet tool install -g Ironbrain.Mcp

# From a packed nupkg (pre-publish / CI artifact)
dotnet tool update -g Ironbrain.Mcp --add-source /path/to/nupkg-dir --version 0.2.3
# or:
dotnet tool install -g Ironbrain.Mcp --add-source /path/to/nupkg-dir --version 0.2.3

Then point Cursor MCP command at ironbrain-mcp (on PATH after global install) and restart the MCP server so the tool list refreshes.

Pack from repo:

dotnet pack Ironbrain.Mcp/Ironbrain.Mcp.csproj -c Release -o ./artifacts

Do not publish to NuGet until Product Manager / Mattanja GO. Publish only via GitHub Actions Trusted Publishing (OIDC) — no classic API keys. See docs/mcp.md § Maintainer publish.

Auth

Preferred: OAuth 2.1 Authorization Code + PKCE against Supabase Auth (AS). Ironbrain.Api is the Resource Server only — no Ironbrain /oauth/token. See docs/mcp-oauth.md.

IRONBRAIN_AUTH_MODE=auto|oauth|legacy (default auto: prefer OAuth when oauthClientId is set). Soft warnings in logs / whoami when legacy is used.

Also set IRONBRAIN_API_BASE_URL (default https://localhost:7065/api). For local HTTPS with a dev cert, set IRONBRAIN_ALLOW_INSECURE_TLS=true.

Config file alternative: ~/.config/ironbrain/platform.json or $IRONBRAIN_PLATFORM_CONFIG (oauthClientId, optional refreshToken).

See docs/mcp.md and docs/mcp-oauth.md.

Cursor MCP snippet

{
  "mcpServers": {
    "ironbrain": {
      "command": "ironbrain-mcp",
      "env": {
        "IRONBRAIN_API_BASE_URL": "https://localhost:7065/api",
        "IRONBRAIN_ALLOW_INSECURE_TLS": "true",
        "IRONBRAIN_SUPABASE_URL": "http://127.0.0.1:54321",
        "IRONBRAIN_SUPABASE_ANON_KEY": "<anon-key>",
        "IRONBRAIN_OAUTH_CLIENT_ID": "<public-client-id>"
      }
    }
  }
}

Demo path

1. Call list_available_actions (or whoami for a short summary) — expect allowMcpConfirm: false by default.
2. Bot calls enqueue_send_email (optional accountId from the catalog).
3. Open ironbrain-web → Outbox (/outbox) — Freigabe still works with MCP confirm disabled.
4. Confirm / Edit / Reject. Confirm runs SMTP with the account’s platform email settings.

Without SMTP configured, enqueue returns a structured missing_smtp / missing_config error and creates no Outbox row.

To enable MCP confirm (customer risk acceptance): org admin PUT /api/organizations/{id}/mcp-confirm with { "allowMcpConfirm": true }.