> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmcpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Channels

> Where anything the product wants to tell you goes.

Returns the catalogue, this person's switches for the personal channels, and the account's Slack and Discord connections. Each channel carries `scope` — `personal` fans out one delivery per recipient, `shared` delivers once per firing, because posting the same message to the same Slack channel once per team member is the same message five times.

`delivers` is the honest answer to "is anything actually sent here". Only `in_app` is true: email, Slack and Discord record deliveries and queue them, and no job drains any of them yet.

A connection's webhook URL is never returned — `webhook_hint` is a masked form, enough to recognise which webhook it is and useless to anyone who reads the response.



## OpenAPI

````yaml https://api.getmcpulse.com/docs/openapi.json get /v1/account/channels
openapi: 3.1.0
info:
  title: MCPulse API
  version: 1.0.0
  description: >-
    Analytics for MCP servers.


    The API is the product — the dashboard is one client and an MCP server will
    be another. Every number here is computed server-side so that both get the
    same answer.


    **Two kinds of auth.** Ingest uses an MCP API key (`mp_live_…`). Everything
    else uses a Supabase access token from the browser session.
servers:
  - url: https://mcpulse-production.up.railway.app
    description: MCPulse API
security: []
tags:
  - name: ingest
    description: What the customer's server sends
  - name: mcps
    description: MCPs and ownership
  - name: metrics
    description: Everything the dashboard reads
  - name: keys
    description: Ingest API keys
  - name: account
    description: Account, team and usage
paths:
  /v1/account/channels:
    get:
      tags:
        - account
      summary: Get Channels
      description: >-
        Where anything the product wants to tell you goes.


        Returns the catalogue, this person's switches for the personal channels,
        and the account's Slack and Discord connections. Each channel carries
        `scope` — `personal` fans out one delivery per recipient, `shared`
        delivers once per firing, because posting the same message to the same
        Slack channel once per team member is the same message five times.


        `delivers` is the honest answer to "is anything actually sent here".
        Only `in_app` is true: email, Slack and Discord record deliveries and
        queue them, and no job drains any of them yet.


        A connection's webhook URL is never returned — `webhook_hint` is a
        masked form, enough to recognise which webhook it is and useless to
        anyone who reads the response.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                nullable: true
        '401':
          description: Invalid or missing token
        '403':
          description: Your role does not permit this

````