Skip to navigation

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

  • New page: Connect an AI assistant (MCP). 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.
  • 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, 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.