MetriBeacon
Menu

Use the API, CLI or MCP with deliberate access.

Connect monitoring to your workflow

Connect your tools through API, CLI or MCP. Read results, send data and manage monitors with scoped access.

Free to use · view quotas
MetriBeaconExample workspace

Check your native agent and its connection.

metribeacon agent status

What you can monitor

Three ways to make the result useful

Connect results, incidents and status updates. Data gaps stay visible.

Use a stable API

Use documented operations with scoped access. Keep credentials private.

Keep scripts predictable

Use structured CLI output. Job wrappers preserve the command’s result.

Connect a supported client

Connect local or remote MCP. Start with read access and grant more scopes when needed.

Understand your data

The same workspace, whichever tool you choose

Use documented operations and stable identifiers. Review results before retrying changes. Automations use the same permissions and quotas as the account area.

Read the setup guide
MetriBeaconExample workspace

Check your native agent and its connection.

metribeacon agent status

Your first steps

Your first steps

Connect your source in three steps.

  1. 01

    Choose a tool

    Follow the API, CLI or MCP guide for your environment.

  2. 02

    Grant scoped access

    Choose a workspace and the minimum required permissions.

  3. 03

    Plan, apply and verify

    Inspect the intended change, apply it and read the resulting monitor.

Good to know

Frequently asked questions

Answers and setup guides.

Are prompts collected automatically?
No. Workflow monitoring does not automatically collect prompts, full logs or control commands.
Does MCP bypass workspace roles?
No. Resources, scopes and workspace permissions are checked by the same service.

Your next step

Make the next step clear

Choose your setup and connect your first source.