Integrations & APIs
Connect Sundial to the tools your team already uses, and access Sundial programmatically over MCP.
Sundial connects to the tools your team already works in, so agents can pull in the context that lives there, and exposes Sundial itself to other AI clients over the Model Context Protocol (MCP).
This is distinct from Connecting your data, which covers warehouse and data-source connectors (BigQuery, Snowflake, Redshift, and so on).
What's here
| Page | What it covers |
|---|---|
| Tool connectors | Connect Notion, Slack, Linear, and GitHub so agents can read context from them |
| MCP server | Point external AI clients (Claude, Cursor, and others) at Sundial to ask analysis and modelling questions |
| API | Programmatic access to Sundial |
Two directions
- Sundial reaches out: connect a tool like Notion or Linear, and agents can read from it (read-only) as additional context when they answer.
- Tools reach into Sundial: Sundial runs an MCP server, so an external agent or client can ask Sundial's analyst and modeller directly, with your governed context behind every answer.
Connections use OAuth, so you authorize access explicitly and can revoke it at any time.