# Sage 300 Construction and Real Estate MCP connector

The Sage 300 Construction and Real Estate connector brings companies, employees, equipment and daily field reports to Claude, ChatGPT, Cursor and Microsoft Copilot, so each person works on them as themselves and every call is logged.

Source: https://elaichi.ai/connectors/sage300constructionandrealestate/

## Facts

| | |
| --- | --- |
| Application | Sage 300 Construction and Real Estate |
| Category | Accounting |
| AI tools | 66 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Sage 300 Construction and Real Estate is connected

- List every employee logged on yesterday's field reports.
- Which equipment was used on field reports this week?
- Show the journal entries on field report 4821 before I finalize it.

## Connect Sage 300 Construction and Real Estate in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Sage 300 Construction and Real Estate.
2. Optionally set Share with, then press Connect.
3. Paste a Sage 300 Construction and Real Estate API key. One person generates a token in Sage 300 Construction and Real Estate and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Sage 300 Construction and Real Estate tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Sage 300 Construction and Real Estate MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Sage 300 Construction and Real Estate MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Sage 300 Construction and Real Estate MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Sage 300 Construction and Real Estate MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Sage 300 Construction and Real Estate MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Sage 300 Construction and Real Estate to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Sage 300 Construction and Real Estate tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Sage 300 Construction and Real Estate through Elaichi

### Log the day's labor from the truck

Field operations. Ask the agent to add labor and equipment lines to today's field report in Sage 300 Construction and Real Estate, then finalize it once the crew heads home.

### Check what happened on site yesterday

Project management. Pull a field report's events and extras by number and get a plain summary before the morning call.

### See which machines are on which report

Equipment. List equipment and equipment cost codes, then check what was logged against a field report before the hire invoice arrives.

### Confirm hours before the pay run

Payroll. List employees and read the labor entries on finalized field reports to catch missing or doubled hours.

### Fix a wrong entry before finalization

Accounting. Remove an incorrect journal entry or labor line from a field report and add the corrected one, with the change recorded in the audit log.

### Keep companies and departments straight

Office. List the companies and departments set up in Sage 300 Construction and Real Estate so new staff are coded to the right place from day one.

## Elaichi vs Zapier MCP vs Composio for Sage 300 Construction and Real Estate

All three can connect Sage 300 Construction and Real Estate to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Sage 300 Construction and Real Estate tools | Allow or restrict single Sage 300 Construction and Real Estate tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Sage 300 Construction and Real Estate call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Sage 300 Construction and Real Estate to Claude?

Connect Sage 300 Construction and Real Estate in Elaichi by pasting its API key, there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and you are done.

### Does Sage 300 Construction and Real Estate work with ChatGPT and Cursor as well as Claude?

Yes. Once Sage 300 Construction and Real Estate is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect it once, not once per client.

### What can an AI agent actually do with my Sage 300 Construction and Real Estate data?

It can list your companies, departments, employees, equipment and equipment cost codes in Sage 300 Construction and Real Estate, and it can read, add to, correct and finalize daily field reports, including labor, equipment, events, extras and journal entries. Short, concrete asks work best, such as show the labor on field report 4821.

### Does connecting Sage 300 Construction and Real Estate give the AI access to every company and every field report?

No. Every call runs inside the access of the person who signed in, so an agent sees only the companies and field reports in Sage 300 Construction and Real Estate that person can already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

### Can my team share one Sage 300 Construction and Real Estate connection?

Yes. One person connects Sage 300 Construction and Real Estate with the API key and shares the connection with a team, and nobody else ever handles the key. Each person still signs in to Elaichi as themselves, so the audit log names who finalized a field report or removed a labor line.

### Can I stop an agent from deleting or changing things in Sage 300 Construction and Real Estate?

Yes. Restrictions in Elaichi apply per action, so you can restrict deleting journal entries or finalizing field reports in Sage 300 Construction and Real Estate for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Sage 300 Construction and Real Estate connection when someone leaves?

Offboarding someone in Elaichi ends their access to Sage 300 Construction and Real Estate through every client at once. A connection they shared keeps working for everyone else on the team. If you want the application gone entirely, disconnect it once in Elaichi and it is removed from every client.

### Does the Sage 300 Construction and Real Estate MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Sage 300 Construction and Real Estate is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Sage 300 Construction and Real Estate?

Yes. Both let Claude, ChatGPT or Cursor use Sage 300 Construction and Real Estate. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Sage 300 Construction and Real Estate call.

### How is Elaichi different from Composio for Sage 300 Construction and Real Estate?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Sage 300 Construction and Real Estate: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 66 Sage 300 Construction and Real Estate tools

Every tool below is callable through https://api.elaichi.ai/mcp once Sage 300 Construction and Real Estate is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Sage 300 Construction and Real Estate auth token** (Create). Log in with the connected Windows user (Domain\User) and get an X-Credentials token (POST /api/common/user/authenticate). The connector calls it on connect and every 20 minutes and fills the body from the account; callers send no body.
- **List all Sage 300 Construction and Real Estate companies** (List). Returns a list of companies to which the authenticated user has access (GET /api/common/company).
- **List all Sage 300 Construction and Real Estate departments** (List). Gets the list of Payroll departments (GET /api/payroll/department). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **List all Sage 300 Construction and Real Estate employees** (List). Gets the Payroll employee list (GET /api/payroll/employee). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **List all Sage 300 Construction and Real Estate equipment** (List). Gets a list of the Equipment Cost equipment items (GET /api/equipment). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **List all Sage 300 Construction and Real Estate equipment cost codes** (List). Gets a list of the Equipment Cost cost code items (GET /api/equipment/costcode). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **Create field report deletion** (Create). Delete a field report (POST /api/fieldreports/fieldreports/delete) by Index and DateTimeStamp.
- **Get field report equipment by ID** (Get). Get a field report equipment observation by index (GET /api/fieldreports/equipment/{index}). id: the observation index.
- **Create field report equipment** (Create). Save a field report equipment observation: creates it, or updates it when Index is given (POST /api/fieldreports/equipment/save).
- **Create field report equipment deletion** (Create). Delete a field report equipment observation (POST /api/fieldreports/equipment/delete) by Index and DateTimeStamp.
- **Create field report event deletion** (Create). Delete a field report event observation (POST /api/fieldreports/event/delete) by Index and DateTimeStamp.
- **Get field report event by ID** (Get). Get a field report event observation by index (GET /api/fieldreports/event/{index}). id: the observation index.
- **Create a Sage 300 Construction and Real Estate field report event** (Create). Save a field report event observation: creates it, or updates it when Index is given (POST /api/fieldreports/event/save).
- **Create field report extra deletion** (Create). Delete a field report extra observation (POST /api/fieldreports/extra/delete) by Index and DateTimeStamp.
- **Get field report extra by ID** (Get). Get a field report extra observation by index (GET /api/fieldreports/extra/{index}). id: the observation index.
- **Create a Sage 300 Construction and Real Estate field report extra** (Create). Save a field report extra observation: creates it, or updates it when Index is given (POST /api/fieldreports/extra/save).
- **Create field report finalization** (Create). Finalize a field report so it can no longer be changed (POST /api/fieldreports/fieldreports/finalize) by Index and DateTimeStamp.
- **Get field report journal entry by ID** (Get). Get a field report journal entry observation by index (GET /api/fieldreports/journalentry/{index}). id: the observation index.
- **Create field report journal entry** (Create). Save a field report journal entry observation: creates it, or updates it when Index is given (POST /api/fieldreports/journalentry/save).
- **Create field report journal entry deletion** (Create). Delete a field report journal entry observation (POST /api/fieldreports/journalentry/delete) by Index and DateTimeStamp.
- **Get field report labor by ID** (Get). Get a field report labor observation by index (GET /api/fieldreports/labor/{index}). id: the observation index.
- **Create a Sage 300 Construction and Real Estate field report labor** (Create). Save a field report labor observation: creates it, or updates it when Index is given (POST /api/fieldreports/labor/save).
- **Create field report labor deletion** (Create). Delete a field report labor observation (POST /api/fieldreports/labor/delete) by Index and DateTimeStamp.
- **Create field report material deletion** (Create). Delete a field report material observation (POST /api/fieldreports/material/delete) by Index and DateTimeStamp.
- **Get field report material by ID** (Get). Get a field report material observation by index (GET /api/fieldreports/material/{index}). id: the observation index.
- **Create field report material** (Create). Save a field report material observation: creates it, or updates it when Index is given (POST /api/fieldreports/material/save).
- **Create field report payroll time deletion** (Create). Delete a field report Payroll time observation (POST /api/fieldreports/payrolltime/delete) by Index and DateTimeStamp.
- **Create field report payroll time submission** (Create). Send the Payroll time observations of a field report within a date range to Payroll (POST /api/fieldreports/payrolltime/sendtopayroll).
- **Get field report payroll time by ID** (Get). Get a field report Payroll time observation by index (GET /api/fieldreports/payrolltime/{index}). id: the observation index.
- **Create field report payroll time** (Create). Save a field report Payroll time observation: creates it, or updates it when Index is given (POST /api/fieldreports/payrolltime/save).
- **Create field report subcontractor deletion** (Create). Delete a field report subcontractor observation (POST /api/fieldreports/subcontractor/delete) by Index and DateTimeStamp.
- **Get field report subcontractor by ID** (Get). Get a field report subcontractor observation by index (GET /api/fieldreports/subcontractor/{index}). id: the observation index.
- **Create field report subcontractor** (Create). Save a field report subcontractor observation: creates it, or updates it when Index is given (POST /api/fieldreports/subcontractor/save).
- **Create field report visitor deletion** (Create). Delete a field report visitor observation (POST /api/fieldreports/visitor/delete) by Index and DateTimeStamp.
- **Get field report visitor by ID** (Get). Get a field report visitor observation by index (GET /api/fieldreports/visitor/{index}). id: the observation index.
- **Create a Sage 300 Construction and Real Estate field report visitor** (Create). Save a field report visitor observation: creates it, or updates it when Index is given (POST /api/fieldreports/visitor/save).
- **Create field report weather site condition deletion** (Create). Delete a field report weather and site conditions observation (POST /api/fieldreports/weathersiteconditions/delete) by Index and DateTimeStamp.
- **Get field report weather site condition by ID** (Get). Get a field report weather and site conditions observation by index (GET /api/fieldreports/weathersiteconditions/{index}). id: the observation index.
- **Create field report weather site condition** (Create). Save a field report weather and site conditions observation: creates it, or updates it when Index is given (POST /api/fieldreports/weathersiteconditions/save).
- **Get field report work activity by ID** (Get). Get a field report work activities observation by index (GET /api/fieldreports/workactivities/{index}). id: the observation index.
- **Create field report work activity** (Create). Save a field report work activities observation: creates it, or updates it when Index is given (POST /api/fieldreports/workactivities/save).
- **Create field report work activity deletion** (Create). Delete a field report work activities observation (POST /api/fieldreports/workactivities/delete) by Index and DateTimeStamp.
- **List all Sage 300 Construction and Real Estate field reports** (List). Gets a list of field reports that match the given criteria (GET /api/fieldreports). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **Get single Sage 300 Construction and Real Estate field report by ID** (Get). Get a field report with all its observations (GET /api/fieldreports/{index}). id: the field report index.
- **Create a Sage 300 Construction and Real Estate field report** (Create). Save a field report: creates it, or updates it when FieldReportIndex is given (POST /api/fieldreports/fieldreports/save).
- **List all Sage 300 Construction and Real Estate files** (List). Gets the list of named files (GET /api/common/files). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **List all Sage 300 Construction and Real Estate job contacts** (List). Gets the list of job contacts for a Project Management job index (GET /api/jobs/contacts). Required: pjJob.
- **Create job cost batch posting** (Create). Post Job Cost batches from the new-transaction file (JCT_NEW_TRANSACTION) to the current-transaction file (POST /api/transactions/post). Pick batches from job_cost_batches.list.
- **List all Sage 300 Construction and Real Estate job cost batches** (List). Gets the list of Job Cost batches in the JCT_NEW_BATCH file, or the named file specified if allowed (GET /api/transactions/batch).
- **List all Sage 300 Construction and Real Estate job cost categories** (List). Gets the Job Cost category items (GET /api/jobcost/category). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- ...and 16 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
