Connect SpireAssists

SpireAssists gives your AI assistant two separate things. Set up either one, or both. Both are free.

1. SpireAssists MCP

Search Spire's documentation

  • Answers “how does Spire work?” from Spire's manuals, support articles, videos, database and API reference, and reports.
  • Hosted for you: sign in once with Google or Microsoft.
  • Never sees your own Spire data.
  • Works in Claude, ChatGPT, Claude Code, Codex and GitHub Copilot.
Set up SpireAssists MCP ↓

2. SpireAssists Local

Work with your own Spire data

  • Reads your own customers, orders, inventory and more, and makes changes only if you allow them.
  • Runs on your own Windows computer; your Spire passwords stay there.
  • Read-only unless you turn on changes.
  • Works in the Claude desktop app, Claude Code, Codex and GitHub Copilot (not ChatGPT).
Set up SpireAssists Local →

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.

In Claude Code, Codex or Copilot in VS Code, one step sets up both: follow Set up SpireAssists Local and it adds SpireAssists MCP too. In the Claude desktop app, GitHub Copilot CLI and ChatGPT, set up SpireAssists MCP separately.

Let your assistant set it up. Paste this into your assistant (Claude Code, Codex, GitHub Copilot, Claude or ChatGPT). It asks which parts you want, then sets them up for you, or walks you through the steps if it can't do them itself: Set up SpireAssists for me by following https://spireassists.com/connect/agent.txt

Set up SpireAssists MCP (search)

Coming from the SpireAssists GPT? SpireAssists has moved. OpenAI is retiring Custom GPTs, so the GPT no longer answers Spire questions. Set up SpireAssists MCP below to keep the same knowledge, and more, in ChatGPT or Claude. It takes a few minutes.

You'll need this address:

https://mcp.spireassists.com/mcp

Claude

Add SpireAssists once, on the Claude website or in the Claude desktop app: the steps are the same. A connector added in one also appears in the other and in the mobile app.

  1. Go to claude.ai (or open the Claude desktop app) and open Settings → Connectors.
  2. Choose Add custom connector.
  3. Name it SpireAssists MCP and paste the address above. If Claude shows sign-in options, keep the detected defaults: Sign in now and Register automatically. Leave any client ID or request header fields empty.
  4. Click Add, then Connect. A SpireAssists sign-in page opens. See Signing in.

Custom connectors may depend on your Claude plan. If you don't see the option, check your plan or ask your Claude workspace administrator.

ChatGPT

These steps work on every ChatGPT plan, including Free. There's no Developer mode step any more: if an older guide mentions one, skip it.

Set it up on chatgpt.com in a web browser, not in the ChatGPT desktop app: the desktop app can't finish the connection. Once connected, SpireAssists also works in the ChatGPT desktop and mobile apps.

  1. On chatgpt.com, open Settings → Plugins (called Apps or Connectors in some versions) and click +. Choose the option to add a custom MCP server. A New Plugin window opens with an upload area: ignore that and click Create MCP App at the bottom left. Enter the name SpireAssists MCP and paste the address above.
  2. Set Authentication to OAuth. ChatGPT fills in the rest automatically. Don't enter a client ID or secret, and leave Base scopes empty.
  3. Tick the confirmation box and click Create.
  4. Go to Settings → Plugins → SpireAssists MCP, click Connect if it isn't connected yet, and sign in. If you started in the desktop app, do this step on chatgpt.com.
Plugins + doesn't offer a custom MCP server? Custom servers aren't available on every ChatGPT account or in every region yet. Use Claude instead, with the same address and sign-in.
Using the ChatGPT desktop app? The desktop app can create the plugin, but its Authenticate button doesn't connect it to your chats. Finish with Connect on chatgpt.com (step 4). Until you do, ChatGPT will say it can't find SpireAssists' tools.

Claude Code

These steps work for Claude Code in a terminal and for the Claude Code extension in VS Code: both share the same settings. In a terminal (in VS Code: Terminal → New Terminal):

claude mcp add --transport http spireassists https://mcp.spireassists.com/mcp

Then in Claude Code (start claude in the terminal, or open the Claude Code panel in VS Code), type /mcp, choose spireassists and Authenticate. Your browser opens the sign-in page.

Codex

These steps work for the Codex CLI and for OpenAI's Codex extension in VS Code: both share the same settings. In a terminal:

codex mcp add spireassists --url https://mcp.spireassists.com/mcp

Then sign in:

codex mcp login spireassists

Your browser opens the sign-in page. In the VS Code extension you can instead open MCP settings from the gear menu and click Authenticate next to spireassists.

VS Code (GitHub Copilot)

Using Claude Code or Codex in VS Code? Follow Claude Code or Codex above instead.

  1. Open the Command Palette (Ctrl+Shift+P) and run MCP: Open User Configuration to use SpireAssists MCP in every workspace. Or create .vscode/mcp.json in a project to use it there only.
  2. Add SpireAssists MCP to the servers section:
    {
      "servers": {
        "SpireAssists MCP": {
          "type": "http",
          "url": "https://mcp.spireassists.com/mcp"
        }
      }
    }
    If the file already has other servers, add just the "SpireAssists MCP": { … } entry inside servers, with a comma between entries.
  3. Save. VS Code shows a Start link above the entry. Click it. When VS Code asks to sign in, allow it: your browser opens the SpireAssists sign-in page.
  4. In Copilot Chat, switch to Agent mode. SpireAssists MCP's tools appear in the tools list.

Signing in

  1. The SpireAssists sign-in page tells you which app is asking to connect (for example ChatGPT or Claude) and where you'll be sent back to. If you didn't start this, close the page.
  2. Choose Continue with Google or Continue with Microsoft, then pick your account.
  3. The first time, Google or Microsoft asks whether SpireAssists may see your name and email address. Accept. SpireAssists never sees your password and gets no access to your email, files or anything else in your account.
  4. You're returned to your assistant, now connected. You won't need to sign in again unless you disconnect or stop using SpireAssists for a long time.

Microsoft 365 work accounts

Some organizations only let employees connect apps their IT administrator has approved. If Microsoft shows “Need admin approval”, send this page to your Microsoft 365 administrator. An administrator (Global, Application or Cloud Application Administrator) can approve SpireAssists for everyone at once: they sign in to SpireAssists themselves, and on Microsoft's permission screen tick Consent on behalf of your organization before accepting. SpireAssists only asks for the basic sign-in permissions: name, email address and profile.

Alternatively, sign in with Google, or with a personal Microsoft account.

Using it

Giving feedback

Troubleshooting

Questions or problems: peter@wright-stuff.com. How we handle your information: Privacy policy.