Twinn: Sage 100 Contractor

สอบถาม Claude เกี่ยวกับบริษัท Sage 100 Contractor: งาน ผู้ขาย ใบแจ้งหนี้ และรายงานการก่อสร้าง เช่น WIP ยอดเรียกเก็บเงินเกิน/ขาด และอายุลูกหนี้การค้าและเจ้าหนี้การค้า อ่านได้อย่างเดียว

เซิร์ฟเวอร์ MCP แบบโฮสต์

npx add-mcp 'https://demo-mcp.twinn.engineering/mcp'

ติดตั้งลง Claude Code, Codex, Cursor และอื่นๆ

เอกสาร

Ask Claude or ChatGPT about your Sage 100 Contractor books, read-only.

Twinn runs a read-only MCP server in front of your Sage 100 Contractor company. Add it to Claude Desktop, Claude Code or ChatGPT, and the assistant can look up jobs, vendors and invoices and run 45 Twinn reports, using only the kinds of data you allow. It cannot post, edit or delete anything.

For Sage 100 Contractor (formerly Sage Master Builder). Not for Sage 100 ERP, the distribution and manufacturing product.

One question, start to finish

1You ask Claude a question“How much do we owe our electrical sub, retention included?”

2Claude calls a Twinn toolIt finds the vendor, then reads the open payable invoices for that vendor.

3Twinn checks the connectionThe request is allowed only if this connection may read that kind of data.

4The Twinn service reads SageThe service on your own network reads Sage 100 Contractor and sends back the records.

5Claude answersIt adds up what came back and tells you the total, with the invoices it used.

What it does

The assistant can read 87 kinds of Sage 100 Contractor records, add them up, and run any of the 45 Twinn reports, the same ones your team runs in the Twinn web app. Each answer is built from live records, not from an export.

MCP (the Model Context Protocol) is an open standard that lets an AI assistant use tools run by someone else. The assistant is the client and Twinn is the server. When you ask a question, the assistant reads the list of tools, decides which ones it needs and calls them.

Without MCP, the usual way to get Sage 100 Contractor data into an assistant is to export a report and paste it in. That copy is out of date by the next posting, and it carries every column whether the assistant needs it or not. With MCP the assistant asks for the records it needs, when it needs them, and only gets what your connection allows.

Questions to ask it

We test the tools against a fixed set of questions like these, asked with no prompt of ours, so they work the same in your assistant as in ours.

  • “Which fiscal year and accounting period are we in right now?”
  • “How many open jobs do we have?”
  • “How much do we currently owe this vendor, retention included?”
  • “What is the cost to date on the Northbank Distribution Center job?”
  • “How much of our open payables is charged to that job?”
  • “What is our total payables more than 90 days past due today?”
  • “What is our net income for the fiscal year to date?”
  • “What was our largest job by cost this year and last year?”
  • “How many accounting periods are still open?”

The nine tools the assistant gets

The assistant chooses tools by reading their descriptions, so each one does a single, clearly named job. Every tool reads through the same API and permission checks as the rest of Twinn.

ToolWhat the assistant uses it for
company_contextLearns which company it is connected to, its fiscal year and open periods, and the dates reports default to.
list_entitiesLists the kinds of records this connection may read (jobs, vendors, payable invoices and so on) and any fields held back from it.
describe_entityExplains one kind of record: each field, its meaning and its format, so the assistant asks for the right thing.
decodeTurns a stored code into its name and meaning, so a status of 4 becomes “Paid” instead of a guess.
find_entityLooks records up by name or by filter, such as a vendor by name or the invoices on one job.
summarize_entityAdds records up in one step: counts, totals, smallest and largest, overall or per group, such as open payables per job or job cost by month.
list_reportsLists the Twinn reports this connection may run.
describe_reportExplains a report’s criteria, columns and how it is calculated, before running it.
run_reportRuns a report and returns its totals, or its rows when asked. The answer names the exact report version that ran.

How it works

The MCP server sits between the assistant and the Twinn service on your own network. It answers with what one connection may read, from one company, and nothing else.

  1. 1

    Read-only at the server

    An AI connection has a read-only key. The MCP server refuses any key that is able to post to Sage, so the assistant has no way to change your books.
  2. 2

    One key, one company

    Each connection’s key belongs to one Sage company and selects it on every request. It cannot reach another company, and revoking it leaves the others working.
  3. 3

    One address per company

    Each company has its own connector address, so several companies can be connected side by side in the same assistant.

Set it up

A company administrator does this once per person or per tool. It takes about five minutes.

  1. 1

    Create an AI connection in the Twinn dashboard

    On your company’s Access page, under AI connections, add a connection. Pick the assistant it is for and tick the kinds of data it may read:
    • Everyday recordsjobs, cost codes, vendors and the like
    • Moneyledgers, invoices, payments and balances
    • Payrollpay and hours
    • Personal detailspeople’s names, addresses, phone numbers and emails Everyday records are always included. Leave Payroll and Personal details off unless that person already sees them in Sage.
  2. 2

    Add it to Claude Desktop, claude.ai or ChatGPT

    Add a custom connector, paste the server address the dashboard shows you, and sign in with your Twinn account when the assistant asks. The connection only works for people who are allowed to use it.
  3. 3

    Or paste the snippet into Claude Code and other tools

    Tools that take a configuration file use the snippet the dashboard gives you. It holds the address and the connection’s key. Treat the key like a password: it is shown once.
  4. 4

    Ask a question

    Start with “What can you read from Twinn?” The assistant lists what this connection may see. Then ask a real question. Most assistants ask your permission before each tool call, so you can watch exactly what it reads.
{
  "mcpServers": {
    "twinn": {
      "type": "http",
      "url": "<the address from your dashboard>",
      "headers": { "X-Api-Key": "<your connection key>" }
    }
  }
}

For Claude Code, the same thing as one command

claude mcp add --transport http twinn "<the address from your dashboard>" \
  -H "X-Api-Key: <your connection key>"

Connecting more than one company? Each has its own server address in the dashboard, so add one connector per company. The setup guide and examples on GitHub have configurations for each client.

What the assistant can and cannot do

Written for the controller who owns the books and the IT lead who owns the server. Claude Desktop, claude.ai, Claude Code and ChatGPT all work with it, as does any tool that supports remote MCP servers over HTTP.

Read-only, by design

An AI connection can never write. The MCP server refuses any key that is able to post to Sage, so nothing the assistant does can change your books.

You choose the data

Each connection reads only the kinds of data you ticked, so money, payroll and personal details can each be withheld. Tax IDs and bank details are always withheld. Fields it may not see are left out of every answer, and the assistant is told they were held back.

One connection per person or tool

Every connection has its own key. Revoke one and the others keep working. Nobody shares a login.

Every call is recorded

Each tool call is counted against its connection, and the dashboard shows which reports each one ran.

Answers stay small

Reports return totals by default, and long lists are capped and say so. The assistant cannot pull your whole ledger by accident.

What the AI provider sees

Your question and what the tools returned for it, sent to the provider of the assistant you use, under your agreement with them. Twinn never sends data to an assistant you did not connect.

Included in every plan

AI connections come with every plan, starting with Reports at $3,000 a year, and every plan starts with a free 30-day trial on a demo company.

Your database stays put

Sage 100 Contractor stays on your own server. The Twinn service there makes outbound connections only, with no open ports.

Try it now on the public demo

Add this address to Claude or ChatGPT and sign in. Behind it is Ridgeline Mechanical & Plumbing, a made-up mechanical and plumbing contractor in Sage 100 Contractor, rebuilt every night so its dates run up to today. It runs the same tools and reports as the server your own company would use, and like every Twinn AI connection it is read-only.

https://demo-mcp.twinn.engineering/mcp

In Claude

  1. Open Customize, then Connectors.
  2. Choose Add, then Add custom connector.
  3. Name it Twinn demo and paste the address.
  4. Sign in with Google, or with an email and password.

Works on every Claude plan; Free allows one custom connector. On Team and Enterprise, an owner adds it under Organization settings.

In ChatGPT

Turn on developer mode in ChatGPT’s settings, create a connector with the address above, and sign in when ChatGPT asks.

Custom connectors need a paid ChatGPT plan, and on Business or Enterprise an admin may have to allow them first. OpenAI moves these settings from time to time, so its help pages have the current menus.

Then ask

  • “Which jobs are over budget?”
  • “What is the cost to date and the remaining committed cost on Northbank Distribution Center?”
  • “Run the AP aging. Which vendors are past 60 days?”
  • “What is our over/under billing position this month?”

Signing in shares your name and email with Twinn’s sales team, who may get in touch. We keep the requests your assistant sends to the demo for 12 months, never your conversation, and an account unused for 30 days is removed. See the privacy policy.

Or a demo company of your own

For a longer look, and to see the answers next to the records, we set up a demo company for you: a real Sage 100 Contractor database running on our servers, with books dated to this month, so “what is overdue” has a real answer. Connect Claude to it, ask your questions, and check each answer in the Twinn dashboard, where jobs, vendors, payable and receivable invoices, purchase orders, payroll records and more are laid out like the Sage 100 Contractor screens your team already knows.

  • Fresh books. Transactions are dated to the current month, so aging, overdue and period questions have real answers.
  • Up to 30 days. A trial company lasts up to 30 days, long enough to connect your assistant and try your own questions.
  • Removed when it ends. The demo company, its database and its connections are deleted completely at the end of the trial.

Your own assistant, or Ask Twinn

Ask Twinn is the assistant built into the Twinn web app. It uses these same tools, so it gives the same answers. Pick it if your team does not use an AI assistant today and you want nothing to set up.

Connect your own assistant if your team already works in Claude or ChatGPT and wants Sage 100 Contractor next to their email, documents and spreadsheets.

Developers who want the data in their own code can use the same records through the Twinn API.

Still choosing, or comparing this with exporting a report into a chat? See AI for Sage 100 Contractor, which sets the options side by side.

Questions about the MCP server

Is there a demo I can connect to right now?

Yes. Add https://demo-mcp.twinn.engineering/mcp to Claude or ChatGPT as a custom connector and sign in with Google or an email address. It is Ridgeline Mechanical & Plumbing, a made-up mechanical and plumbing contractor in Sage 100 Contractor, rebuilt every night, read-only, with the same tools and reports as the paid server.

What is an MCP server?

A program that offers tools to an AI assistant over the Model Context Protocol, an open standard. Twinn’s MCP server offers tools that read Sage 100 Contractor records and run reports. The assistant decides when to call them.

Which assistants work with it?

Claude Desktop, claude.ai, Claude Code and ChatGPT. Any other tool that supports remote MCP servers over HTTP can use the configuration snippet.

Can we connect more than one Sage company?

Yes. Each company has its own connector address and its own key, so you can add several companies to the same assistant side by side. Each connector reads only its own company.

Does this work with Sage 100 ERP?

No. Twinn works only with Sage 100 Contractor, the construction accounting product formerly called Sage Master Builder. Sage 100 ERP (formerly MAS 90 and MAS 200) is a separate product on a different database.

Can the assistant change anything in Sage 100 Contractor?

No. AI connections are read-only, and the server refuses any key that is able to write.

What does the AI provider see?

Your question and what the tools returned for it, which is only data the connection is allowed to read. That is sent to the provider of the assistant you use, under your agreement with them. Twinn never sends your data to an assistant you did not connect.

Does Twinn keep a copy of our Sage data?

No. Each tool call reads live data through the Twinn service on your network. There is no warehouse or nightly copy behind it.

Can the assistant get a number wrong?

The figures come from Sage records and Twinn reports, which show how they are calculated. An assistant can still misread a question, so ask it which report or records it used. Every report answer names the report version that ran.

What does it cost?

AI connections are included in every plan, starting with Reports at $3,000 a year. Every plan starts with a free 30-day trial on a demo company, and you can connect your assistant to it during the trial.

See Claude answer from Sage 100 Contractor

Connect to the public demo in a couple of minutes, or tell us which questions you would ask first and we will set up a demo company of your own.