# Sage MCP server

MCP, Sage, read 8 Nov 2026

**The short answer.** Sage's MCP status on 8 Nov 2026: none found. No MCP server found. An outside AI client cannot connect to Sage through MCP on the pages read; the API, where published, is the route. The off switch and the sensitive-field control that apply to the connector are listed below.

- **Status:** none found
- **Access:** not stated
- **Evidence:** No MCP server found.
- **Source:** [www.sage.com/en-us/sage-business-cloud/hr/](https://www.sage.com/en-us/sage-business-cloud/hr/)
- **Off switch:** none found: Not found.
- **Sensitive fields:** partial: Permission levels in Sage HR.
- **AI governance:** none found: Not named.

## What an outside agent can do through it

Nothing through MCP on 8 Nov 2026. Sage's pages describe no agent actions in other systems; a company that runs its AI stack outside the HRIS reaches Sage by API or export.

**Where Shapes is weak.** Shapes's MCP server is documented as read access on the date read; write actions run inside Shapes, not through the connector.

## Sources

- Sage: www.sage.com/en-us/sage-business-cloud/hr/: https://www.sage.com/en-us/sage-business-cloud/hr/ (read 8 Nov 2026)
- Sage: www.sage.com/en-us/trust-security/security/technical/standards-compliance/: https://www.sage.com/en-us/trust-security/security/technical/standards-compliance/ (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestaiagentsforhr.com/mcp/sage/
