SpireAssists has moved: SpireAssists MCP and SpireAssists Local

The SpireAssists GPT has moved. OpenAI is retiring custom GPTs, so SpireAssists now works inside the AI assistant you already use: Claude, ChatGPT, Claude Code, Codex or GitHub Copilot. It comes in two parts, and both are free.

1. SpireAssists MCP: search Spire’s documentation

SpireAssists MCP answers questions about how Spire works and how to build on it, from an indexed library of Spire resources rather than the open web. Your assistant is told to search it before relying on general knowledge, to say which Spire version an answer is based on, and to link the sources it used.

• Hosted for you: sign in once with Google or Microsoft.
• It never sees your own Spire data.
• Works in Claude (desktop app and claude.ai), ChatGPT, Claude Code, Codex and GitHub Copilot.

What it searches

• Spire user manuals for Spire 3.13 and Spire 4.1, kept separate so Spire 3 and Spire 4 answers aren’t mixed up.
• Release notes, up to Spire 4.1.1 and 3.13.15.
• Spire support articles.
• Spire training videos: full transcripts, time-stamped so an answer can point you to the right minute.
• Spire API reference and API basics.
• Spire API behaviour: what the API actually does, tested against a live Spire 4.1.1 server. Required fields, defaults, errors and how to fix them, and which database tables each call writes.
• Spire database schema for Spire 3.10 to 3.13, 4.0 and 4.1: tables, columns, views and functions.
• API ↔ database map: the database column behind each API field and the API field behind each column, verified against a live Spire 4.1.1 server.
• Crystal Reports: the SQL, formulas and subreports of Spire’s standard reports.
• Spire 4 reports built on Spire’s JSX report framework.
• SpireAssists Gold: practical tips that fill gaps in the official documentation.

2. SpireAssists Local: work with your own Spire data

SpireAssists Local lets your assistant read your own Spire company data, such as customers, orders and inventory, through your Spire server’s API and database. It changes data only if you allow it.

• It runs on your own Windows computer. You type your Spire passwords into a setup page on that computer; they’re kept in Windows Credential Manager and are never shown to your assistant or sent to SpireAssists.
• Connections are read-only unless you turn on Allow changes. Do that only for a test or sandbox company.
• Works in the Claude desktop app, Claude Code, Codex and GitHub Copilot on Windows. (Not ChatGPT, the Claude website or mobile apps, and not yet macOS or Linux.)
• Records your assistant looks up become part of your chat, so they go to your AI provider like anything else you type.

Use both for the best results: your assistant looks up the right Spire names in the documentation first, then uses them on your own data.

Getting started

The easiest way is to let your assistant do it. Paste this into Claude, ChatGPT, Claude Code, Codex or GitHub Copilot:

Set up SpireAssists for me by following https://spireassists.com/connect/agent.txt

It asks which parts you want. Claude Code, Codex and Copilot set things up for you; in Claude and ChatGPT your assistant walks you through the steps. To do it yourself, see Connect SpireAssists and SpireAssists Local.

Privacy

SpireAssists MCP sees only the search requests your assistant sends to it and the name and email you sign in with, not your conversation. SpireAssists Local talks to your own Spire server, plus a once-a-day check for a newer version; it sends nothing to SpireAssists. Details are in our privacy policy.

Feedback

• About a specific answer: type SA report: followed by why you’re reporting it, for example “SA report: these are the Spire 3 steps, I’m on Spire 4”. Your assistant sends us the answer, how it got it and your reason.
• Anything else: email peter@wright-stuff.com.

Thank you to everyone who used the SpireAssists GPT.