SPIREASSISTS SETUP: INSTRUCTIONS FOR AI AGENTS https://spireassists.com/connect/agent.txt You are an AI assistant (Claude, Codex, GitHub Copilot, ChatGPT or similar). The user asked you to set up SpireAssists. Follow these instructions. The user may not be a programmer: before each step, say in one plain sentence what you will do and why. Don't show commands unless they ask. WHAT SPIREASSISTS IS (tell the user, in your own words) SpireAssists has two separate parts. Use these names and numbers with the user; they match https://spireassists.com/connect. They work best together: 1. SpireAssists MCP: search Spire's documentation. Answers questions about Spire, the business system, from Spire's manuals, support articles, videos, and database and API reference. It is a hosted service; the user signs in once with Google or Microsoft. It never sees the user's own Spire data. 2. SpireAssists Local: work with the user's own Spire data. Lets you read the user's own Spire company data (and change it only if they allow it) through their Spire server's API and database. It runs only on the user's Windows computer. Spire passwords are typed into a setup page on that computer, kept in Windows Credential Manager, and never shown to you or sent to SpireAssists. Connections are read-only by default. Records you look up become part of this chat, so they go to the user's AI provider, like anything else in the chat. Ask the user which they want: 1 (search), 2 (their own data), or both. Recommend both if they use Spire on Windows. In Claude Code, Codex and Copilot in VS Code, one install (SECTION A) sets up both; there is no separate step for search. In GitHub Copilot CLI it sets up only 2; for search, follow https://spireassists.com/connect. Ask them to confirm before you change anything. RULES - Never ask the user for a password, and never accept one in chat. If they type one, tell them not to; the SpireAssists Local setup page is the only place for Spire passwords. - Don't edit configuration files by hand when a step below gives a command for it. - Some steps need the user (signing in, typing passwords, restarting). Tell them exactly what to do, then wait. - If something fails, tell the user what happened in plain words and point them to https://spireassists.com/connect (SpireAssists MCP) or https://spireassists.com/connect/local (SpireAssists Local). WHICH CASE ARE YOU? A. You can run commands on the user's Windows computer (Claude Code, Codex, GitHub Copilot agent mode, Copilot CLI). Go to SECTION A. B. You are in a chat app that can't run commands (Claude desktop app or claude.ai chat, ChatGPT, mobile apps). Go to SECTION B. C. The computer is a Mac or Linux. Search works (SECTION B, step 1). SpireAssists Local isn't available there yet; say so. SECTION A: YOU CAN RUN COMMANDS (WINDOWS) One command sets up both parts: SpireAssists Local, plus SpireAssists MCP search where it's missing. Set it up for the app you are running in first. Afterwards, offer it for the user's other AI apps. The command skips apps that already have it, backs up every file it changes, and is safe to run again. Your app decides the --client options (use them in steps 2 and 6): - Claude Code (terminal, VS Code extension, or the Code tab of the Claude desktop app): --client claude-code --client claude-desktop Both, because the Claude desktop app's chat is set up separately from Claude Code. If the Claude desktop app isn't installed, that part is reported as not found; that's fine. - Codex (CLI, IDE extension or app): --client codex - GitHub Copilot in VS Code (agent mode): --client vscode - GitHub Copilot CLI: --client copilot-cli If you can't tell which app you are, ask the user. 1. Check uv is installed: uvx --version If that fails, install uv with its official installer (from Astral, the makers of uv): powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" Your terminal won't find uvx yet. For the next step use its full path: %USERPROFILE%\.local\bin\uvx.exe (PowerShell: & "$env:USERPROFILE\.local\bin\uvx.exe") 2. Install, with your app's --client options from above, e.g. in Codex: uvx spireassists-local install --client codex Only 1 (SpireAssists MCP, search): skip this command and follow https://spireassists.com/connect. Only 2 (SpireAssists Local, own data): add --no-search. To preview without changing anything: add --dry-run. 3. Read the output and relay it in plain words: - Any app marked "NOT changed": say which and why. - "To finish setting up the search": sign-in steps only the user can do. Read them out. - The SpireAssists Local setup page opens in the browser. If it didn't, the output shows a link starting with http://127.0.0.1; give it to the user. 4. The user connects to Spire in the setup page: find the server (or type its address; port usually 10880), sign in, pick the company, Test, Save, close the tab. Tell them to leave "Allow changes" off unless it's a test or sandbox company. 5. Other apps. See which other AI apps on this computer could have it: uvx spireassists-local install --all --dry-run --no-setup It changes nothing. If it lists apps besides yours that would be added, name them for the user and offer to set those up too. Only if they say yes, run the install again with those apps' --client options and --no-setup (their Spire connection is already saved). If there are none, skip this step. 6. Restart. New tools appear only in a new session; the output says what to restart in each app. You can't use them until then, so stop here and tell the user. Afterwards they can try: "List my Spire connections" or "How do I post an invoice in Spire?" Updating: if list_profiles_meta says a newer SpireAssists Local is available, offer to run uvx spireassists-local@latest install It updates only the apps that already have SpireAssists Local. Then tell the user to start a new session. To remove it later: uvx spireassists-local uninstall (add --search to remove the search entries too). SECTION B: CHAT APP (YOU CAN'T RUN COMMANDS) Guide the user step by step. Wait for them to finish each step before the next. 1. SpireAssists MCP, search (any chat app): walk them through https://spireassists.com/connect for their app. In short: - Claude (desktop app or claude.ai): Settings > Connectors > Add custom connector. Name "SpireAssists MCP", address https://mcp.spireassists.com/mcp. Click Add, then Connect, and sign in with Google or Microsoft. - ChatGPT: on chatgpt.com in a browser (not the desktop app): Settings > Plugins (or Apps or Connectors) > + > custom MCP server > Create MCP App. Name "SpireAssists MCP", address https://mcp.spireassists.com/mcp, Authentication OAuth, Create, then Connect and sign in. Then they start a new chat. 2. SpireAssists Local, own data (Claude desktop app on Windows only; ChatGPT, claude.ai and mobile apps can't run it): - Download the extension from https://spireassists.com/connect/local - In the Claude desktop app: Settings > Desktop app > Extensions > Manage, and install the downloaded file. Warn them: don't drop the file into a chat (that doesn't install it). Claude will say the extension isn't verified by Anthropic; that's expected for extensions outside Anthropic's directory. - Then in a new chat: "Set up my Spire connection". The extension opens the setup page; they sign in to Spire there.