Skip to content

Beaam

Official status unknown81 tools reported1 source

Beaam keeps watch over the services behind your product and brings forward only what needs attention. Use the connector to inspect current health, review monitoring coverage, investigate incidents and likely causes, manage watchlists and alert rules, and test notification delivery. Calls are scoped to the connected Beaam organization. Read-only and destructive actions are annotated independently so Claude can ask for confirmation when appropriate. Beaam supports Cloudflare, Vercel, Netlify, Supabase, Neon, MongoDB Atlas, Sentry, Stripe, Polar, Resend, DigitalOcean, Hostinger, HTTP endpoints, and MCP servers. It can also connect providers, schedule maintenance, route notifications, and help apply a monitoring plan generated from a project. Every tool uses the same capability layer as the Beaam web app and API, under row-level security scoped to the signed-in organization. Billing, subscription changes, API-key issuance, and organization administration are deliberately not exposed.

Connection details

  • Remote endpoint

    Official status unknown

    Transport not established · Authentication not established

    https://app.beaam.app/api/mcp

    Use the source documentation for installation instructions. No command has been inferred.

    Connection source and version

    Reported by Claude logoClaude connector directory

81 tool names reported

Source-declared tools. Availability can depend on the connection and permissions; these are not runtime test results.

Claude connector directory ↗ · Observed 2026-11-01 · Completeness not established

  • acknowledge_incident
  • acknowledge_welcome
  • add_incident_note
  • apply_monitoring_plan
  • begin_aws_connect
  • begin_oauth_connect
  • cancel_maintenance_window
  • check_aws_registration
  • check_coverage
  • check_oauth_connect
  • connect_aws
  • connect_cloudflare
  • connect_digitalocean
  • connect_hostinger
  • connect_http
  • connect_mcp
  • connect_mongodb
  • connect_neon
  • connect_netlify
  • connect_polar
  • connect_resend
  • connect_sentry
  • connect_stripe
  • connect_supabase
  • connect_vercel
  • create_stack
  • delete_integration
  • delete_notification_channel
  • delete_stack
  • detection_stats
  • explain_incident
  • get_activation_progress
  • get_collector_health
  • get_health_grid
  • get_health_timeline
  • get_incident
  • get_ingest_stats
  • get_integration_catalog
  • get_monitoring_health
  • get_service
  • get_status_board
  • list_alerts
  • list_checks
  • list_connections
  • list_detection_rules
  • list_devices
  • list_incidents
  • list_integration_rules
  • list_integrations
  • list_maintenance_windows
  • list_notification_channels
  • list_planned_connections
  • list_recent_changes
  • list_services
  • list_stacks
  • list_suppressions
  • next_connection
  • plan_monitoring
  • query_metrics
  • rediscover_integration
  • register_device
  • remove_missing_services
  • rename_service
  • rename_stack
  • resolve_oauth_connect
  • review_alert
  • save_notification_channel
  • schedule_maintenance_window
  • send_test_alert
  • set_collector_mode
  • set_detection_rule
  • set_integration_rule
  • set_service_mute
  • set_service_notifications
  • set_service_stack
  • set_service_watched
  • set_watchlist
  • snooze_incident
  • unregister_device
  • update_integration_settings
  • vote_integration

Sources and provenance

Grouping basis: endpoint. Exact endpoints or package sets can be grouped automatically; other relationships require evidence review. This does not verify publisher affiliation, connection health, or equivalent capabilities.

Search API Tracker

Curated starting points