Integrations · AnalyticsConnect LunarCrush to Well
Bring LunarCrush social-sentiment scores, influencer activity, and token signals into Well, joined to the assets and topics you track.
What Well pulls from LunarCrush
LunarCrush feeds social signal, asset, post into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke LunarCrush’s access.
| From LunarCrush | In Well | Relation | |
|---|---|---|---|
| Social signal | Engagement record | Feeds | |
| Asset | Instrument | Resolves to | |
| Post | Audit attachment | Captures as |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- LunarCrush → Well
What Well does with your LunarCrush connection
Connect
Connect LunarCrush over OAuth (MCP DCR): Well registers a client through LunarCrush's OAuth Dynamic Client Registration and you approve on LunarCrush's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings social signal, asset, and post in from LunarCrush on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each LunarCrush entity into engagement record, instrument, and audit attachment, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from LunarCrush lands in the workspace as engagement record, instrument, and audit attachment you can search, chart, and automate.
Questions LunarCrush unlocks
Ask in plain language. Well answers from your connected LunarCrush connection, resolved against the rest of your stack.
Ask anything about your LunarCrush connection
Ask about your LunarCrush connection…
Connect LunarCrush in three steps
- 01
Authorise LunarCrush via MCP
From Well's Connections panel, search for LunarCrush and click Connect. Well discovers LunarCrush's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on LunarCrush's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverlunarcrush.ai/mcp
- 02
Map your entities
Well's MCP client discovers social signal, asset, and post from LunarCrush that LunarCrush's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on LunarCrush records. Because LunarCrush ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical LunarCrush records happens in the background.
How LunarCrush stays secure with Well
Well connects to LunarCrush's MCP server (lunarcrush.ai/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived LunarCrush secret. Tokens are scoped to the social signal, asset, and post LunarCrush exposes and refreshed server-side. Reads only, Well cannot modify or delete LunarCrush records.
- granted
Read LunarCrush records
Resources the LunarCrush MCP server exposes, scoped by your OAuth approval.
- granted
Resolve social signal, asset, and post across your stack
Match identifiers in LunarCrush against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete LunarCrush records
Not granted; LunarCrush is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store LunarCrush passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about LunarCrush and Well
From Well, open Connections, find LunarCrush, and click Connect. Well discovers the OAuth metadata at lunarcrush.ai/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on LunarCrush's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in social signal, asset, and post from LunarCrush and reshapes each entity into your workspace: social signal becomes engagement record; asset becomes instrument. Every record arrives with the source identifier preserved, so LunarCrush stays the source of truth while Well lets you query the data alongside the rest of your stack.
Each LunarCrush sentiment score, influencer mention, and token social-volume signal is linked to the matching asset or topic in your workspace. Ask "show me the social-sentiment trend for the tokens we follow" and Well returns the time series with social-volume and influencer context.
Well watches for updates to social signals and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right engagement record. Edits flow in incrementally; nothing is duplicated, and the LunarCrush source identifier is retained on every revision.
Well combines live LunarCrush events with periodic reconciliation reads of social signal, asset, and post. New rows appear within seconds when LunarCrush pushes them; periodic reads catch anything a push missed. The first connect backfills history from LunarCrush in the background.
Open Connections > LunarCrush in Well and click Disconnect. Well calls LunarCrush's token revocation endpoint and stops calling LunarCrush immediately on its side; provider-side propagation to LunarCrush's admin panel varies by provider. The social signal, asset, and post Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
LunarCrush records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with LunarCrush
More in Analytics
Popular cross-category
Ready to connect LunarCrush?
Connect once. Every social signal, asset, post from LunarCrush becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.