# Monitor as code, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** Defining a data monitor as configuration kept in a repository instead of clicking it together in a UI. An agent can draft the configuration from a description, and a person reviews it before it ships. Per Sifflet's README, the get_monitor_code_by_description tool returns a monitor configuration for a plain-language description and needs the Editor role on the domain.

## Definition

Defining a data monitor as configuration kept in a repository instead of clicking it together in a UI. An agent can draft the configuration from a description, and a person reviews it before it ships.

## Example from a real server

**Example.** Per Sifflet's README, the get_monitor_code_by_description tool returns a monitor configuration for a plain-language description and needs the Editor role on the domain.

## Related terms

- [OAuth 2.1 authorization for MCP](/glossary/oauth-2-1-authorization-for-mcp/): The sign-in flow the MCP specification defines for HTTP servers.
- [persona scoping](/glossary/persona-scoping/): Limiting what an agent can see or do by the persona of the signed-in person, such as admin, member or guest.
- [metadata graph](/glossary/metadata-graph/): A connected store of data assets and their relationships: tables, columns, dashboards, owners and the links between them.

## Where to read more

- [The directory](/)
- [All glossary terms](/glossary/)

## Sources

- github.com/siffletdata/sifflet-mcp/blob/main/README.md: https://github.com/siffletdata/sifflet-mcp/blob/main/README.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/glossary/monitor-as-code/
