How to connect Claude to Sage 100: a step-by-step guide
David Helon, Co-founder and COO·10 min read
To connect Claude to Sage 100, give it read-only access to Sage's database through the ODBC driver Sage already ships, then serve that access to Claude as an MCP server. The catch is reach: Claude connects from Anthropic's cloud, and Sage usually sits on a server in your office. The safe way across is a connection that opens from your side, outbound only.
TL;DR
- Pick the route that fits where Sage runs and who'll maintain it. Four options are compared below.
- Create a read-only Sage login and decide which tables the AI may read. Payroll can stay off the list.
- Connect over ODBC through a tunnel that opens from your network, so no port faces the internet.
- Add the MCP server to Claude as a custom connector, and ask questions in plain English.
- Keep writes out of Sage. Anything going back in becomes an import file a person approves.
You'll need: someone with access to the Sage server (often your Sage partner), a read-only login, and a Claude plan that allows custom connectors.
Key facts: connecting Claude to Sage 100
- Where Claude's custom connectors connect from: Anthropic's cloud, so the server must be reachable from the public internet [Anthropic Help Center, 2026]
- How Sage 100 Standard and Advanced expose data: A read-only ODBC driver over the ProvideX data files; Premium runs on Microsoft SQL Server [WYRE AI, 2026]
- Default port for Sage 100 Advanced client/server ODBC: 20222 [Sage 100 Installation Guide, 2024]
- How Visual Integrator treats a bad import record: Every item is validated before files update; a record that fails is skipped and logged [Sage 100 Help, 2023]
- Share of US businesses using AI in any function: 19.8% (period ending 3 May 2026); 33.9% in finance and insurance [US Census Bureau, 2026]
Why connecting Claude to Sage 100 is harder than it looks
Most teams that use Claude already have the connectors for their cloud apps. HubSpot, Slack and Google Drive each take a sign-in. Sage 100 is different, for one reason: where it lives.
In a typical install, Sage 100 runs on a server in the office, often looked after by an outside Sage partner. Claude's custom connectors don't connect from your laptop. They connect from Anthropic's infrastructure, and Anthropic's own documentation is plain about the consequence: "Servers hosted on a private corporate network, behind a VPN, or blocked by a firewall won't connect, even if you can reach them from your own machine" [Anthropic Help Center, 2026].
So the question everyone asks Claude, "what's our aging this month?", gets answered from whatever someone exports and pastes in. That's why most business AI still drafts rather than answers. In Census Bureau research, writing, document analysis and information search were the leading uses of generative AI at work, and 57% of firms using AI had it in three or fewer business functions [US Census Bureau, 2026].
Signs you need this
- One or two people hold the Sage login, and every number goes through them.
- Someone exports the aging report on Monday and retypes it into a spreadsheet.
- Your team pastes the same Sage export into Claude every week, and it's out of date by Wednesday.
- Nobody wants to open a port on the Sage server, and they're right.
Quotable fact: Claude's custom connectors reach your server from Anthropic's cloud, so a Sage 100 server on a private office network won't connect unless something bridges it [Anthropic Help Center, 2026].
Four ways to connect Claude to Sage 100
There's more than one sensible route. Which is right depends on who'll maintain it and how many people need answers.
1. A local ODBC MCP server in Claude Desktop
An open-source MCP server runs on one Windows machine, uses Sage's ODBC driver, and talks to Claude Desktop. Projects like mcp-odbc document a Sage 100 Advanced setup with a read-only flag [mcp-odbc on GitHub, 2026].
- Good for: one technical person who wants answers on their own machine, free.
- Watch out for: it only works in Claude Desktop on that machine, and someone has to install and maintain it.
2. Open the server to Anthropic's IP ranges
Anthropic publishes the IP addresses its connectors come from, and you can allowlist them so a remote MCP server inside your network becomes reachable [Anthropic Help Center, 2026].
- Good for: an IT team that already runs public services and wants its own server.
- Watch out for: you're opening an inbound path to your accounting system, and you still have to build and host the MCP server.
3. Query an analytics warehouse that already models Sage
If you already copy Sage into a reporting warehouse, some of those vendors now offer an MCP server on top of the modeled data.
- Good for: companies that already pay for a warehouse and a reporting team.
- Watch out for: you're asking about the warehouse's copy, on its refresh schedule, and the setup is a project of its own.
4. An outbound-only tunnel to a hosted MCP server
A small service on your network opens a connection out to a hosted platform, which reads Sage read-only and serves it to Claude. Nothing listens for incoming traffic. This is how altspark does it, with a service called altbot.
- Good for: teams with no engineer to spare who want everyone, not one person, asking.
- Watch out for: someone still has to install the service and grant a read-only login.
Comparison
- Local ODBC MCP in Claude Desktop: Who can ask: One machine; Opens your network?: No; Who maintains it: You; Best for: A single analyst
- Allowlist Anthropic's IPs: Who can ask: Anyone with the connector; Opens your network?: Yes, inbound; Who maintains it: Your IT team; Best for: IT teams that host services
- Analytics warehouse with MCP: Who can ask: Anyone with access; Opens your network?: Depends on the vendor; Who maintains it: Warehouse vendor and your team; Best for: Companies with a warehouse already
- Outbound tunnel to a hosted server: Who can ask: Anyone you invite, any AI tool that supports MCP; Opens your network?: No, outbound only; Who maintains it: The platform; Best for: Teams with no engineer free
Our recommendation: if one person needs answers and can maintain a local server, route 1 is free and fine. If the whole team needs answers, use an outbound-only route, so nobody opens a port to the ledger.
How to connect Claude to Sage 100, step by step
The steps below follow route 4, the one that keeps your network closed. Steps 1 and 2 apply to every route.
Step 1: Find out which Sage 100 edition you run
Sage 100 Premium keeps its data in Microsoft SQL Server; Standard and Advanced use ProvideX data files read through Sage's ODBC driver [WYRE AI, 2026]. The route in is different for each, so check first.
How to do it:
- Ask your Sage partner which edition you run, or check the product's About screen.
- For Advanced, check whether the client/server ODBC driver is enabled under Library Master, Setup, System Configuration [Sage 100 Installation Guide, 2024].
- Write down who looks after the server: your IT person or your Sage partner.
Step 2: Create a read-only login and choose the tables
The AI should read exactly what it needs and nothing more.
How to do it:
- Create a Sage user, or a SQL Server login on Premium, that's used only for the AI connection.
- List the questions you want answered (receivables, open orders, supplier spend), then the tables behind them.
- Leave payroll and anything sensitive off the list.
Pro tip: start with three or four questions. You can add tables later, and a short list is easier for your controller to approve.
Step 3: Install the connector on your network
With altspark, someone with access to the network installs altbot, a small service that opens an outbound-only connection, with a separate switch for databases, internal web services and files. It's included on every plan.
How to do it:
- Pick a machine on the same network as the Sage server.
- Install altbot and switch on the database tunnel only.
- Confirm nothing new is listening for inbound traffic.
Step 4: Connect Sage 100 over ODBC, read-only
Through altbot, altspark reads SQL Server, PostgreSQL, MySQL and any ODBC source, which covers every Sage 100 edition. altspark runs only single read (SELECT) statements against a database, and altbot checks again on your network.
How to do it:
- In your altspark project, add a database connection and choose ODBC (or SQL Server for Premium).
- Enter the read-only login and pick the allowed tables.
- Choose which tables to sync into altspark on a schedule, so they can be joined with your CRM or invoice inbox.
Example: sync the aging and open orders nightly, then ask "which customers over 60 days have open orders this month?" in one question.
Step 5: Add the MCP server to Claude
Every altspark project comes with its own MCP server, built and hosted for you.
How to do it:
- In Claude, go to Customize, then Connectors, and add a custom connector with your project's server URL [Anthropic Help Center, 2026]. On Team and Enterprise plans, an Owner first adds it under Organization settings, then Connectors, and each person then connects from Customize, then Connectors.
- In ChatGPT, add it as a custom plugin; most other AI tools take it as an MCP server.
- If a team should see only part of Sage, use roles to limit which data stores they see, or build a separate server for them in Designer MCP, altspark's custom MCP server builder.
Step 6: Keep writes out of Sage
When something needs to go back into Sage, like a batch of supplier invoices, altspark prepares an import file, a person approves it, and Sage validates and posts it through Visual Integrator. altspark never writes into Sage directly.
Visual Integrator checks every data item before files update, and skips and logs any record that fails [Sage 100 Help, 2023]. The worst case is a rejected file, or a bad row a person spots before it posts.
Quick reference checklist
- Step 1: Edition checked, server owner named
- Step 2: Read-only login created, tables listed
- Step 3: Outbound-only connector installed
- Step 4: Sage connected over ODBC, syncs chosen
- Step 5: Server added to Claude
- Step 6: Write-back only through approved import files
Common mistakes to avoid
Mistake 1: Opening the Sage server to the internet
What happens: a firewall rule meant for one connector becomes a permanent way into your accounting system. What to do instead: use an outbound-only connection, or keep the server local (routes 1 and 4).
Mistake 2: Using an everyday Sage login
What happens: the AI can read every table that person can, payroll included. What to do instead: a dedicated read-only login with an allowed-tables list.
Mistake 3: Pointing tools at the default SOTAMAS90 data source
What happens: connections break or point at the wrong install. As one Sage community member put it, "Never use the SOTAMAS90 DSN in a connection string. The SOTAMAS90 DSN values are updated each time Sage 100 is started" [Sage Community Hub, jcnichols, 2021; DATED: 2021, still current advice for ProvideX installs]. What to do instead: create a dedicated data source, or reference the driver directly.
Mistake 4: Letting AI post straight into Sage
What happens: entries skip the validation your accounting depends on. What to do instead: prepare an import file, have a person approve it, and let Visual Integrator validate it.
Mistake 5: Pasting exports into chat
What happens: every answer is as old as the export, and nobody can say which one. What to do instead: connect the source and sync it on a schedule you set.
Key insight: the safe setup is the boring one. Read-only, outbound-only, and a person approving anything that goes back in.
Tools and resources
- Sage 100 ODBC driver: Best for: Reading Sage data; Price: Ships with Sage 100; Our take: The foundation for every route
- Visual Integrator: Best for: Importing into Sage with validation; Price: Sage 100 module; Our take: The safe way back in
- Open-source ODBC MCP servers: Best for: One person in Claude Desktop; Price: Free; Our take: Good for a technical user on one machine
- altspark: Best for: The whole team, any MCP-capable AI; Price: From $299 a month; Our take: Outbound-only, read-only, hosted
Free resources:
- Anthropic's guide to custom connectors [Anthropic Help Center, 2026]
- Sage's guide to configuring the client/server ODBC driver [Sage 100 Installation Guide, 2024]
- Sage's Import Job Maintenance help for Visual Integrator [Sage 100 Help, 2023]
Further reading:
- Is it safe to connect AI to our accounting system?
What to expect
Once it's connected: the questions that used to wait for the person with the login get asked directly: aging, open orders, supplier exposure, with each account's orders beside the aging.
After a few weeks: the Monday export stops. Live insights, altspark's alerts, can watch stock against open orders and start a workflow that tells the buyer.
Realistic expectations: answers are as current as the last sync you schedule. Sage stays the record of who changed what; altspark syncs from it.

