API: MCP server

Nybero runs a hosted Model Context Protocol server. Point an MCP-capable AI client at it, and the client can read your workspace: template delivery stats, contacts, tags, segments and automations. You can then ask things like “How did our reminder templates perform over the last 30 days?” without building anything.

The MCP server is read-only. It cannot send messages or change data. For that, use the REST API.

Connection details


URL	`https://app.nybero.com/api/mcp`
Transport	Streamable HTTP
Auth	Your workspace API key as `Authorization: Bearer nyb_live_…`

It uses the same API keys as the REST API. Create one under Integrations → API. A key only ever sees its own workspace, and the same rate limit applies (120 requests per minute per key).

Claude Code

claude mcp add --transport http nybero https://app.nybero.com/api/mcp \
  --header "Authorization: Bearer $NYBERO_KEY"

Cursor, Windsurf and other clients

Most clients take a JSON config like this:

{
  "mcpServers": {
    "nybero": {
      "url": "https://app.nybero.com/api/mcp",
      "headers": { "Authorization": "Bearer nyb_live_…" }
    }
  }
}

Tools

Tool	What it returns
`get_workspace`	Id and name of the workspace
`template_stats`	Sent / delivered / read / failed per template, optional `days` and `template_name` (same as `GET /v1/templates/stats`)
`list_templates`	Approved templates
`get_template`	One template’s full content, including body text and button URLs
`list_contacts`	Contacts, filterable by `search`, `tag`, `opt_in_status`, with paging
`get_contact`	One contact by `contact_id` or `phone`, with attributes and tags
`list_tags`	All tags
`list_automations`	Automations and whether they are active
`list_segments` / `segment_contacts`	Segments and the contacts currently in them