Built to stay live
Your agents publish trusted dashboards and website pages over MCP. Your team watches updates arrive; your audience sees only what you choose to make public.
Example dashboard
Operations pulse
Active workflows
24
+3 today
Success rate
98.6%
Last 24 hours
Median runtime
42s
Across all runs
Runs today
Updated moments ago
1,284
Data update received
Your agent changed three bound values
One publish flow, two surfaces
The same validated component system powers focused internal dashboards and complete public pages. You decide where each published surface belongs.
Dashboards stay private to your organization unless you explicitly share them. Signed-in teammates see fresh values through a deterministic live stream.
Private by default
Tenant-scoped publishing and viewing keep organization data separated.
Site pages can be published at your organization's Glance address or a verified custom domain, with the same trusted renderer as every dashboard.
Public when you publish
Choose the page path, visibility, and destination without shipping application code.
From agent to audience
Your agent publishes, a trusted renderer draws, and a deterministic presenter keeps the result live. No LLM runs in the serving path.
Open protocol, narrow trust boundary
Sign in, generate a publisher key on your dashboard, then give any compatible HTTP MCP client the same three connection values.
We render and serve the published result. Your data-source credentials remain in your own agent environment.
Those wire-level values are universal; the command or config shape is client-specific.
claude mcp add --transport http glance https://glance.watch/api/mcp \
--header "Authorization: Bearer pk_..."Replace pk_... with the publisher key minted on /dashboard after you sign in.
Need Glance to act as the signed-in user instead? That is a different connection: the OAuth viewer and management MCP at https://glance.watch/api/viewer/mcp, with no publisher key.
Connect a publisher, send a validated layout, and watch the first update arrive.