Twinn: Sage 100 Contractor

engineering.twinnPublished by twinn.engineeringOfficial publisherv1.0.0Updated Nov 4, 2026

Read-only Sage 100 Contractor data and construction reports (WIP, AR/AP aging) on a demo company.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Read-only access to Sage 100 Contractor data and construction reports such as WIP and AR/AP aging, served from a demo company.

What you can do
  • Read Sage 100 Contractor records from a demo company.
  • Retrieve construction reports, including work-in-progress (WIP) figures.
  • Review accounts receivable and accounts payable aging.
  • No tool list is published, so the exact operations are not documented.
When to use it
Worth trying when you want an assistant to look up construction accounting figures or aging reports from Sage 100 Contractor without touching production data, for example to explore what a read-only integration could answer.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
The endpoint is a demo company, so figures are not your real books. Access is read-only per the description, but the tool list is unpublished, so confirm what each tool does before relying on it. OAuth grants the server access to your account; review the scopes requested.

Installation

In SourceWeft

  1. Open Twinn: Sage 100 Contractor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/engineering.twinn%2Fsage-100-contractor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "twinn-sage-100-contractor": {
      "type": "http",
      "url": "https://demo-mcp.twinn.engineering/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.