Skip to main content
A hands-on workshop for developers and technical integrators: drive Ana programmatically through the REST API, stream responses into your apps, automate playbooks and dashboards from code, expose Ana inside Claude/Cursor/ChatGPT via MCP, and extend Ana outward with MCP tools. Hands-on format: copy-paste curl/Python, checkpoints. ~2 hours.

​
What you’ll be able to do

The Chat API

Sync, SSE streaming, retrieval — the agentic loop as an endpoint.

Resource APIs

Connectors, playbooks, dashboards as code; the ETL-completion trigger.

Sandbox API

Warehouse data into DataFrames; your code in Ana’s environment.

Ana as MCP server

Warehouse answers inside Claude, Cursor, and your IDE.

MCP tools

Extend Ana with Notion, GitHub, Jira — or your internal APIs.

Production patterns

Identity design, timeouts, cost, testing nondeterminism.

​
Prerequisites

  • API key access (Settings → Configuration → API Keys; creation may be role-gated)
  • curl or Python + requests; an MCP client for Modules 4–5
  • A connected data source
API shapes follow the current reference at docs.textql.com. Python SDK: TextQLLabs/textql-python. VPC deployments substitute their own host.
T-minus-1-day pre-flight: run the workshop’s key prompts end-to-end in the session workspace — confirm logins, connectors, and the features this workshop touches are enabled for every attendee; have a fallback demo workspace ready in case a customer connector fails live. Pacing: when a long prompt is running (2–4 min), fire it first, then discuss the concept while Ana works — never watch a spinner in silence. If behind schedule, cut sections marked optional, never the checkpoints. Group sessions: attendees drive, you narrate; collect every miss or wrong answer in a shared doc — that list is the ontology backlog. With 10+ attendees on one warehouse, stagger the heavy prompts.