Sundial

MCP server

Point external AI clients at Sundial over MCP to ask analysis and modelling questions with your governed context.

Sundial exposes a Model Context Protocol (MCP) server, so AI clients you already use, Claude, Cursor, and other MCP-capable tools, can query Sundial directly. Instead of copying data around, your client asks Sundial, and Sundial answers using your governed semantic layer, playbooks, and context.

What it exposes

Connecting to Sundial's MCP server gives a client two tools:

  • ask_sundial_analyst: ask analytical questions (the same capability as the Analysis Agent), with follow-ups.
  • ask_sundial_modeler: ask the Data Modelling Agent about, and make changes to, your semantic layer and models.

Because these run inside Sundial, answers keep the same grounding and trust signals you get in the app; your external client gets governed analytics, not a raw warehouse pipe.

Connecting

The MCP server uses OAuth, so there's nothing to configure beyond the endpoint URL: point your client at it, leave any authentication field blank, and complete the OAuth prompt using the same login you use for Sundial. Once authorized, the client can call the tools on your behalf.

Endpoint URL

Use the endpoint for your deployment:

  • AWS: https://production.us-east-2.api.sundial.work/context-engine/mcp
  • GCP (US): https://sundial-gcp-prod.us-central1.api.sundial.work/context-engine/mcp
  • GCP (EU): https://sundial-gcp-eu-prod.europe-west1.api.sundial.work/context-engine/mcp
  • On-premises: contact Sundial.

Client setup

Sundial connects like any other remote (HTTP) MCP server. The examples below use the AWS endpoint — substitute the URL for your deployment.

Claude Desktop — an organization admin can add a custom connector (name it anything, e.g. sundial) pointing at the endpoint URL, then complete the OAuth prompt.

Claude Code (docs):

claude mcp add --transport http sundial https://production.us-east-2.api.sundial.work/context-engine/mcp

Codex (docs):

codex mcp add sundial --url https://production.us-east-2.api.sundial.work/context-engine/mcp

If you hit any issues connecting, reach out to Sundial on Slack.

When to use this

Use the MCP server when you want Sundial's answers inside another agent or workflow, for example asking Sundial from your coding assistant, or composing Sundial into a larger multi-tool agent. To work the other way, letting Sundial read from your other tools, see Context connectors.

On this page