> Tillcast is live: the API at https://api.tillcast.com/v1 and the dashboard at https://dashboard.tillcast.com. A key prints on real printers, so do not call the API unless asked. A job carries its receipt as "document", an array of blocks (the recommended way), or as "receiptline", ReceiptLine text, exactly one of the two: read https://docs.tillcast.com/create-a-print-job.md and https://docs.tillcast.com/concepts/documents.md before you write a job body. Do not code against what does not exist yet: webhooks, a template language, stored templates (a job has no template field), OAuth connections and connectors for Make, Zapier and n8n, and OAuth sign-in for the MCP server. SDKs for TypeScript (@tillcast/sdk, version 0.2.0 or later for blocks) and Python (tillcast) exist as pre-1.0 versions. To show a receipt in a web page without printing, there are the npm packages @tillcast/preview and @tillcast/html-render (0.x, no API key, no call to Tillcast to draw): read https://docs.tillcast.com/preview-a-receipt.md. The docs are the source of truth: check the index https://docs.tillcast.com/llms.txt and https://docs.tillcast.com/roadmap.md before you code against anything. For clean Markdown of any page, append .md to the page URL. The Tillcast MCP server is live at https://api.tillcast.com/mcp and takes an API key as a bearer token (setup: https://docs.tillcast.com/connect-an-ai-assistant.md). It acts on the live account and its tools print on real paper, so do not connect to it or call its tools unless the owner asked you to. The MCP server at https://docs.tillcast.com/_mcp/server is a different one: it only searches these docs and cannot call the Tillcast API.

## The MCP server is announced: connect an AI assistant with an API key

* **New page: [Connect an AI assistant (MCP)](/connect-an-ai-assistant).** Tillcast runs an MCP server at `https://api.tillcast.com/mcp`. An AI assistant that can send an `Authorization` header connects with an API key as the bearer token and gets 28 tools for customers, locations, printers and jobs, and `preview_document`, which draws a receipt without printing it. A key is shown only the tools its scopes allow, so a key with the Read only preset sees 10 tools and cannot print. The page has the setup for Claude Code, Codex CLI, Gemini CLI, Cursor, VS Code, Zed and Claude custom connectors, says which of them Tillcast tried and which follow the vendor's documentation only, and lists the scopes to give, the safety notes and the troubleshooting.
* **Not yet.** OAuth sign-in for the MCP server is planned and not available, so an assistant that offers only OAuth sign-in, such as ChatGPT, cannot connect today. See the [roadmap](/roadmap).
* **Unchanged.** The REST API, the API reference and the SDKs are as they were. The contract does not list the MCP tools: the tools describe themselves to the client. A key prints on real paper, and there is still no test mode.
* **Agents.** [Build with an agent](/build-with-an-agent), the `AGENTS.md` snippet and the note at the top of every Markdown page now name the MCP server and tell an agent not to connect to it or call its tools unless the owner asked.
* **Update 2026-10-25.** Tillcast has no test mode.