Skip to main content
Summation hosts a Model Context Protocol (MCP) server that exposes your workspace to MCP-capable agents — Claude, Codex, or anything that speaks streamable HTTP:

​
What it exposes

A curated set of non-destructive tools over the public API, including:
  • Analyst — ask data questions in natural language (ask_analyst), with multi-turn follow-ups
  • Catalog — search and describe tables, views, connections, and lineage; preview data
  • Query — bounded, read-only SQL execution
  • Reports — generate, validate, and export reports
  • Files — upload, download, and import files to tables
  • Playbooks & schedules — list, create, pause, resume, and trigger recurring runs
Tools that send email (like schedule creation) describe that in their tool definition so agents confirm recipients first. The server is stateless — no session affinity required.

​
Authentication

Every request needs a Summation bearer credential in the Authorization header.
Easiest path: the Claude plugin registers this server automatically when you sign in — no manual configuration at all.
To connect manually, you need a credential:
  • Your own session — sign in through the Addison plugin (/addison:signin); it stores a device-login credential locally.
  • A machine credential — ask your Summation admin for API credentials, then exchange them for an access token via the Public API.

​
Claude Code

​
Codex

In ~/.codex/config.toml:

​
Other MCP clients

Any client that supports streamable HTTP with a custom Authorization header works the same way. The server advertises its metadata at:
Browser-based OAuth sign-in is coming. The server already returns the standard 401 challenge with resource metadata; once the authorization server ships, MCP clients that implement the MCP authorization spec will sign in with a browser flow — no header configuration needed.

​
Scopes

Tokens carry scopes that gate tool access: A valid token without the required scope gets a 403 with the missing scope named.

​
Behavior notes

  • Long-running tools return one buffered result. Analyst questions, report generation, and validation take roughly 15–60 seconds and arrive as a single response. Set client tool timeouts to at least 120 seconds.
  • Auth errors mean an expired or revoked credential — mint a fresh one and update the header.
  • Include the request_id from any error when contacting support; it joins your client-side failure to server-side traces.