Integrations · observability

Connect Better Stack to Well

Connect Better Stack to make it reachable from conversation and your agents in Well. Better Stack exposes no structured records to sync today, so this is a reach connection, not a data feed.

Connect Better StackSee what Well does

What Well pulls from Better Stack

Better Stack feeds Better Stack into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Better Stack’s access.

From Better Stack		In Well	Relation
Better Stack		Workspace context	Reachable from

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Better Stack → Well

What Well does with your Better Stack connection

Connect

Connect Better Stack over OAuth (MCP DCR): Well registers a client through Better Stack's OAuth Dynamic Client Registration and you approve on Better Stack's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Connecting Better Stack makes it reachable from your workspace; Better Stack exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Better Stack adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Better Stack is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Better Stack unlocks

Ask in plain language. Well answers from your connected Better Stack connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Better Stack connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Better Stack connection…

1 agent skill runs on Better Stack.

Well lists Better Stack in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Better Stack

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Better Stack in three steps

01
Authorise Better Stack via MCP
From Well's Connections panel, search for Better Stack and click Connect. Well discovers Better Stack's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Better Stack's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Make it reachable
The connection puts Better Stack within reach of your workspace and its agents. Better Stack exposes no structured record for Well to map into an invoice, transaction, or account today, so there is no records table to set up and Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach Better Stack in the same place it reaches the rest of your stack. If Better Stack later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Better Stack stays secure with Well

Well connects to Better Stack's MCP server via the Model Context Protocol. The MCP server handles credential issuance through OAuth Dynamic Client Registration, so Well never holds a long-lived Better Stack secret. Because Better Stack maps no structured entity today, the token simply makes Better Stack reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Better Stack.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Better Stack records
Resources the Better Stack MCP server exposes, scoped by your OAuth approval.
granted
Reach Better Stack from your workspace
The grant makes Better Stack reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Better Stack.
granted
Modify or delete Better Stack records
Not granted; Better Stack is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Better Stack passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Better Stack’s admin panel.

Frequently asked questions about Better Stack and Well

How do I connect Better Stack to Well, and how long does it take?

Choose Better Stack in Well's Connections panel and authorise it over its MCP server. Well discovers the OAuth metadata from the MCP endpoint and registers a client via Dynamic Client Registration, so there are no keys to paste. The handshake completes in about a minute and puts Better Stack within reach of your workspace and its agents.

What does Well sync from Better Stack today?

No structured record, and the page is candid about that. Better Stack exposes no supported target model for Well to turn into an invoice, transaction, or account, so there is no records table to configure and nothing is pulled into your workspace. The connection is about reach, not a data feed.

If nothing is synced, what does connecting Better Stack give me?

It lets an agent working in your workspace reach Better Stack in the same place it reaches the rest of your stack, instead of treating it as a separate destination. This is a reach-and-availability connection: honest about not pulling structured records that Better Stack does not expose.

Will Better Stack ever bring records into the workspace?

Only if and when Better Stack exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller; if that changes, the data-flow section would reflect the real entities.

What happens if I disconnect Better Stack?

Disconnecting Better Stack in Well revokes the OAuth token and ends the MCP reach immediately. Because nothing structured was being synced, there are no workspace records to retain or purge; it simply removes Better Stack from the set of tools your agents can reach through Well.