Google Chat

https://docs-dev.evohub.io/mcp

claude mcp add --transport http evohub-docs-docs https://docs-dev.evohub.io/mcp

{
  "mcpServers": {
    "evohub-docs-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs-dev.evohub.io/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "evohub-docs-docs": {
      "url": "https://docs-dev.evohub.io/mcp"
    }
  }
}

{
  "servers": {
    "evohub-docs-docs": {
      "type": "http",
      "url": "https://docs-dev.evohub.io/mcp"
    }
  }
}

EvoHub can post On-Call alerts to a Google Chat space. Each alert arrives as a card with its title, severity, status, source and start time, and buttons to acknowledge it, resolve it or open it in EvoHub. Everything about one alert stays in one thread. Google Chat runs alongside paging: it never replaces the phone calls, push notifications and emails your escalation policies send.

Google Chat messages are free: they are not counted towards your usage.

#Add a Google Chat space

The URL is a credential — its key and token let anyone post to your space. EvoHub stores it encrypted and never shows it again. Only https://chat.googleapis.com/v1/spaces/…/messages URLs with both key and token are accepted.

Adding, testing and removing chat channels needs the On-Call settings permission.

#Where alerts are posted

• Every new alert — tick Every new alert on the space in Chat Channels.
• From an escalation step — open the escalation policy, click Edit, and in the step's Chat area pick the space. The step still pages its target; the post is in addition. See Escalation policies.

An alert is posted to a space once, even if both apply.

#Acknowledge and resolve from Google Chat

Cards posted through a webhook can only open links, so the Acknowledge and Resolve buttons open EvoHub in your browser. You confirm the action there, signed in as yourself:

• You need permission to respond to alerts. If the alert belongs to a team, you must be in that team, be an admin, or be the person the alert is assigned to.
• Each button link works once and expires after 24 hours. After that, use Open in EvoHub instead.

The action is recorded on the alert's timeline under your name, for example "Acknowledged from Google Chat."

#When the alert changes

A webhook cannot edit a card it has posted. When the alert is acknowledged, taken over or resolved — anywhere — EvoHub replies in the alert's thread, for example "Resolved by Ada Lovelace: Disk full on db-1". In a space without threads, the reply is posted as a new message.

Google Chat accepts one message a second per space; EvoHub waits and retries once when it is asked to slow down. Text from the alert is shown as plain text: formatting and mentions in an alert's title or description are not applied.

#Remove a space

In On-Call → Chat Channels, click the bin icon next to the space and confirm. Escalation steps that named it post nowhere until you choose another channel. Delete the webhook in Google Chat as well if you no longer need it.

#Related

• Mattermost
• Slack
• Escalation policies