Ask your assistanthow production is doing.

Connect

Add Beaam as a remote MCP server in your assistant's connector settings:

https://app.beaam.app/api/mcp

Authentication is OAuth 2.0 with PKCE and dynamic client registration, so there is no key to paste and nothing long-lived to leak. Your assistant opens a browser, you approve access to your Beaam account, and the connection is scoped to you.

What it can and cannot do

91 of 131 operations are exposed to assistants. The remaining 40 are deliberately withheld.

Billing and administrative operations are never reachable over MCP — an assistant cannot change your subscription, and organization-wide admin tooling is not registered at all. Operations that change or remove something you already have carry a destructive hint, so a compliant assistant asks before running them; operations that only add something — connecting a provider, creating a stack, sending a test alert — do not. The rule is enforced in code, and a conformance test fails the build if a new capability is added without a title, an end-user description, or the right destructive flag.

Full list, with the mcp badge marking what is exposed:API reference.

Worth asking it

• “Is anything wrong with my stack right now?”
• “What broke last week, and did I get alerted?”
• “Which services am I watching, and which are quiet?”
• “Send a test alert so I know delivery works.”

This is the same capability layer behind the web app and the API — the assistant is not reading a scraped dashboard, it is calling the product.