Skip to content

Use MCP Server to Create Alert Schema

Use this guide when you want to create an Alert Schema from a real payload in an MCP-based workflow.

This path is practical when your team wants to automate schema creation, script repeatable tests, or pair schema work with an AI assistant.

Before you start

You need:

  • an API Token with configuration write access
  • your organization UID for X-Org-Context
  • one representative firing payload from your Alert Producer
  • MCP client access to the 1stLine MCP Server

You can manage API tokens in Access Control.

Steps

  1. Connect your MCP client to https://1stline.burava.com/api/mcp.
  2. Send Bearer authentication (Authorization or X-Authorization) and set X-Org-Context.
  3. Run create_schema_creation_token.
  4. Run create_alert_schema_from_payload with:
    • token from step 3
    • payload set to your real sample alert body
  5. Save the new schema UID from the tool response.
  6. Test extraction quality with test_alert_schema_patterns using the same payload.
  7. If needed, apply updates with update_alert_schema and re-run tests.
  8. Open Alert Schemas and review the new schema.
  9. Send one real test alert and open Alert Instances to confirm the alert is created or updated correctly.
  10. If the alert stays orphaned, create a Routing Rule for that schema.

What to check before rollout

  • required fields for your routing and communication logic are extracted
  • Fingerprint Fields identify repeated alerts correctly
  • receiver destination and transformation behavior match your Alert Receiver expectations