-
Notifications
You must be signed in to change notification settings - Fork 21
Integrations
claude-ops supports 11 integrations across two connection models: MCP (OAuth via Claude.ai, zero config) and CLI (command-line tools, usually auto-installed via Homebrew). Some integrations offer both; a few are one-or-the-other only.
| Integration | MCP | CLI tool | Best path |
|---|---|---|---|
| GitHub | — |
gh (auto-installed) |
CLI only — everything requires gh
|
| AWS | — |
aws (auto-installed) |
CLI only — ECS, Cost Explorer, CloudWatch |
| Linear | OAuth via Claude.ai | — | MCP only — fully covered, 12 tools |
| Vercel | OAuth via Claude.ai | — | MCP only — deploy status, logs |
| Slack | OAuth via Claude.ai | local bot token | MCP for most; token adds unlimited search |
| Gmail | OAuth via Claude.ai (read + draft only) |
gog CLI |
CLI for autonomous send/archive |
| Google Calendar | OAuth via Claude.ai (full CRUD) |
gog cal (read only) |
Either works for briefings |
| Sentry | OAuth via Claude.ai | sentry-cli |
MCP covers all current use cases |
| — | wacli |
CLI only — no MCP alternative exists | |
| Telegram | Bundled MCP server (gram.js) | — | Bundled server — setup fully automated |
| GSD | — | auto-detected | Optional — dashboards degrade gracefully without it |
Type: CLI only
Tool: gh — GitHub CLI
Auto-installed: Yes, via Homebrew
GitHub is the backbone of the plugin. The gh CLI is used by 8+ skills for PR management, CI log retrieval, issue triage, and the autonomous merge pipeline. There is no MCP fallback — GitHub requires gh.
What you get:
- Open PR listings with review state, CI status, draft flag
- CI failure logs from GitHub Actions (last 24h)
- Autonomous PR review, conflict resolution, and merge (
/ops:merge) - Issue triage cross-referenced with code (
/ops:triage)
Setup: gh auth login — runs automatically if not authenticated when you first use a skill.
Type: CLI only
Tool: aws — AWS CLI v2
Auto-installed: Yes, via Homebrew
AWS powers the infrastructure health and revenue dashboards. The plugin queries ECS for service health, Cost Explorer for spend tracking, and CloudWatch indirectly via ECS metrics.
What you get:
- ECS cluster and service health (running/desired task counts, stopped tasks)
- Monthly AWS spend by service
- Last 3 months cost trend
- Credits balance and expiry tracking
- Runway estimate based on burn rate
Setup: aws configure or set AWS_PROFILE / AWS_ACCESS_KEY_ID in environment.
Configure your default region in plugin settings: aws_region (default: us-east-1).
Type: MCP only
Connected via: OAuth through Claude.ai
Tools exposed: 12 (list issues, list cycles, list teams, list projects, get issue, save issue, get team, list users, save comment, and more)
Linear is fully covered by MCP. No CLI tool is needed or used.
What you get:
- Current sprint cycle with issues, statuses, assignees
- Create and update issues from within skills
- Cross-reference Linear issues with Sentry errors in
/ops:triage - Sprint progress in
/ops:gomorning briefing
Setup: /ops:setup → Configure MCPs → Linear → OAuth flow opens in browser.
Set your default team key in plugin settings: linear_team (e.g., HEA).
Type: MCP only
Connected via: OAuth through Claude.ai
Tools exposed: list projects, list deployments, get deployment, get build logs, get runtime logs
What you get:
- Recent deployment status per project
- Build log retrieval for failed deploys
- Runtime error logs for production debugging
Setup: /ops:setup → Configure MCPs → Vercel → OAuth flow.
Note: Deploys are triggered via GitHub Actions CI/CD, not directly through the plugin.
Type: MCP (primary) or local bot token (extended)
Connected via: OAuth through Claude.ai / Playwright token extraction
MCP tools: send message, read channel, search, schedule message, read thread, search users
MCP covers most Slack use cases. The local bot token path (via ops-slack-autolink.mjs) adds unlimited search and private channel access without requiring bot membership.
What you get with MCP:
- Read channels, threads, DMs
- Send messages and drafts
- Search public channels
- User profile lookups
What you additionally get with local token:
- Unlimited search (MCP has quota limits)
- Read private channels without explicit bot membership
-
SLACK_MCP_ENABLEDflag enables Slack section in/ops:unread
Setup: /ops:setup → Configure channels → Slack → OAuth (recommended) or token extraction.
Type: MCP (read + draft only) or gog CLI (full)
MCP connected via: OAuth through Claude.ai
CLI tool: gog (not on Homebrew — manual install required)
This is the integration where the choice matters most. MCP can read threads and create drafts but cannot send or archive. The gog CLI enables fully autonomous inbox management.
What you get with MCP only:
- Search inbox, read threads
- Create draft replies (you send manually)
- Calendar read via same OAuth session
What you additionally get with gog CLI:
- Send emails autonomously
- Archive handled threads
- Full
/ops:inbox emailautonomous mode - Multi-account support via
-a account@example.comflag
Setup: /ops:setup → Configure channels → Email → gog auth login (browser OAuth).
Type: MCP (recommended) or gog cal (read only)
Connected via: OAuth through Claude.ai
MCP actually has more features here — it can create events, RSVP, find free time, and list across calendars. The gog cal path is simpler but read-only.
What you get:
- Today's events in the morning briefing
- Upcoming meetings context for
/ops:nextprioritization
Setup: Automatically configured when Gmail MCP is connected (same OAuth scope).
Type: MCP (primary) or sentry-cli (extended)
Connected via: OAuth through Claude.ai
MCP tools: search issues, update issue, get issue details, find projects, find organizations, whoami
Current skills use only the MCP tools. sentry-cli adds release tracking and source map management, which are not used by the current skill set.
What you get:
- Recent unresolved errors in
/ops:fires - Cross-platform triage in
/ops:triage(Sentry + Linear + GitHub) - Auto-resolve issues that are already fixed in code
Setup: /ops:setup → Configure MCPs → Sentry → OAuth.
Set your org slug in plugin settings: sentry_org (e.g., my-org).
Type: CLI only
Tool: wacli
Auto-installed: No — manual install required (source)
WhatsApp has no official API for personal accounts and no MCP alternative. wacli authenticates via QR pairing (similar UX to WhatsApp Web) and uses the WhatsApp Web protocol.
What you get:
- List all non-archived chats with recent activity
- Read messages from specific contacts/groups
- Send messages to contacts
- Contact lookup by name
- Full inbox in
/ops:inbox whatsapp
Setup: /ops:setup → Configure channels → WhatsApp → wacli auth (QR pairing).
Known issue: App-state key desync can occur after extended inactivity. See Troubleshooting.
Type: Bundled MCP server (gram.js MTProto)
Authentication: Your personal account, not a bot
Tools: list_dialogs, get_messages, send_message, search_messages
The plugin ships its own Telegram MCP server in telegram-server/. It authenticates as your personal Telegram account using MTProto — this is required because the Bot API cannot read user DMs.
What you get:
- List all recent conversations (DMs, groups, channels)
- Read messages from specific chats
- Send messages to any contact
- Full-text search across all your chats
- Full inbox in
/ops:inbox telegram
Setup: /ops:setup telegram — fully automated. Enter your phone number, then two codes: one from my.telegram.org and one from the Telegram app. The wizard handles app creation, session generation, and keychain storage.
Credentials flow through plugin settings (telegram_api_id, telegram_api_hash, telegram_phone, telegram_session) — never stored in files.
Known issue: Telegram rate-limits list_dialogs after frequent calls. See Troubleshooting.
Type: Auto-detected companion plugin
Required: No — skills degrade gracefully without it
GSD is a separate Claude Code plugin that adds project roadmap tracking. When installed, claude-ops dashboards automatically show active phases, progress percentages, and next actions per project.
What you get with GSD:
- Active phase shown in
/ops:goand/ops:projects - GSD work included in
/ops:nextpriority stack - YOLO mode COO/CEO agents analyze roadmap state
Setup: /ops:setup → Companion plugins → Install GSD, or manually:
/plugin marketplace add example/get-shit-done
/plugin install gsd@example-get-shit-done