moberghr/beacon

Database monitoring and governed AI access for .NET.
Scheduled SQL checks, alerting and data movement, with an MCP server that gives AI assistants
project-scoped, read-only, masked and audited access to your data.
Documentation ·
Cookbooks ·
MCP ·
Integrate ·
Security ·
What's new in 5.0
Sample data from Beacon's mock mode ( npm run dev:mock ).
## Overview
Beacon is an operations layer for your databases, your team and your AI assistants. It connects to PostgreSQL, SQL Server, MySQL, Azure Synapse, Snowflake, BigQuery, Databricks, CloudWatch and REST APIs, and provides the following capabilities.
Monitoring: multi-step SQL checks run on a cron schedule. Steps can span engines and are joined in memory.
Alerting: results are delivered by email, Microsoft Teams, Slack, Jira or webhook. Tasks are opened when a check fails and resolved when it passes, and statistical anomalies are flagged.
AI access: a Model Context Protocol (MCP) server lets Claude, Cursor, VS Code and other MCP clients explore and query your data through a single governed path.
Data movement: when enabled, audited Insert, Upsert and Truncate-Load jobs write into data sources that an Admin has designated as write targets.
Beacon runs as a self-hosted reference application or inside your own ASP.NET Core application through the Moberg.Beacon. NuGet packages, using your sign-in, job runner and deployment.
> New in 5.0: the MCP gateway. Moberg.Beacon.Gateway turns your own ASP.NET Core application into an MCP server:
> people connect Claude, sign in with Microsoft Entra, and Claude calls your endpoints as them, through your own
> authorization, with every call audited. See What's new in 5.0.
## Choose your path
| You want | Start with | Hand it to your AI |
| AI clients acting as your own application's users, through your endpoints | MCP gateway recipe | llms-gateway.txt |
| Beacon's data product in your application: monitoring, alerts, data movement, MCP over your databases | Integrate Beacon | llms-integrate.txt |
| Claude Code, Cursor or VS Code on a Beacon that is already running | Connect a coding agent | connect-coding-agent.md |
| One specific task: single sign-on, a saved query as a tool, Slack alerts, … | Cookbooks | llms-cookbooks.txt |
| To see it first | Run it locally or browse the screenshots | |
## Start with AI
Most integrations are done with a coding agent, and the docs are written for that. Paste the prompt for your goal into
Claude Code, Cursor or any coding agent working in your repository:
text
Add an MCP gateway to this ASP.NET Core app with Beacon.
Read https://moberghr.github.io/beacon/llms-gateway.txt first and follow it step by step.
Ask me before every decision it marks as one.
text
Integrate Beacon into this ASP.NET Core app.
Read https://moberghr.github.io/beacon/llms-integrate.txt first and follow its checklist step by step.
Ask me before every decision the guide marks as one.
With Claude Code, install Beacon's plugin and just ask: its skills (beacon-integrate, beacon-gateway,
beacon-tool, beacon-entra) fetch the current guides and follow them.
text
/plugin marketplace add moberghr/beacon
/plugin install beacon@moberg-beacon